can you set the log level to debug, and post here the logs you get when you try to dim from the switch.
Announcement
Collapse
No announcement yet.
Set Hue Brightness via Link?
Collapse
X
-
Code:Oct-04 1:37:04 PM UPBSpud DEBUG PIM_RCVR:: Message already received and treated -- message ignored Oct-04 1:37:04 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU8905470E0924FFFFF2] Oct-04 1:37:03 PM UPBSpud DEBUG LINK[14]:: Got Link STOP FADE Oct-04 1:37:03 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU8904470E0924FFFFF3] Oct-04 1:37:01 PM UPBSpud DEBUG PIM_RCVR:: Message already received and treated -- message ignored Oct-04 1:37:01 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU8905470E0923640588] Oct-04 1:37:01 PM UPBSpud DEBUG LINK[14]:: Got Link START FADE Oct-04 1:37:01 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU8904470E0923640589] Oct-04 1:37:01 PM weatherXML Run between 0 23 Oct-04 1:37:01 PM weatherXML Run timer items Oct-04 1:36:56 PM UPBSpud DEBUG PIMADAPTER:: Confirmed message to device succeeded Oct-04 1:36:56 PM UPBSpud DEBUG PIM_SEND:: Message ID 8 confirmed sent successfully Oct-04 1:36:56 PM UPBSpud DEBUG PIM_SEND:: Got UPB Device NAK for LINK messge -- treating it as OK Oct-04 1:36:55 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=8) Oct-04 1:36:55 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[8814470CFF2100F1 ] Oct-04 1:36:55 PM UPBSpud DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left Oct-04 1:36:55 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 8 to PIM, retry count=0 Oct-04 1:36:55 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 8) Oct-04 1:36:55 PM UPBSpud DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet Oct-04 1:36:55 PM UPBSpud DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter Oct-04 1:36:54 PM UPBSpud DEBUG PIMADAPTER:: Confirmed message to device succeeded Oct-04 1:36:54 PM UPBSpud DEBUG PIM_SEND:: Message ID 7 confirmed sent successfully Oct-04 1:36:54 PM UPBSpud DEBUG PIM_SEND:: Got UPB Device NAK for LINK messge -- treating it as OK Oct-04 1:36:54 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=7) Oct-04 1:36:54 PM UPBSpud DEBUG LINK[14]:: Got Link STOP FADE Oct-04 1:36:54 PM UPBSpud DEBUG PIM_RCVR:: Received UPB command [PU8904470E0924FFFFF3] Oct-04 1:36:54 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[8814470BFF2100F2 ] Oct-04 1:36:54 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 7 to PIM, retry count=0 Oct-04 1:36:54 PM UPBSpud DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left Oct-04 1:36:54 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 7) Oct-04 1:36:54 PM UPBSpud DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet Oct-04 1:36:54 PM UPBSpud DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter Oct-04 1:36:53 PM UPBSpud DEBUG PIMADAPTER:: Confirmed message to device succeeded Oct-04 1:36:53 PM UPBSpud DEBUG PIM_SEND:: Message ID 6 confirmed sent successfully Oct-04 1:36:53 PM UPBSpud DEBUG PIM_SEND:: Got UPB Device NAK for LINK messge -- treating it as OK Oct-04 1:36:53 PM UPBSpud DEBUG PIM_SEND:: PIM ACK'd current message (ID=6) Oct-04 1:36:53 PM UPBSpud DEBUG PIM_SEND:: ABOUT_TO_SEND[8814470AFF2100F3 ] Oct-04 1:36:53 PM UPBSpud DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left Oct-04 1:36:53 PM UPBSpud DEBUG PIM_SEND:: Sending Message ID 6 to PIM, retry count=0 Oct-04 1:36:53 PM UPBSpud DEBUG PIM_SEND:: Extracted next message to send from queue (ID 6) Oct-04 1:36:53 PM UPBSpud DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet Oct-04 1:36:53 PM UPBSpud DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
_______________________________________________
HS3 : HSpro (3.0.0.460) on Win2012 (vm on ESXi)
Plugins: HSTouch, UPBSpud, Kinect, Nest, IFTTT, DirecTV, EasyTrigger, Imperihome, Zwave, RFXcom, UltraMon3, UltraWeatherBug3, UltraGCIR3, UltraLog3, UltraPioneer, PHLocation, Pushover, Pushalot, MCSSPrinklers S, JowiHue
Jon00 Plugins: Bluetooth Proximity, Performance Monitor, DB Chart, Links
Comment
-
I see the problem: when you hold/release the switch the messages sent are "Start Fade"/"Stop Fade". The problem is that the Stop Fade message does not specify a level, so the link device cannot be updated to a specific dim%
We have the same problem with UPB devices, but for devices the plugin sends a "State request" query whenever a "Stop fade" is received, so that the level can be updated.
Unfortunately this trick cannot be done for Links
One workaround would be to have at least one UPB device that would react to this link, so that instead of using the link device to update the Hue lights you could use the HS device for this UPB device. It could even be a UPB dimming module connected to nothing.
Comment
-
Thank you for looking into this, and for all your help. I guess I am at the end of this journey. I don't want to put dummy dimmers in place for this, so unfortunately, despite a very nice script that works perfectly with the web control, without the level reported from the UPB link it looks like the whole idea is not going to work.
I had plans of incorporating this more broadly with more switches. Do you think this is something that could be added to the UPB protocol? Would this be a bug report or a feature request?_______________________________________________
HS3 : HSpro (3.0.0.460) on Win2012 (vm on ESXi)
Plugins: HSTouch, UPBSpud, Kinect, Nest, IFTTT, DirecTV, EasyTrigger, Imperihome, Zwave, RFXcom, UltraMon3, UltraWeatherBug3, UltraGCIR3, UltraLog3, UltraPioneer, PHLocation, Pushover, Pushalot, MCSSPrinklers S, JowiHue
Jon00 Plugins: Bluetooth Proximity, Performance Monitor, DB Chart, Links
Comment
Comment