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
  #21  
Old May 6th, 2016, 11:17 AM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Quote:
Originally Posted by spud View Post
I'm confused by your test , do you try to change from High to Off, or from Off to High? because you said Off indicator lit, and then you say you press the Off button on the physical switch.

the following message is definitely weird:
May-06 6:41:07 AM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 8

It is as if the level on channel 0 was binary coded to represent the state of all indicators or something like that.

When this happens can you try to select the channel device on the management page, and click the poll button to see what state report message is sent in this case.
Sorry for the confusion. I am trying to come up with a test that is simple and doesn't have us moving between speeds etc on the fan which can confuse things. The messages generated in the log are when physically pressing the Off Button while the unit is already off (Off Indicator Lit in HS and on the Controller itself). The physical device status didn't change, the Off indicator stays on but in HS, suddenly the "High" LED and the "Off" LED were both lit. There is no reason for the High LED to be lit and it isn't in sync with the physical device when it shows it in HS that way. Polling doesn't fix it either. Whenever I poll the device, the response is always the say, regardless of the indicators:

Polling...
3 @ Polling: Downstairs Kitchen Ceiling Fan Speed - Off LED (Status is: 0)
2 @ Polling: Downstairs Kitchen Ceiling Fan Speed - High LED (Status is: 0)
1 @ Polling: Downstairs Kitchen Ceiling Fan Speed - Medium LED (Status is: 0)
0 @ Polling: Downstairs Kitchen Ceiling Fan Speed - Low LED (Status is: 0)
Done

-Travis
Reply With Quote
  #22  
Old May 6th, 2016, 02:25 PM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
Quote:
Originally Posted by Daweeze View Post
Sorry for the confusion. I am trying to come up with a test that is simple and doesn't have us moving between speeds etc on the fan which can confuse things. The messages generated in the log are when physically pressing the Off Button while the unit is already off (Off Indicator Lit in HS and on the Controller itself). The physical device status didn't change, the Off indicator stays on but in HS, suddenly the "High" LED and the "Off" LED were both lit. There is no reason for the High LED to be lit and it isn't in sync with the physical device when it shows it in HS that way. Polling doesn't fix it either. Whenever I poll the device, the response is always the say, regardless of the indicators:

Polling...
3 @ Polling: Downstairs Kitchen Ceiling Fan Speed - Off LED (Status is: 0)
2 @ Polling: Downstairs Kitchen Ceiling Fan Speed - High LED (Status is: 0)
1 @ Polling: Downstairs Kitchen Ceiling Fan Speed - Medium LED (Status is: 0)
0 @ Polling: Downstairs Kitchen Ceiling Fan Speed - Low LED (Status is: 0)
Done

-Travis
ok it's clear now, and I think I understand where the problem is. Could you do the following tests and post the logs for each:

(1) Starting with the controller being on High speed, press the off button on the physical switch

(2) Starting with the controller being off, press the High button on the physical switch

(3) Starting with the controller being on High speed, press the Low button on the physical switch

thanks
Reply With Quote
  #23  
Old May 6th, 2016, 08:15 PM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Hey Spud,

Here's a little more information I was able to gather today. I contacted Simply Automated and spoke to Millard. He ran through the setup with a test unit over there and he recreated the same issue. He doesn't know why the controller is sending out the value of 4 and 8 etc either. He suspects it is a firmware thing or the UpStart is not programming the controller correctly. Either way, he is going to figure out what the issue is and if it's intentional, then what the values mean for the interpretation by the Plug-In. That said, if you are on a road to figuring it out, let's keep going that way since you might be able to fix by ignoring a command or by interpreting what the values actually mean before they could fix the issue or identify it. Since UPB hardware isn't firmware End-User firmware upgradeable, if that's the issue, I would have to send them back in once they have a fix.

It appears that Channel 0 can have values of 0,1,2,4,8 or 100 as far as I can tell. He was expecting it to be 0 and 100 only.

Here's the info you asked for:

Quote:
Originally Posted by spud View Post
(1) Starting with the controller being on High speed, press the off button on the physical switch
May-06 5:12:20 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-06 5:12:20 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878608DC]
May-06 5:12:19 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 8
May-06 5:12:19 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878608DD]
May-06 5:12:19 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-06 5:12:19 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502048720FFFFC7]
May-06 5:12:19 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 3 from 0 to 100
May-06 5:12:18 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 100 to 0
May-06 5:12:18 PM UPBSpud DEBUG Device 135 transmitted link 4 with action Activate => Firing event 9686
May-06 5:12:17 PM UPBSpud DEBUG LINK[4]:: Got Link ACTIVATE
May-06 5:12:17 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402048720FFFFC8]

Quote:
Originally Posted by spud View Post
(2) Starting with the controller being off, press the High button on the physical switch
May-06 5:13:19 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-06 5:13:19 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878601E3]
May-06 5:13:19 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 100 to 1
May-06 5:13:19 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878601E4]
May-06 5:13:19 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-06 5:13:19 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502018720FFFFCA]
May-06 5:13:18 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 3 from 100 to 0
May-06 5:13:17 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 100
May-06 5:13:17 PM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 9335
May-06 5:13:17 PM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 8232
May-06 5:13:16 PM UPBSpud DEBUG LINK[1]:: Got Link ACTIVATE
May-06 5:13:16 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402018720FFFFCB]

Quote:
Originally Posted by spud View Post
(3) Starting with the controller being on High speed, press the Low button on the physical switch
May-06 5:14:40 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-06 5:14:40 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878604E0]
May-06 5:14:39 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 4
May-06 5:14:39 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878604E1]
May-06 5:14:39 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-06 5:14:39 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502038720FFFFC8]
May-06 5:14:38 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 2 from 0 to 100
May-06 5:14:38 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 100 to 0
May-06 5:14:38 PM UPBSpud DEBUG Device 135 transmitted link 3 with action Activate => Firing event 2737
May-06 5:14:37 PM UPBSpud DEBUG LINK[3]:: Got Link ACTIVATE
May-06 5:14:37 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402038720FFFFC9]

Thanks again for your help with this,

-Travis
Reply With Quote
  #24  
Old May 8th, 2016, 09:30 AM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
Can you test version 3.0.0.32 attached. In this version I have handled this device in a specific class that ignores the state reports, that should fix the issue.
Attached Files
File Type: zip UPBSpud_3-0-0-32.zip (230.3 KB, 4 views)
File Type: txt updater_override.txt (3.1 KB, 3 views)
Reply With Quote
  #25  
Old May 8th, 2016, 11:56 AM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Quote:
Originally Posted by spud View Post
Can you test version 3.0.0.32 attached. In this version I have handled this device in a specific class that ignores the state reports, that should fix the issue.
Hi Spud,

I updated to the .32 build and tested as requested. The LED Devices were no longer tracking so I deleted them and reimported the UpStart Export. They were recreated but remained the same. There is no updating of the LED status in HS in any of the 4 button modes. I redid the tests you asked before...results here:

(1) Starting with the controller being on High speed, press the off button on the physical switch



May-08 9:01:43 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 9:01:43 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878608DC]
May-08 9:01:42 AM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 8
May-08 9:01:42 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878608DD]
May-08 9:01:42 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 9:01:42 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502048720FFFFC7]
May-08 9:01:41 AM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 1 to 0
May-08 9:01:41 AM UPBSpud DEBUG Device 135 transmitted link 4 with action Activate => Firing event 9686
May-08 9:01:40 AM UPBSpud DEBUG LINK[4]:: Got Link ACTIVATE
May-08 9:01:40 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402048720FFFFC8]



(2) Starting with the controller being off, press the High button on the physical switch



May-08 9:02:46 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 9:02:46 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878601E3]
May-08 9:02:46 AM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 100 to 1
May-08 9:02:46 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878601E4]
May-08 9:02:46 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 9:02:46 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502018720FFFFCA]
May-08 9:02:45 AM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 8 to 100
May-08 9:02:45 AM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 9335
May-08 9:02:45 AM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 8232
May-08 9:02:44 AM UPBSpud DEBUG LINK[1]:: Got Link ACTIVATE
May-08 9:02:44 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402018720FFFFCB]



(3) Starting with the controller being on High speed, press the Low button on the physical switch



May-08 9:03:16 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 9:03:16 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878604E0]
May-08 9:03:15 AM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 4
May-08 9:03:15 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878604E1]
May-08 9:03:15 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 9:03:15 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502038720FFFFC8]
May-08 9:03:14 AM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 1 to 0
May-08 9:03:14 AM UPBSpud DEBUG Device 135 transmitted link 3 with action Activate => Firing event 2737
May-08 9:03:13 AM UPBSpud DEBUG LINK[3]:: Got Link ACTIVATE
May-08 9:03:13 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402038720FFFFC9]

Thanks again for your help with this...

-Travis
Reply With Quote
  #26  
Old May 8th, 2016, 12:34 PM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
ooops, sorry, bad copy/paste in the code I changed, could you try again with .33 attached. Please post the logs you get for the fan controller when you import.
Attached Files
File Type: zip UPBSpud_3-0-0-33.zip (230.3 KB, 3 views)
File Type: txt updater_override.txt (3.1 KB, 3 views)
Reply With Quote
  #27  
Old May 8th, 2016, 01:25 PM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Quote:
Originally Posted by spud View Post
ooops, sorry, bad copy/paste in the code I changed, could you try again with .33 attached. Please post the logs you get for the fan controller when you import.
Hi Spud,

Here's the entire log from the update to .33. Note that my Test Fan Device is the one that is UID 135. The LED Device Status is still not updating in this version, not sure if it was supposed to at this point though.....

Quote:
May-08 10:23:28 AM UPBSpud INFO Checking HS Devices Completed
May-08 10:23:23 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:23:23 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880F01CCFF260077]
May-08 10:23:22 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:23:22 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880E01CCFF260078]
May-08 10:23:22 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:23:21 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880D01CCFF260079]
May-08 10:23:21 AM UPBSpud DEBUG UPB_RCVR:: Recieved message from/for network #1 which is not a known network -- message ignored
May-08 10:23:20 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880C01CCFF26007A]
May-08 10:23:20 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:23:20 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880F0144FF26649B]
May-08 10:23:19 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:23:19 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880E0144FF26649C]
May-08 10:23:19 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:23:19 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880D0144FF26649D]
May-08 10:23:18 AM UPBSpud DEBUG UPB_RCVR:: Recieved message from/for network #1 which is not a known network -- message ignored
May-08 10:23:18 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU880C0144FF26649E]
May-08 10:23:17 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:23:17 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU0915015AFF22000066]
May-08 10:23:17 AM UPBSpud DEBUG UPB_RCVR:: Recieved message from/for network #1 which is not a known network -- message ignored
May-08 10:23:16 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU0914015AFF22000067]
May-08 10:23:16 AM Event Event Trigger "Lights - Automatic Dimming (Automation) Aubries Bedroom - Lighting - Automatic Dimming - Not Occupied"
May-08 10:23:07 AM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 10:23:06 AM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 10:23:06 AM UPBSpud DEBUG PIM_SEND:: Message ID 6 confirmed sent successfully
May-08 10:23:05 AM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=6)
May-08 10:23:05 AM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=6)
May-08 10:23:04 AM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140287FF302D ]
May-08 10:23:04 AM UPBSpud DEBUG PIM_SEND:: Sending Message ID 6 to PIM, retry count=0
May-08 10:23:03 AM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 6)
May-08 10:23:03 AM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 10:23:03 AM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 10:23:03 AM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 10:23:02 AM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (135)
May-08 10:23:02 AM UPBSpud DEBUG PIM_SEND:: Message ID 5 confirmed sent successfully
May-08 10:23:01 AM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=5)
May-08 10:23:00 AM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=5)
May-08 10:22:59 AM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140286FF302E ]
May-08 10:22:59 AM UPBSpud DEBUG PIM_SEND:: Sending Message ID 5 to PIM, retry count=0
May-08 10:22:59 AM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 5)
May-08 10:22:59 AM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 10:22:58 AM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 10:22:57 AM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 10:22:57 AM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (134)
May-08 10:22:56 AM UPBSpud DEBUG PIM_SEND:: Message ID 4 confirmed sent successfully
May-08 10:22:56 AM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=4)
May-08 10:22:56 AM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=4)
May-08 10:22:55 AM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140285FF302F ]
May-08 10:22:55 AM UPBSpud DEBUG PIM_SEND:: Sending Message ID 4 to PIM, retry count=0
May-08 10:22:55 AM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 4)
May-08 10:22:54 AM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 10:22:53 AM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 10:22:53 AM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 10:22:53 AM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (133)
May-08 10:22:52 AM UPBSpud DEBUG PIM_SEND:: Message ID 3 confirmed sent successfully
May-08 10:22:52 AM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=3)
May-08 10:22:51 AM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=3)
May-08 10:22:51 AM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140284FF3030 ]
May-08 10:22:50 AM UPBSpud DEBUG PIM_SEND:: Sending Message ID 3 to PIM, retry count=0
May-08 10:22:50 AM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 3)
May-08 10:22:50 AM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 10:22:49 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:22:49 AM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 10:22:49 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502008386000067]
May-08 10:22:49 AM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 10:22:48 AM UPBSpud DEBUG UPB_RCVR:: Unable to find LINK with ID 0
May-08 10:22:48 AM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (132)
May-08 10:22:48 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402008386000068]
May-08 10:22:48 AM UPBSpud DEBUG PIM_SEND:: Message ID 2 confirmed sent successfully
May-08 10:22:48 AM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=2)
May-08 10:22:48 AM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=2)
May-08 10:22:47 AM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 10:22:47 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU080502FF828600EA]
May-08 10:22:45 AM UPBSpud DEBUG DEVICE[130]:: Level changing on channel 0 from -1 to 0
May-08 10:22:44 AM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140283FF3031 ]
May-08 10:22:44 AM UPBSpud DEBUG PIM_SEND:: Sending Message ID 2 to PIM, retry count=0
May-08 10:22:43 AM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 2)
May-08 10:22:43 AM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 10:22:43 AM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU080402FF828600EB]
May-08 10:22:42 AM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 10:22:42 AM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 10:22:42 AM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Remote-IO (131)
May-08 10:22:42 AM UPBSpud DEBUG PIM_SEND:: Message ID 1 confirmed sent successfully
May-08 10:22:42 AM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=1)
May-08 10:22:42 AM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=1)
May-08 10:22:42 AM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140282FF3032 ]
May-08 10:22:42 AM UPBSpud DEBUG PIM_SEND:: Sending Message ID 1 to PIM, retry count=0
May-08 10:22:42 AM UPBSpud INFO Checking HS Devices Started
May-08 10:22:42 AM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 1)
May-08 10:22:42 AM UPBSpud INFO Import of UPStart file completed
May-08 10:22:42 AM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 10:22:42 AM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Pool - Speed (130)
May-08 10:22:42 AM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 10:22:42 AM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Room [Kitchen] -- 6 rooms now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Room [Pool] -- 5 rooms now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Room [Pool Control] -- 4 rooms now known
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: Channel Count mismatch on deviceID 131 between import file (2) and device (5) -- updating device
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Room [Aubrie's Bedroom] -- 3 rooms now known
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Room [Annie's Bedroom] -- 2 rooms now known
May-08 10:22:41 AM Plug-In Finished initializing plug-in UPBSpud
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Room [Master Bedroom] -- 1 rooms now known
May-08 10:22:41 AM UPBSpud DEBUG PIM_SEND:: Got ACK from PIM, but no current command to apply it toward
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Channel 2 Open (232)] -- 30 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Channel 2 Closed (231)] -- 29 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Compressor Relay - Off (230)] -- 28 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Compressor Relay - On (229)] -- 27 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Input 3 Open (228)] -- 26 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Input 3 Closed (227)] -- 25 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote IO Control - Speed Down (226)] -- 24 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote IO Control - Speed Up (225)] -- 23 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - Off (116)] -- 22 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - Low (115)] -- 21 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - Medium (114)] -- 20 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - High (113)] -- 19 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - Off (112)] -- 18 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - Low (111)] -- 17 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - Medium (110)] -- 16 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - High (109)] -- 15 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - Off (108)] -- 14 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - Low (107)] -- 13 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - Medium (106)] -- 12 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - High (105)] -- 11 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 20% (102)] -- 10 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 40% (101)] -- 9 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 60% (100)] -- 8 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 80% (99)] -- 7 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 0% (98)] -- 6 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 100% (97)] -- 5 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - Off (4)] -- 4 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - Low (3)] -- 3 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - Medium (2)] -- 2 links now known
May-08 10:22:41 AM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - High (1)] -- 1 links now known
May-08 10:22:41 AM UPBSpud INFO Import of UPStart file started
May-08 10:22:41 AM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[70028E ]
May-08 10:22:41 AM UPBSpud DEBUG UPB_RCVR:: PIM Port opened and installed
May-08 10:22:41 AM UPBSpud DEBUG PIM_SEND:: PIM Adapter starting sender thread
May-08 10:22:41 AM UPBSpud DEBUG UPB_MGR:: Activating media adapter
May-08 10:22:41 AM UPBSpud DEBUG UPB_MGR:: Initializing media adapter
May-08 10:22:41 AM UPBSpud INFO UPBSpud version 3.0.0.33
May-08 10:22:41 AM Info Plugin UPBSpud has connected. IP:127.0.0.1:55325
May-08 10:22:28 AM Updater Install/Update of package UPBSpud was successful.
May-08 10:22:28 AM Updater Warning File exists, not overwriting: C:\Program Files (x86)\HomeSeer HS3\Config\UPBSpud.ini
May-08 10:22:28 AM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\bin\UPBSpud\UPB4CSharp.dll
May-08 10:22:28 AM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\HSPI_UPBSpud.exe.config
May-08 10:22:28 AM Updater Extraction Complete.
May-08 10:22:28 AM Updater Extracting files from zip file: images.zip
May-08 10:22:28 AM Updater Copying file: C:\Program Files (x86)\HomeSeer HS3\HSPI_UPBSpud.exe
May-08 10:22:28 AM Updater Installing package UPBSpud
May-08 10:22:28 AM Updater Using local file: UPBSpud_3-0-0-33.zip
May-08 10:22:28 AM Updater Downloading update: UPBSpud
May-08 10:22:28 AM Updater Starting download of updates
Thanks,

-Travis
Reply With Quote
  #28  
Old May 8th, 2016, 02:09 PM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
Yes this version is supposed to fix the issue were the High channel device was updated incorrectly when you press physically the switch:

You should see some debug log messages like this one:
"Ignoring device state report for fan controller"

Could you try to delete your channel devices and then reimport or restart the plug-in. Thanks.
Reply With Quote
  #29  
Old May 8th, 2016, 06:46 PM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Quote:
Originally Posted by spud View Post
Yes this version is supposed to fix the issue were the High channel device was updated incorrectly when you press physically the switch:

You should see some debug log messages like this one:
"Ignoring device state report for fan controller"

Could you try to delete your channel devices and then reimport or restart the plug-in. Thanks.
Hi Spud,

That previous report was based off doing exactly what you asked. This time I deleted all 8 Devices for Unit 135 (Scene/Links and Channels) and restarted the Plug-In. Also I tested them as we had done before. I don't see that message anywhere when testing.

Here are the test results:

(1) Starting with the controller being on High speed, press the off button on the physical switch



May-08 3:52:15 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:52:15 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878608DC]
May-08 3:52:14 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 8
May-08 3:52:14 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878608DD]
May-08 3:52:14 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:52:14 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502048720FFFFC7]
May-08 3:52:13 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 1 to 0
May-08 3:52:13 PM UPBSpud DEBUG Device 135 transmitted link 4 with action Activate => Firing event 9686
May-08 3:52:12 PM UPBSpud DEBUG LINK[4]:: Got Link ACTIVATE
May-08 3:52:12 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402048720FFFFC8]



(2) Starting with the controller being off, press the High button on the physical switch



May-08 3:52:45 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:52:45 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878601E3]
May-08 3:52:44 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 100 to 1
May-08 3:52:44 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878601E4]
May-08 3:52:44 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:52:44 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502018720FFFFCA]
May-08 3:52:43 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 8 to 100
May-08 3:52:43 PM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 9335
May-08 3:52:43 PM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 8232
May-08 3:52:42 PM UPBSpud DEBUG LINK[1]:: Got Link ACTIVATE
May-08 3:52:42 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402018720FFFFCB]



(3) Starting with the controller being on High speed, press the Low button on the physical switch



May-08 3:53:11 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:53:11 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878604E0]
May-08 3:53:10 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 0 to 4
May-08 3:53:10 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878604E1]
May-08 3:53:10 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:53:10 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502038720FFFFC8]
May-08 3:53:09 PM UPBSpud DEBUG DEVICE[135]:: Level changing on channel 0 from 1 to 0
May-08 3:53:09 PM UPBSpud DEBUG Device 135 transmitted link 3 with action Activate => Firing event 2737
May-08 3:53:09 PM UPBSpud DEBUG LINK[3]:: Got Link ACTIVATE
May-08 3:53:09 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402038720FFFFC9]

Here are the log results from the initial restart of the Plug-In up until I began testing:



May-08 3:49:50 PM Z-Wave HomeSeer SmartStick+: Z-Wave Wake-Up 'No More Info' Notification sent to Node 11(Upstairs Office Loft Smoke Alarm - Root).
May-08 3:49:50 PM Event Event Trigger "Smoke & CO Alarms (Timers) Office Loft - Smoke - Heartbeat - Timer Reset"
May-08 3:49:50 PM Z-Wave HomeSeer SmartStick+: Device (Node 11) woke up and Poll Device for Upstairs Office Loft Smoke Alarm - Status was successfully sent.
May-08 3:49:50 PM Z-Wave HomeSeer SmartStick+: Wake-Up Notification Processing for Node 11 (Upstairs Office Loft Smoke Alarm - Root)
May-08 3:49:50 PM Z-Wave HomeSeer SmartStick+: Z-Wave Wake-Up Notification Received for Node 11
May-08 3:49:42 PM UPBSpud INFO Checking HS Devices Completed
May-08 3:49:19 PM UPBSpud INFO UPB Link Kitchen - Ceiling Fan - Off created
May-08 3:49:18 PM UPBSpud INFO UPB Link Kitchen - Ceiling Fan - Low created
May-08 3:49:17 PM UPBSpud INFO UPB Link Kitchen - Ceiling Fan - Medium created
May-08 3:49:16 PM UPBSpud INFO UPB Link Kitchen - Ceiling Fan - High created
May-08 3:49:15 PM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 3:49:15 PM UPBSpud INFO UPB Device Ceiling Fan - Ch 4 created
May-08 3:49:14 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 3:49:14 PM UPBSpud DEBUG PIM_SEND:: Message ID 6 confirmed sent successfully
May-08 3:49:14 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=6)
May-08 3:49:13 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=6)
May-08 3:49:13 PM UPBSpud INFO UPB Device Ceiling Fan - Ch 3 created
May-08 3:49:13 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140287FF302D ]
May-08 3:49:13 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 6 to PIM, retry count=0
May-08 3:49:13 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 6)
May-08 3:49:13 PM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 3:49:12 PM UPBSpud INFO UPB Device Ceiling Fan - Ch 2 created
May-08 3:49:12 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 3:49:12 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 3:49:12 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (135)
May-08 3:49:12 PM UPBSpud DEBUG PIM_SEND:: Message ID 5 confirmed sent successfully
May-08 3:49:12 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=5)
May-08 3:49:11 PM UPBSpud INFO UPB Device Ceiling Fan - Ch 1 created
May-08 3:49:11 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=5)
May-08 3:49:11 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140286FF302E ]
May-08 3:49:11 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 5 to PIM, retry count=0
May-08 3:49:11 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 5)
May-08 3:49:11 PM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 3:49:10 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 3:49:09 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 3:49:09 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (134)
May-08 3:49:09 PM UPBSpud DEBUG PIM_SEND:: Message ID 4 confirmed sent successfully
May-08 3:49:09 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=4)
May-08 3:49:08 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=4)
May-08 3:49:07 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140285FF302F ]
May-08 3:49:07 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 4 to PIM, retry count=0
May-08 3:49:07 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 4)
May-08 3:49:07 PM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 3:49:06 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 3:49:06 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 3:49:05 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (133)
May-08 3:49:05 PM UPBSpud DEBUG PIM_SEND:: Message ID 3 confirmed sent successfully
May-08 3:49:04 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=3)
May-08 3:49:04 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=3)
May-08 3:49:04 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140284FF3030 ]
May-08 3:49:03 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 3 to PIM, retry count=0
May-08 3:49:03 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 3)
May-08 3:49:02 PM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 3:49:01 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 3:49:01 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:49:01 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 3:49:01 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502008386000067]
May-08 3:49:00 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Ceiling Fan (132)
May-08 3:49:00 PM UPBSpud DEBUG UPB_RCVR:: Unable to find LINK with ID 0
May-08 3:49:00 PM UPBSpud DEBUG PIM_SEND:: Message ID 2 confirmed sent successfully
May-08 3:49:00 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402008386000068]
May-08 3:49:00 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=2)
May-08 3:49:00 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=2)
May-08 3:48:59 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-08 3:48:59 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU080502FF828600EA]
May-08 3:48:57 PM UPBSpud DEBUG DEVICE[130]:: Level changing on channel 0 from -1 to 0
May-08 3:48:56 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140283FF3031 ]
May-08 3:48:56 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 2 to PIM, retry count=0
May-08 3:48:56 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 2)
May-08 3:48:56 PM UPBSpud DEBUG PIM_SEND:: Resuming sending after waiting a refreshing 600ms
May-08 3:48:55 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU080402FF828600EB]
May-08 3:48:55 PM UPBSpud DEBUG PIM_SEND:: Pausing because last command expected a reply
May-08 3:48:55 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 3:48:55 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Remote-IO (131)
May-08 3:48:55 PM UPBSpud DEBUG PIM_SEND:: Message ID 1 confirmed sent successfully
May-08 3:48:55 PM UPBSpud DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=1)
May-08 3:48:55 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=1)
May-08 3:48:54 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[07140282FF3032 ]
May-08 3:48:54 PM UPBSpud INFO Checking HS Devices Started
May-08 3:48:54 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 1 to PIM, retry count=0
May-08 3:48:54 PM UPBSpud INFO Import of UPStart file completed
May-08 3:48:54 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 1)
May-08 3:48:54 PM UPBSpud DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
May-08 3:48:54 PM UPBSpud DEBUG UPB_MGR:: STATE_QUEUE:: Sending state query for device Pool - Speed (130)
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 135 is not a keypad, ignoring button record
May-08 3:48:54 PM Plug-In Finished initializing plug-in UPBSpud
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Room [Kitchen] -- 6 rooms now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Room [Pool] -- 5 rooms now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Room [Pool Control] -- 4 rooms now known
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: Channel Count mismatch on deviceID 131 between import file (2) and device (5) -- updating device
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 134 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Room [Aubrie's Bedroom] -- 3 rooms now known
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 133 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Room [Annie's Bedroom] -- 2 rooms now known
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG UPStart_IMPORT:: device 132 is not a keypad, ignoring button record
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Room [Master Bedroom] -- 1 rooms now known
May-08 3:48:54 PM UPBSpud DEBUG PIM_SEND:: Got ACK from PIM, but no current command to apply it toward
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Channel 2 Open (232)] -- 30 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Channel 2 Closed (231)] -- 29 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Compressor Relay - Off (230)] -- 28 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Compressor Relay - On (229)] -- 27 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Input 3 Open (228)] -- 26 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote-IO - Input 3 Closed (227)] -- 25 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote IO Control - Speed Down (226)] -- 24 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Remote IO Control - Speed Up (225)] -- 23 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - Off (116)] -- 22 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - Low (115)] -- 21 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - Medium (114)] -- 20 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Master Bedroom - Ceiling Fan - High (113)] -- 19 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - Off (112)] -- 18 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - Low (111)] -- 17 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - Medium (110)] -- 16 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Annie's Bedroom - Ceiling Fan - High (109)] -- 15 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - Off (108)] -- 14 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - Low (107)] -- 13 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - Medium (106)] -- 12 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Aubrie's Bedroom - Ceiling Fan - High (105)] -- 11 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 20% (102)] -- 10 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 40% (101)] -- 9 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 60% (100)] -- 8 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 80% (99)] -- 7 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 0% (98)] -- 6 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Pool - Speed 100% (97)] -- 5 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - Off (4)] -- 4 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - Low (3)] -- 3 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - Medium (2)] -- 2 links now known
May-08 3:48:54 PM UPBSpud DEBUG NETWORK[2]:: Added Link [Kitchen - Ceiling Fan - High (1)] -- 1 links now known
May-08 3:48:54 PM UPBSpud INFO Import of UPStart file started
May-08 3:48:54 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[70028E ]
May-08 3:48:54 PM UPBSpud DEBUG UPB_RCVR:: PIM Port opened and installed
May-08 3:48:54 PM UPBSpud DEBUG PIM_SEND:: PIM Adapter starting sender thread
May-08 3:48:54 PM UPBSpud DEBUG UPB_MGR:: Activating media adapter
May-08 3:48:54 PM UPBSpud DEBUG UPB_MGR:: Initializing media adapter
May-08 3:48:54 PM UPBSpud INFO UPBSpud version 3.0.0.33
May-08 3:48:54 PM Info Plugin UPBSpud has connected. IP:127.0.0.1:60716

Thanks again for all of your help with the troubleshooting of this issue!!

-Travis

Last edited by Daweeze; May 8th, 2016 at 06:59 PM.
Reply With Quote
  #30  
Old May 9th, 2016, 02:10 PM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Hey Spud,

Anything else you needed me to do? I will be able to test again later this evening.

Thanks,

-Travis
Reply With Quote
  #31  
Old May 9th, 2016, 03:38 PM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
could you try again with version 3.0.0.34

I tried importing your upe file with version .33, and got the following error:
ERROR UPStart_IMPORT:: Unable to create tailored device instance -- No parameterless constructor defined for this object.

It is now fixed in .34, but what is weird is that this error is not in your logs. Have you ever seen it?
When you install make sure both HSPI_UPBSpud.exe and bin/UPBSpud/UPB4CSharp.dll are updated and that you don't have any other UPB4CSharp.dll in the HS3 folder.

thanks
Attached Files
File Type: zip UPBSpud_3-0-0-34.zip (230.3 KB, 3 views)
File Type: txt updater_override.txt (3.1 KB, 3 views)
Reply With Quote
  #32  
Old May 9th, 2016, 10:37 PM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Quote:
Originally Posted by spud View Post
Yes this version is supposed to fix the issue were the High channel device was updated incorrectly when you press physically the switch:

You should see some debug log messages like this one:
"Ignoring device state report for fan controller"
I am now seeing these messages with version 3.0.0.34.

Quote:
Originally Posted by spud View Post
Could you try to delete your channel devices and then reimport or restart the plug-in. Thanks.

could you try again with version 3.0.0.34
I did this just as you asked.

Quote:
Originally Posted by spud View Post
I tried importing your upe file with version .33, and got the following error:
ERROR UPStart_IMPORT:: Unable to create tailored device instance -- No parameterless constructor defined for this object.

It is now fixed in .34, but what is weird is that this error is not in your logs. Have you ever seen it?
I don't believe that I have. For reference, I am using UpStart 8.0 Build 47 for my most recent Export files.


Quote:
Originally Posted by spud View Post
When you install make sure both HSPI_UPBSpud.exe and bin/UPBSpud/UPB4CSharp.dll are updated and that you don't have any other UPB4CSharp.dll in the HS3 folder.

thanks
Both files updated. There was not an occurance of UPB4CSharp.dll in the HS3 Folder.

Neither activating the Links or using the Controller changes the Ceiling Fan LED Indicators in HS3 anymore. I can see the commands in the Log that look like they should be changing them but the status is now "Off" all of the time.

I did notice that I am no longer seeing this message that I am used to seeing after a level change in the log:

"DEBUG FAN_CONTROLLER_DEVICE[135]:: Confirmed request to set device to level succeedded -- updating internal state".

Maybe you accidentally filtered the state change that was needed?

Here's the test logs with this version:

(1) Starting with the controller being on High speed, press the off button on the physical switch



May-09 7:09:31 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-09 7:09:31 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878608DC]
May-09 7:09:31 PM UPBSpud DEBUG FAN_CONTROLLER_DEVICE[135]:: Ignoring device state report for fan controller
May-09 7:09:31 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878608DD]
May-09 7:09:31 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-09 7:09:31 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502048720FFFFC7]
May-09 7:09:30 PM UPBSpud DEBUG FAN_CONTROLLER_DEVICE[135]:: Level changing on channel 0 from 100 to 0
May-09 7:09:30 PM UPBSpud DEBUG Device 135 transmitted link 4 with action Activate => Firing event 9686
May-09 7:09:29 PM UPBSpud DEBUG LINK[4]:: Got Link ACTIVATE
May-09 7:09:29 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402048720FFFFC8]



(2) Starting with the controller being off, press the High button on the physical switch



May-09 7:10:07 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-09 7:10:07 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878601E3]
May-09 7:10:07 PM UPBSpud DEBUG FAN_CONTROLLER_DEVICE[135]:: Ignoring device state report for fan controller
May-09 7:10:07 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878601E4]
May-09 7:10:07 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-09 7:10:07 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502018720FFFFCA]
May-09 7:10:06 PM UPBSpud DEBUG FAN_CONTROLLER_DEVICE[135]:: Level changing on channel 0 from 0 to 100
May-09 7:10:06 PM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 9335
May-09 7:10:06 PM UPBSpud DEBUG Device 135 transmitted link 1 with action Activate => Firing event 8232
May-09 7:10:05 PM UPBSpud DEBUG LINK[1]:: Got Link ACTIVATE
May-09 7:10:05 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402018720FFFFCB]



(3) Starting with the controller being on High speed, press the Low button on the physical switch



May-09 7:10:41 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-09 7:10:41 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08050200878604E0]
May-09 7:10:41 PM UPBSpud DEBUG FAN_CONTROLLER_DEVICE[135]:: Ignoring device state report for fan controller
May-09 7:10:41 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU08040200878604E1]
May-09 7:10:41 PM UPBSpud DEBUG UPB_RCVR:: Message already received and treated -- message ignored
May-09 7:10:41 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890502038720FFFFC8]
May-09 7:10:40 PM UPBSpud DEBUG FAN_CONTROLLER_DEVICE[135]:: Level changing on channel 0 from 100 to 0
May-09 7:10:40 PM UPBSpud DEBUG Device 135 transmitted link 3 with action Activate => Firing event 2737
May-09 7:10:40 PM UPBSpud DEBUG LINK[3]:: Got Link ACTIVATE
May-09 7:10:40 PM UPBSpud DEBUG UPB_RCVR:: Received UPB command [PU890402038720FFFFC9]

Thanks,

-Travis
Reply With Quote
  #33  
Old May 10th, 2016, 08:29 AM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
ok, I think we are almost there
please test version 3.0.0.35 attached
Attached Files
File Type: zip UPBSpud_3-0-0-35.zip (230.3 KB, 3 views)
File Type: txt updater_override.txt (3.1 KB, 3 views)
Reply With Quote
  #34  
Old May 10th, 2016, 09:37 AM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Hi Spud,

Thanks you. You nailed it. I couldn't get it to fail even once. I even turned the HS Light Indicators on manually in all modes so they were all lit and it corrected the condition with the next UPB Activation of a Link for Speed or Off change. I changed HS Light Indicator devices to Status Only and it continues to work so this is perfect. I will still followup with any issues as well as with whatever work Simply Automated comes back at me with but this looks to be squashed.

Thanks a gain for your time and help with this. Top notch support as always.

-Travis
Reply With Quote
  #35  
Old May 10th, 2016, 02:14 PM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
Cool, thanks for all the testing.
Reply With Quote
  #36  
Old May 11th, 2016, 04:58 PM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Hi Spud,

Everything is still good here, thanks! I just received an email from Simply Automated explaining the UPB message you have programmed the PI to ignore. I am not sure if you want to play with it to fully support the switch or not without the workaround but here is the information:

----------
Good Day Travis,

Doing a little review of the Fan Controller (UCQF) state functions, I now see the state report is a value of 2 bytes that define the 16 various states of the 4 LEDs. Note, the first of the 2 bytes is not used (always 0).

When the state is reported by the unit, it transmits the basic/standard UPB status message, where the last byte (before the check sum) indicates which LEDs are lit.

For example if no LEDs are lit, the value is 0 (e.g. 00000000 binary, or 00 hex). If all the LEDs are lit, then the value is 15 (00001111, or 0F).

Therefore, the High, Medium, Low and Off values (per factory default) would be 1, 2, 4 and 8 (decimal), which is what UPStart tells us in Log View.

If the Fan Controller was configured to use the light-load output (4th LED), then all 16 values of the byte would cover all possible (including unusual/undesirable) states, as follows:

HEX: Fan and Light State
00: fan off, light off
01: fan high, light off
02: fan medium, light off
03: fan high and medium, light off
04: fan low, light off
05: fan high and low, light off
06: fan medium and low, light off
07: fan high, medium and low, light off
08: fan off, light on
09: fan high, light on
0A: fan medium, light on
0B: fan high and medium, light on
0C: fan low, light on
0D: fan high and low, light on
0E: fan medium and low, light on
0F: fan high, medium and low, light on

The unusual/undesirable states of the fan being on at multiple speeds (e.g. medium and low), results in the fan being on high as the capacitor network built into the unit for speed control would pass current roughly equal to high speed.

I hope this helps,

Millard Schewe

Simply Automated, Inc.
----------

What do you think? I'm ok with staying as is or testing if you want to go that route.

Thanks,

-Travis
Reply With Quote
  #37  
Old May 11th, 2016, 05:19 PM
spud's Avatar
spud spud is offline
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,624
Quote:
Originally Posted by Daweeze View Post

What do you think? I'm ok with staying as is or testing if you want to go that route.
I say we stay as is for now!
Reply With Quote
  #38  
Old May 11th, 2016, 07:25 PM
Daweeze's Avatar
Daweeze Daweeze is online now
Seer Deluxe
 
Join Date: Dec 2009
Location: North Bay
Posts: 408
Quote:
Originally Posted by spud View Post
I say we stay as is for now!
Sounds good. At least you have the information should you need it in the future. It may be needed for other circumstances when the controller is setup differently in UpStart.

-Travis
Reply With Quote
Reply

Bookmarks

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
HAI / Simply Automated GadgetBoySI Lighting & Primary Technology Discussion 4 May 13th, 2010 05:58 PM
Simply Automated PIM - USB GadgetBoySI HomeSeer UPB Plug-In (Beta) 6 May 9th, 2010 06:37 AM
Simply Automated USB PIM Oman HomeSeer UPB Plug-In (Beta) 2 November 22nd, 2008 07:08 PM
Simply Automated UPB - Random reprogramming GlennWo HomeSeer UPB Plug-In (Beta) 5 April 15th, 2008 12:29 PM
Help on UPB 3 way using Simply Automated switches Richard HomeSeer UPB Plug-In (Beta) 26 July 16th, 2007 10:50 PM


All times are GMT -4. The time now is 01:25 AM.


Copyright HomeSeer Technologies, LLC