www.homeseer.com    
 

Go Back   HomeSeer Message Board > Lighting & Primary Technology Plug-ins > Lighting & Primary Technology Discussion > UPB plugin by Spud (3P)

UPB plugin by Spud (3P) Spud UPB plugin discussions.

Reply
 
Thread Tools Display Modes
  #1  
Old November 22nd, 2013, 03:47 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
UPB Plug-in - Beta Testing

This plugin is designed to allow HomeSeer (HS3 or HS3PRO) to control UPB (Universal Powerline Bus) hardware.

Please report any bug.

Please read the User Guide before installing.

Installation:
  • download the zip attached to this post and save it in the HS3 application folder /updates3/zips
  • download the file named updater_override.txt attached to this post and save it in the HS3 application folder.
  • go to the "PLUG-INS > Manage" page and click the "Update Listing" button, then click "Additional interfaces > Test Plugin" and check the UPB line.
  • click the "Download and Install" button
  • enable the plugin from the "PLUG-INS > Manage" page
  • delete updater_override.txt from your HS3 application folder

Changes to v3.0.0.41
- Automatic update of Link devices so that the "Is Dimmable" field is set.

Changes to v3.0.0.40
- Added room to the name of device in the device list of the "Poll Device State" action

Changes to v3.0.0.39
- Automatic update of Link devices created with version < 3.0.0.35 so that ControUse field is set for Activate/Deactivate.

Changes to v3.0.0.38
- Fixed regression introduced in .35 for UMI-32 3-Input / 2-Output Module

Changes to v3.0.0.37
- Fixed problem with multiple instances feature.

Changes to v3.0.0.36
- Added ability to run multiple instances of the plug-in
- Fixed import error

Changes to v3.0.0.35
- Support for UCQF-W 3-Speed Fan controller
- Set Control-Use On/Off property for Link devices Activate/Deactivate controls

Changes to v3.0.0.31
- Added possibility to change number of transmission attempts

Changes to v3.0.0.30
- Added support for PulseWorx Gateway PGW (Ethernet based controller)
- Added icon for different dim levels

Changes to v3.0.0.29
- Fixed possible buffer overrun
- Added more error trapping

Changes to v3.0.0.28
- Fixed error when accessing config page for the first time.

Changes to v3.0.0.27
- Added "Fade Up", "Fade Down", "Goto On", "Goto Off" as possible actions for the "UPB device transmits Link" trigger
- Fixed "Fade Stop" problem

Changes to v3.0.0.26
- Added "Action" parameter to "UPB device transmits Link" trigger
- Speed up handling of HS devices

Changes to v3.0.0.25
- Added "UPB Device transmits Link" trigger

Changes to v3.0.0.24
- Fixed problem with devices being updated after each plugin restart.

Changes to v3.0.0.23
- Added setting to disable polling of devices at startup.

Changes to v3.0.0.22
- Automatic upgrade of devices.

Changes to v3.0.0.21
- Added Blink feature for both links and devices

Changes to v3.0.0.20
- Fixed Snap On/Snap Off status for Links

Changes to v3.0.0.19
- ignore messages received that have already been treated in a previous transmission

Changes to v3.0.0.18
- added support for HAI keypad indicator lights
- fixed status device update when turning on a dimming device

Changes to v3.0.0.15:
- Fixed problem with using default fade rate (255) for non dimming devices.

Changes to v3.0.0.14:
- Added indicator lights on/off buttons for keypads

Changes to v3.0.0.13:
- Fixed crash when the plugin is shut down.

Changes to v3.0.0.12:
- Implemented ControlUse interface for UPB devices

Changes to v3.0.0.11:
- Fixed issue with Timed Event Controller.
- Cosmetic changes

Changes to v3.0.0.9:
- Added support for keypads.
- Implemented HS polling feature

Changes to v3.0.0.8:
- Added "Poll Device State" Action.

Changes to v3.0.0.7:
- Fixed problem when turning on non dimmable devices

Changes to v3.0.0.6:
- Fixed problem with I/O devices
- Fixed problem with Links not reporting their status to HS devices

Changes to v3.0.0.5:
- Added support for I/O devices and devices with several channels
- Added an import button on config page which allow to re-import the .upe file without restarting the plugin.

Changes to v3.0.0.4:
- Renamed plugin to UPBSpud to avoid license issues with the HS2 UPB plugin

Changes to v3.0.0.3:
- Possibility to override the serial port configuration from UPB.ini

Changes to v3.0.0.2:
- Fixed a problem preventing import of device with more than 1 channel

Changes to v3.0.0.1:
- Plugin now works on Linux
- Fixed a problem preventing the plugin to shutdown gracefully.

spud
Attached Files
File Type: zip UPBSpud_3-0-0-41.zip (226.2 KB, 8 views)
File Type: txt updater_override.txt (3.1 KB, 4 views)

Last edited by spud; November 20th, 2017 at 04:46 PM.
Reply With Quote
  #2  
Old November 24th, 2013, 01:39 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
Testing....from one ubuntu machine to another (both have testing HS3 for Linux on them).


Quote:
root@ICS-joggler2:/usr/local/upb-remote# mono HSPI_UPB.exe server=192.168.244.172
Plugin: UPB Instance: starting...
Connecting to server at 192.168.244.172...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
Missing method UPB4CSharp.PIMAdapter::SetPIMPort(SerialPort) in assembly /usr/local/upb-remote/UPB4CSharp.dll, referenced in assembly /usr/local/upb-remote/HSPI_UPB.exe
Connection lost, exiting
Disconnected from server - client
Error SendInvokeResponse: Client is not connected to the server.

172 - Ubuntu running HS3
189 - Unbuntu running plugin

Here is what I see on the HS3 logs on the remote end.

Quote:
Nov-24 11:46:13 AM Error Initializing plug-in(2): UPB Instance::Object reference not set to an instance of an object0STACK: at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000] in {0x3C}filename unknown{0x3E}:0
Nov-24 11:46:13 AM Info Plugin UPB with instance: has disconnected
Nov-24 11:46:13 AM Info Plug-in UPB has connected successfully
Nov-24 11:46:13 AM Info Remote application or plugin has connected: 192.168.244.189:38010
Nov-24 11:46:13 AM Info Remote application or plugin has connected: 192.168.244.189:38009
__________________
- Pete

Automator

HS3 Pro & Lite
Edition Beta 3.0.0.387 | Ubuntu 16.04 64 bit | Oracle Windows Virtual Box ==> for Wintel only SAPI and HS3 plugins

Reply With Quote
  #3  
Old November 24th, 2013, 01:46 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
Quote:
Missing method UPB4CSharp.PIMAdapter::SetPIMPort(SerialPort) in assembly /usr/lo cal/upb-remote/UPB4CSharp.dll, referenced in assembly /usr/local/upb-remote/HSPI _UPB.exe
make sure you are using the latest exe (HSPI_UPB.exe) and latest dll (UPB4CSharp.dll) from the zip on first post of this thread. This methos has changed in version 3.0.0.1
Reply With Quote
  #4  
Old November 24th, 2013, 02:03 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
Copied over the newest files.

Plugin on the HS3 Linux box appears to work now and created devices.

Remote shows:

Quote:
root@ICS-joggler2:/usr/local/upb-remote# mono HSPI_UPB.exe server=192.168.244.172
Plugin: UPB Instance: starting...
Connecting to server at 192.168.244.172...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
ERROR Cannot read UPStart export file: /usr/local/HomeSeer/Config/export.upe
^C
Here I copied the export file to the locally installed HS3 directory (HS3 is not running right now on remote machine). It looks like it loaded the export.upe file then.

Quote:
root@ICS-joggler2:/usr/local/upb-remote# mono HSPI_UPB.exe server=192.168.244.172
Plugin: UPB Instance: starting...
Connecting to server at 192.168.244.172...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
ERROR Invalid Serial Port: COM1
ERROR PIMADAPTER:: Unable to open PIM port COM1
copying over the INI file....
Reply With Quote
  #5  
Old November 24th, 2013, 02:08 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
My mistake.

Changing everything such that 189 runs the HS3 for Linux and 172 runs the remote on the Ubuntu box (that is where the UPB controller is plugged in).

A couple minutes....

OK...so I am running remote plugin on Ubuntu 172 talking to HS3 on Ubuntu 189.

Ubuntu 172 has the UPB plugged in via a USB/serial link. /dev/ttyUSB1

Quote:
root@ICS-ZM2:/usr/local/upb-remote# mono HSPI_UPB.exe server=192.168.244.189
Plugin: UPB Instance: starting...
Connecting to server at 192.168.244.189...
Connection attempt #1
Cannot connect(2):Object reference not set to an instance of an object
^C
I then tried to run the remote plugin on 189 talking to HS3 on 189 and see the same:

Quote:
root@ICS-joggler2:/usr/local/upb-remote# mono HSPI_UPB.exe server=192.168.244.189
Plugin: UPB Instance: starting...
Connecting to server at 192.168.244.189...
Connection attempt #1
Cannot connect(2):Object reference not set to an instance of an object
^C
I see just a couple of issues:

1 - The remote couldn't find the export file until I put it in the HomeSeer directory on the same computer.
2 - Guessing that the methodology of use for the remote plugin would be that the machine running the remote plugin has the UPB PIM connected to it.

That said I get the above error when running the remote plugin with the UPB PIM plugged into same said machine.

I am guessing that this is the way it should work eh?

Remote box #1
Linux - connected to PIM and running remote plugin - IP #172

HS3 Box #2
Linux - running HS3 - IP #189

Last edited by Pete; November 24th, 2013 at 02:26 PM.
Reply With Quote
  #6  
Old November 24th, 2013, 02:39 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
So I installed the UPB plugin on box #189 HS3 that is currently running but left it disabled.

I then reran remote from box #172. I see a difference now in the SSH session.

Quote:
root@ICS-ZM2:/usr/local/upb-remote# ^C
root@ICS-ZM2:/usr/local/upb-remote# mono HSPI_UPB.exe server=192.168.244.189
Plugin: UPB Instance: starting...
Connecting to server at 192.168.244.189...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
ERROR Invalid Serial Port: COM1
ERROR PIMADAPTER:: Unable to open PIM port COM1
^C
Curious where the remote plugin gets its connection settings from?

I see only references to the UPB port in the settings.ini file on the homeseer3 directory but no where else.

Quote:
/usr/local/HomeSeer/Config/settings.ini
Quote:
COMPort_UPB:=/dev/ttyUSB1
and in HSPI_UPB.exe.config I see:

Quote:
<?xml version="1.0"?>
<configuration>
<startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup>
<runtime>
<loadFromRemoteSources enabled="true"/>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="bin/UPB;bin"/>
</assemblyBinding>
</runtime>
</configuration>

Last edited by Pete; November 24th, 2013 at 03:03 PM.
Reply With Quote
  #7  
Old November 24th, 2013, 03:05 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
Please confirm that if you install everything (HS3, plugin, PIM) on the same linux box, it works? At some point you said the HS devices were created so I assume it does.

You always need to have the PIM and the plugin on the same box. One potential problem when running the plugin remotely is that the dropdown list of serial ports you see on the PLUGINS > Manage page is built by HS not the plugin, so it's the list of serial ports of the HS box. So if the name of the serial port of the HS box and Plugin box is not exactly the same it won't work.

From your logs it seems that the plugin tries to connect to COM1 which doesn't look like a linux serial port name, do you know where this is coming from?
Reply With Quote
  #8  
Old November 24th, 2013, 03:20 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
Quote:
Please confirm that if you install everything (HS3, plugin, PIM) on the same linux box, it works? At some point you said the HS devices were created so I assume it does.
Here is the HS3 for Linux running on box #172 and enabling UPB plugin on same said box.

Something is going on now because it loaded it the first time just fine. Whatever is happening its messing with HS3 and shutting it down.

Quote:
root@ICS-ZM2:/usr/local/HomeSeer# Plugin: UPB Instance: starting...
Connecting to server at 127.0.0.1...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
ERROR Invalid Serial Port: COM1
ERROR PIMADAPTER:: Unable to open PIM port COM1
Yup I do not have any COM1 ports on the Linux box.

Rebooted machine and will start again.

Changing computer console...moving to a different room now...
Reply With Quote
  #9  
Old November 24th, 2013, 03:29 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
I think I know whats going on, when you start the plugin remotely (or even on the same machine but manually) you can't choose the serial port on the PLUGINS > Manage page, so it always use COM1 by default, which of course never works on Linux.

So, I need to add a setting in UPB.ini to override the serial port configuration done by HS. Until it's done your only choice is to run the plugin locally and start it from the web interface (PLUGINS > Manage) and not from command line.
Reply With Quote
  #10  
Old November 24th, 2013, 03:33 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
OK.

Moved to 3 screens now. Easier than looking at one screen doing this stuff.

The linux plugin also seems to drifting over to using a com1 by default.

I will change the INI settings in the settings.ini file back and see if the UPB plugin starts up OK on the Linux box.

I rebooted the original machine and am looking at the settings.ini file stuff. I have not started HS3 yet. It shows.

Quote:
io_interfaces=UPB:
COMPort_UPB:=/dev/ttyS0
Left it alone and restarted Homeseer 3 on the Ubuntu box.

Its showing what I see above on boot.

Quote:
root@ICS-ZM2:/usr/local/HomeSeer# mono HSConsole.exe &
[1] 2751
root@ICS-ZM2:/usr/local/HomeSeer# Plugin: UPB Instance: starting...
Connecting to server at 127.0.0.1...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
ERROR PIMADAPTER:: Unable to open PIM port /dev/ttyS0
This error makes HS3 do a partial start cuz I see the mono process but cannot get to the web gui. I killed the mono process and HS3 kept restarting.

That said rebooted the box again. I will edit the ini file first before starting HS3.

Last edited by Pete; November 24th, 2013 at 04:00 PM.
Reply With Quote
  #11  
Old November 24th, 2013, 03:48 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
you should not have to edit anything in settings.ini
if you still get an error and this error shows the correct port name, it means that the port is used by another process or not correctly configured. Make sure you don't have some hanging HSPI_UPB.exe processes.
Reply With Quote
  #12  
Old November 24th, 2013, 04:14 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
I had an issue here.

I have two USB to serial devices plugged into the Ubuntu box.

When I plugged the USB to UPB device; it would not come up.

That said I moved it to a different USB port and it came right up.

Quote:
root@ICS-ZM2:/usr/local/HomeSeer# lsusb
Bus 001 Device 004: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader
Bus 002 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@ICS-ZM2:/usr/local/HomeSeer#
Second issue was that I didn't update the HS3 on this machine with the newer plugin and just did that and restarted HS3.

Quote:
11/24/2013 2:08:13 PM:[Startup]->Scripting is OK and is now running Startup.vb
11/24/2013 2:10:06 PM:[Plug-In]->Interface UPB is running as a trial, 30 days remaining.
Plugin: UPB Instance: starting...
Connecting to server at 127.0.0.1...
Connection attempt #1
11/24/2013 2:10:06 PM:[Info]->Remote application or plugin has connected: 127.0.0.1:35629
11/24/2013 2:10:06 PM:[Info]->Remote application or plugin has connected: 127.0.0.1:35630
11/24/2013 2:10:06 PM:[Info]->Plug-in UPB has connected successfully
Connected (HomeSeer API 3). Waiting to be initialized...
11/24/2013 2:10:07 PM:[Plug-In]->Finished initializing plug-in UPB
Still having an issue. I saw the browser window for about a minute; now I do not see it.

I do not see a mono process running so I will restart HS3.

The webgui keeps locking up. I do not know what is causing it.

Rebooted box again.

Quote:
root@ICS-ZM2:~# cd /usr/local/HomeSeer
root@ICS-ZM2:/usr/local/HomeSeer# mono HSConsole.exe &
[1] 1997
root@ICS-ZM2:/usr/local/HomeSeer# Plugin: UPB Instance: starting...
Connecting to server at 127.0.0.1...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
Looks like something is/was locking up Firefox. I cannot tell what it is. If I go the UPB configuration page; FF hangs and I have to kill it and start again.

HS3 is running though. The startup of HS3 in the SSH window just sits a the connected prompt but doesn't return back to the SSH prompt

It did create all of the UPB devices and I tested a few and it talks fine to my switches.

Quote:
Nov-24 2:40:24 PM Device Control Device: 2nd Floor Meagan Bedroom to On (100) by/from: CAPI Control Handler
Nov-24 2:40:17 PM Device Control Device: 2nd Floor Edward BR SW-3 to On (100) by/from: CAPI Control Handler
Nov-24 2:39:17 PM Device Control Device: FR-OFF to Fade On (100) by/from: CAPI Control Handler
Nov-24 2:31:45 PM Device Control Device: 2nd Floor Study to On (100) by/from: CAPI Control Handler
Nov-24 2:31:42 PM Device Control Device: 2nd Floor Study to Off (0) by/from: CAPI Control Handler
Nov-24 2:31:39 PM Device Control Device: 2nd Floor Study to On (100) by/from: CAPI Control Handler
Shut down Homeseer from the GUI, rebooted and started it again.

Quote:
Nov-24 2:45:02 PM Startup Checking for available plug-ins
Nov-24 2:45:02 PM Plug-In Found plug-in: UPB, version: 3.0.0.1
Nov-24 2:45:03 PM Plug-In Found plug-in: Z-Wave, version: 3.0.0.29
Nov-24 2:45:03 PM Startup Initializing Plug-Ins
Nov-24 2:45:03 PM Plug-In Interface UPB is running as a trial, 30 days remaining.
Nov-24 2:45:03 PM Info Remote application or plugin has connected: 127.0.0.1:50145
Nov-24 2:45:03 PM Info Remote application or plugin has connected: 127.0.0.1:50146
Nov-24 2:45:04 PM Info Plug-in UPB has connected successfully
Nov-24 2:45:04 PM Plug-In Finished initializing plug-in UPB
Not sure why but FF is hanging. Only have two windows open. One to the HS3 GUI and one to HS forum.

Thank you Spud for providing the opportunity to test the plugin on the Linux boxes.

Last edited by Pete; November 24th, 2013 at 04:47 PM.
Reply With Quote
  #13  
Old November 24th, 2013, 05:14 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
so, everytime you go to the UPB config page, FF hangs?

to make it work from a remote box, you can try the version attached (unzip and copy over HSPI_UPB.exe)
in UPB.ini in your HS3 box add these lines:
Code:
[PIM]
com_port=/dev/ttyUSB1
this will override the com port that HS2 pass as a parameter to the plugin.
Attached Files
File Type: zip HSPI_UPB.zip (16.2 KB, 4 views)
Reply With Quote
  #14  
Old November 24th, 2013, 07:13 PM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
Earlier I am thinking that stuff got cached from starting and stopping HS3 and I kept switching from Linux to Wintel to Linux PCs.

Worked! This is great! Thank-you Spud!

Quickie Overview:

1 - Machine 189 - Joggler running Ubuntu 12.X - HS3 Pro for Linux - installed UPB plugin and disabled it.
2 - Machine 172 - 64bit Ubuntu 12.X - HS3Pro for Linux is installed - remote UPB is installed - shut off HS3Pro - ran the remote plugin configured to talk to machine 189

Quote:
root@ICS-ZM2:/usr/local/upb-remote# mono HSPI_UPB.exe server=192.168.244.189 &
[1] 10052
root@ICS-ZM2:/usr/local/upb-remote# Plugin: UPB Instance: starting...
Connecting to server at 192.168.244.189...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
Quote:
Jan-02 14:38:23 Info Remote application or plugin has connected: 192.168.244.172:45484
Jan-02 14:38:23 Info Remote application or plugin has connected: 192.168.244.172:45485
Jan-02 14:38:24 Info Plug-in UPB has connected successfully
Jan-02 14:39:10 Info Plugin UPB with instance: has disconnected
Jan-02 14:39:27 Info Remote application or plugin has connected: 192.168.244.172:45490
Jan-02 14:39:27 Info Remote application or plugin has connected: 192.168.244.172:45491
Jan-02 14:39:27 Info Plug-in UPB has connected successfully
I was able to turn on and off UPB lights just fine. I am not seeing anything in the HS3 logs regarding turning on and off of the lights.
Attached Images
 

Last edited by Pete; November 24th, 2013 at 07:26 PM.
Reply With Quote
  #15  
Old November 25th, 2013, 09:09 AM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
25th November, 2013 - Day 2 - Ubuntu box #1 running remote plugin with a /dev/ttyUSB1 hardware connection talking to Ubuntu box #2 running HS3 for Linux V dot 42.

All appears fine this morning; thank you Spud.

The response times are excellent relating to web page control of the UPB direct connects and UPB link connects.

I am only running your UPB stuff plus Jon's HS3/HS2 conduit with two HS2 machines.

The above said; is there anything in particular that you want me to test at this time?
Reply With Quote
  #16  
Old November 25th, 2013, 10:42 AM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
Quote:
Originally Posted by Pete View Post
I am not seeing anything in the HS3 logs regarding turning on and off of the lights.
If you go to the config page and set the log level to debug, you will see a lot more stuff logged. But maybe I should move some of these logs at the INFO level?

Quote:
Originally Posted by Pete View Post
Is there anything in particular that you want me to test at this time?
Nothing specific, just make sure you can control all your devices from HS. I already know that the UPB devices that use more than 1 channel don't work correctly. So I have to fix that.
Reply With Quote
  #17  
Old November 25th, 2013, 10:56 AM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
Set the configuration to debug.

Here is the log playing with two switches. The garage UPB is a dual load; multitoggle switch. I do notice that only the garage coach lights show up and not the interior garage lighting shows. I utilize many links. Migrated a couple of years ago from single toggle UPB switches to multitoggle (with many links) and dual load switches. Wife knows the kitchen switches better than me. (4-4 multitoggle switches there for the lighting in the kitchen stuff).

Yup: personally I am OK with the stuff at the debug level versus the info level; but that is me.

Quote:
Nov-25 8:56:22 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C37FF220020{0xD}]
Nov-25 8:56:22 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
Nov-25 8:56:22 AM UPB DEBUG PIM_SEND:: Sending Message ID 12 to PIM, retry count=0
Nov-25 8:56:22 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 12)
Nov-25 8:56:22 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
Nov-25 8:56:22 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
Nov-25 8:56:22 AM Device Control Device: Outside Garage Coach to Off (0) by/from: CAPI Control Handler
Nov-25 8:56:15 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09056CFF37860707BC]
Nov-25 8:56:12 AM UPB DEBUG DEVICE[55]:: Level changing on channel 1 from 0 to 7
Nov-25 8:56:09 AM UPB DEBUG DEVICE[55]:: Level changing on channel 0 from 0 to 7
Nov-25 8:56:09 AM UPB DEBUG PIM_SEND:: Resuming sending as we received at least one device message
Nov-25 8:56:09 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09046CFF37860707BD]
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Pausing because last command expected a reply
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Message ID 34 confirmed sent successfully
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=34)
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=34)
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[07146C37FF3013{0xD}]
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Sending Message ID 34 to PIM, retry count=0
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 34)
Nov-25 8:56:08 AM UPB DEBUG DEVICE[55]:: Confirmed request to set device to level succeedded -- updating internal state
Nov-25 8:56:08 AM UPB DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
Nov-25 8:56:08 AM UPB DEBUG UPB_MGR:: STATE_QUEUE:: Sending state queury for device Garage Coach (55)
Nov-25 8:56:08 AM UPB DEBUG DEVICE[55]:: Got request to set light to non-normative level -- queueing status request to confirm
Nov-25 8:56:08 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Message ID 11 confirmed sent successfully
Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=11)
Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=11)
Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C37FF2264BC{0xD}]
Nov-25 8:56:07 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: Sending Message ID 11 to PIM, retry count=0
Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 11)
Nov-25 8:56:07 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
Nov-25 8:56:07 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
Nov-25 8:56:07 AM Device Control Device: Outside Garage Coach to On (100) by/from: CAPI Control Handler
Nov-25 8:56:02 AM UPB DEBUG DEVICE[54]:: Confirmed request to set device to level succeedded -- updating internal state
Nov-25 8:56:00 AM UPB DEBUG DEVICE[54]:: Level changing on channel 0 from 100 to 0
Nov-25 8:56:00 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
Nov-25 8:56:00 AM UPB DEBUG PIM_SEND:: Message ID 10 confirmed sent successfully
Nov-25 8:56:00 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=10)
Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=10)
Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C36FF220021{0xD}]
Nov-25 8:55:59 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: Sending Message ID 10 to PIM, retry count=0
Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 10)
Nov-25 8:55:59 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
Nov-25 8:55:59 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
Nov-25 8:55:59 AM Device Control Device: Outside Front Door to Off (0) by/from: CAPI Control Handler
Nov-25 8:55:55 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU08056CFF36866468]
Nov-25 8:55:53 AM UPB DEBUG PIM_SEND:: Resuming sending as we received at least one device message
Nov-25 8:55:53 AM UPB DEBUG DEVICE[54]:: Level changing on channel 0 from 0 to 100
Nov-25 8:55:53 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU08006CFF3686646D]
Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Pausing because last command expected a reply
Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Message ID 33 confirmed sent successfully
Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=33)
Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=33)
Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[07146C36FF3014{0xD}]
Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Sending Message ID 33 to PIM, retry count=0
Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 33)
Nov-25 8:55:52 AM UPB DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
Nov-25 8:55:52 AM UPB DEBUG UPB_MGR:: STATE_QUEUE:: Sending state queury for device Front Door (54)
Nov-25 8:55:49 AM UPB DEBUG DEVICE[54]:: Confirmed request to set device to level succeedded -- updating internal state
Nov-25 8:55:49 AM UPB DEBUG DEVICE[54]:: Got request to set light to non-normative level -- queueing status request to confirm
Nov-25 8:55:49 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: Message ID 9 confirmed sent successfully
Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=9)
Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=9)
Nov-25 8:55:48 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C36FF2264BD{0xD}]
Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: Sending Message ID 9 to PIM, retry count=0
Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 9)
Nov-25 8:55:48 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
Nov-25 8:55:48 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
Nov-25 8:55:47 AM Device Control Device: Outside Front Door to On (100) by/from: CAPI Control Handler
Nov-25 8:55:40 AM Device Control Device: Outside Garage Coach to Off (0) by/from: CAPI Control Handler
Nov-25 8:55:27 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09056CFF37860000CA]
Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: Resuming sending as we received at least one device message
Nov-25 8:55:26 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09046CFF37860000CB]
Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: Pausing because last command expected a reply
Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: Message ID 32 confirmed sent successfully
Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=32)
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=32)
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[07146C37FF3013{0xD}]
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Sending Message ID 32 to PIM, retry count=0
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 32)
Nov-25 8:55:25 AM UPB DEBUG DEVICE[55]:: Confirmed request to set device to level succeedded -- updating internal state
Nov-25 8:55:25 AM UPB DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
Nov-25 8:55:25 AM UPB DEBUG UPB_MGR:: STATE_QUEUE:: Sending state queury for device Garage Coach (55)
Nov-25 8:55:25 AM UPB DEBUG DEVICE[55]:: Got request to set light to non-normative level -- queueing status request to confirm
Nov-25 8:55:25 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Message ID 8 confirmed sent successfully
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=8)
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=8)
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C37FF2264BC{0xD}]
Nov-25 8:55:25 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Sending Message ID 8 to PIM, retry count=0
Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 8)
Nov-25 8:55:25 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
Nov-25 8:55:24 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
Nov-25 8:55:24 AM Device Control Device: Outside Garage Coach to On (100) by/from: CAPI Control Handler
Attached Images
 
Reply With Quote
  #18  
Old November 26th, 2013, 08:51 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,621
new version available 3.0.0.5

I have uploaded a new version in first post of this thread.

The plugin has been renamed to UPBSpud to avoid any license issue with the existing UPB plugin for HS2. So if you are upgrading from a previous version you will need to delete all your UPB devices (UPB Device and UPB Link types)

I/O devices and devices using several channels are now supported.

Please test and report any bug. Thanks
Reply With Quote
  #19  
Old November 27th, 2013, 08:49 AM
Pete's Avatar
Pete Pete is offline
OverSeer
 
Join Date: Jan 2001
Location: House
Posts: 14,266
Thanks Spud!

- Linux testing with a SA UPB serial PIM to a USB to Serial cable coming up as \dev\ttyUSB0 or \dev\ttyUSB1

- Updated two HS3 Linux boxes to V.46; Ubuntu 64bit and Ubuntu32bit.

- Updated remote directories on two above mentioned boxes and Zee.

- First box tested - HS3 32bit Ubuntu
a - ran HS3
b - deleted UPB events and devices
c - deleted legacy UPB plugin
d - shut down HS3
e - deleted files related to legacy UPB plugin
f - started HS3 and installed new UPB plugin
g - ran remote plugin on Ubuntu 64 bit
h - imported export UPB file
i - box created devices and links (sees dual load switches just fine)

- Second box tested - HS3 64bit Ubuntu
a - as above but ran the plugin locally the first time run
b - imported export file and it created devices and links
c - disabled plugin
d - deleted all UPB devices
e - shut down HS3 lite on Zee
f - ran remote UPB on Zee
g - connected and and it created all of the devices and links
h - probably some 50% slower than the 64bit and 32 bit remote Ubuntu UPB run.
i - working fine as above (just slower).
j - will create a few events today.

Updated Wintel HS3 box yesterday with HS3 V46. Will test UPB plugin on said box today using a Quatech serial server connected UPB serial PIM. Testing will be utilizing an HAI serial UPB PIM connecting via IP serial to network.
Reply With Quote
  #20  
Old November 27th, 2013, 04:41 PM
tam tam is offline
Seer
 
Join Date: Apr 2002
Location: Seattle
Posts: 19
3.0.0.5 reports as 3.0.0.4

Problem

After downloading the 3.0.0.5 PI, it is not showing as an option for install.
Only 3.0.0.4 can be seen in the PL Management screen.

See “Install Error?” below for info as to perhaps why.

Background
On the HS3 box a new UpStart file and export was created with two devices
-UMI
-Appliance module

The IDs and links were imported from the devices which function properly with my HS2 setup.
The UMI properly signals the Appliance module (powering a wallwart/LED) that either garage door is open.

HS3 3.0.0.43 was loaded and all UPB devices/links were deleted.

The available 3.0.0.4 PI was installed and pointed to the new UPE.
Logging was set to Debug.

HS3 sees the appliance module and properly reports it’s state

The links are correctly shown as they exist in the UpStart file, but do not update.

The UMI is not seen, but this is 3.0.0.4, not 5.


Please see attached UPBSpud3004-SS for screen shots.

BTW, I’m using Opera 12.16.


Install Error?
The following may be relevant to the issue.

Because I had forgotten to remove the “updater_override.txt” file, I had could not remove the 3.0.0.0 PI. Before realizing this I moved several UPB subdirectories to temp folders in the HS3 tree.

Eventually,”updater_override.txt” was deleted, 3.0.0.0 disappeared and installing the new PI (3.0.0.4) continued.

Thanks for your support and patience on this.

Terry
Attached Images
File Type: pdf UPBSpud3004-SS.pdf (102.2 KB, 15 views)
Reply With Quote
Reply

Bookmarks

Tags
simply automated, universal powerline bus, upb

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Kodi/XBMC Plug-in - Beta Testing spud Kodi/XBMC Plug-In (3P) 116 June 4th, 2017 08:51 AM
Kinect Plug-in - Beta Testing spud Kinect (3P) 147 May 10th, 2016 08:37 AM
EnvisaLink DSC Plug-in - HS2 Beta Testing spud Envisalink DSC Plugin (3P) 102 October 31st, 2013 07:48 PM
DirecTV Plug-in - Beta Testing spud DirecTV for HS3 (3P) 0 October 1st, 2013 07:23 AM
Plug-in is ready for beta testing rjh HAI/OnQ Panel (HS2) 8 September 6th, 2002 06:44 AM


All times are GMT -4. The time now is 03:59 PM.


Copyright HomeSeer Technologies, LLC