All Activity

I'll take a look to see if I can find something - I did not change any code relating to this, but there must be a bug. I have no way to test as I am travelling Can you send a full debug log - the issue may occur earlier than what you included - ideally as a log zip file

@Panda88I notice something odd that just started happening with the latest version. I have a message that plays through the speaker hubs saying "Someone is at the front door". This works fine after a restart of the Yolink node server but sometime later the behavior changes to saying " Basement fridge or freezer door is open" which is another one of my messages that was selected and played later in the day. If I go into the AC and play any message on the speaker hub screen it always plays the same incorrect message even when I select a different message to play from the AC. If I restart the Yolink node server, everything then works ok until some time later after another different message is played. It seems to me that the message selection gets stuck and will not continue to update. The first time or two that a message is selected in the AC after a node server restart it works ok but then it gets stuck and won't play a different select message, just plays the one that is stuck. Gary I don't know if this helps but here is a log file when it fails to change messages 2025-07-05 10:47:13.368 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-07-05 10:47:13.368 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-07-05 10:47:13.368 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '8b4c1604002268', 'cmd': 'MESSAGE', 'value': '0', 'uom': '25', 'query': {}} from Polyglot 2025-07-05 10:47:13.368 Command udi_interface INFO udiYoSpeakerHubV2:setMessage: udiYoSpeakerHub setMessage 2025-07-05 10:47:13.368 Command udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV4 0 None 2025-07-05 10:47:13.368 Command udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV4 to 0 to Polyglot 2025-07-05 10:47:13.368 Command udi_interface.node DEBUG node:reportDriver: Updating value to 0 2025-07-05 10:47:13.368 Command udi_interface INFO udiYoSpeakerHubV2:setMessage: udiYoSpeakerHub setMessage 0 Someone is at the Front Door 2025-07-05 10:47:13.377 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV4', 'value': '0', 'uom': 25, 'text': None}]} 2025-07-05 10:47:13.414 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV4 to 0 UOM 25 2025-07-05 10:47:59.499 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-07-05 10:47:59.499 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-07-05 10:47:59.499 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '8b4c1604002268', 'cmd': 'PLAY', 'query': {}} from Polyglot 2025-07-05 10:47:59.499 Command udi_interface INFO udiYoSpeakerHubV2:playMessage: udiYoSpeakerHub playMessage 2025-07-05 10:47:59.499 Command udi_interface DEBUG yolinkSpeakerHubV3:playAudio: SpeakerHub - playAudio 2025-07-05 10:47:59.499 Command udi_interface DEBUG yolinkSpeakerHubV3:playAudio: playAudio: {'method': 'SpeakerHub.playAudio', 'targetDevice': 'd88b4c1604002268', 'token': '36D6FD222DDB834F455F516C82A6412A', 'params': {'tone': 'Tip', 'volume': 10, 'repeat': 0, 'message': 'Basement Fridge or Freezer Door is Open'}} 2025-07-05 10:47:59.499 Command udi_interface DEBUG yoLink_init_V3:publish_data: Publish Data to Queue: {'method': 'SpeakerHub.playAudio', 'targetDevice': 'd88b4c1604002268', 'token': '36D6FD222DDB834F455F516C82A6412A', 'params': {'tone': 'Tip', 'volume': 10, 'repeat': 0, 'message': 'Basement Fridge or Freezer Door is Open'}} 2025-07-05 10:47:59.500 Thread-3821 (transfer_data) udi_interface DEBUG yoLink_init_V3:transfer_data: Starting publish_data: 2025-07-05 10:47:59.500 Thread-3821 (transfer_data) udi_interface DEBUG yoLink_init_V3:time_tracking: time_track_going in: 1751726879500, d88b4c1604002268, {'d88b4c02000a9794': [], 'd88b4c02000aac97': [], 'd88b4c02000aa795': [], 'd88b4c02000a98dd': [], 'd88b4c02000eb8a5': [], 'd88b4c02000a9751': [], 'd88b4c02000a9c43': [], 'd88b4c02000aaca9': [], 'd88b4c010005aaf5': [], 'd88b4c02000eb8dd': [], 'd88b4c02000a9776': [], 'd88b4c0200037958': [], 'd88b4c020003794a': [], 'd88b4c02000aa808': [], 'd88b4c01000c2e21': [], 'd88b4c160400190b': [], 'd88b4c1604002268': [1751726560223, 1751726638698, 1751726757672, 1751726778691, 1751726798312], 'd88b4c1604002182': [], 'd88b4c1604003e76': [], 'd88b4c010008a200': [], 'd88b4c02000797cf': [], 'd88b4c040006a122': [], 'd88b4c01000abf03': [], 'd88b4c010005482d': []} 2025-07-05 10:47:59.501 Thread-3821 (transfer_data) udi_interface DEBUG yoLink_init_V3:time_tracking: Adding 0 delay to t_now 1751726879500 = 1751726879500 to TimeTrack - dev delay=0, all_delay=0, dev2dev=0 2025-07-05 10:47:59.501 Thread-3821 (transfer_data) udi_interface DEBUG yoLink_init_V3:time_tracking: TimeTrack after: time 1751726879500 dev: d88b4c1604002268 delay: 0 - {'d88b4c02000a9794': [], 'd88b4c02000aac97': [], 'd88b4c02000aa795': [], 'd88b4c02000a98dd': [], 'd88b4c02000eb8a5': [], 'd88b4c02000a9751': [], 'd88b4c02000a9c43': [], 'd88b4c02000aaca9': [], 'd88b4c010005aaf5': [], 'd88b4c02000eb8dd': [], 'd88b4c02000a9776': [], 'd88b4c0200037958': [], 'd88b4c020003794a': [], 'd88b4c02000aa808': [], 'd88b4c01000c2e21': [], 'd88b4c160400190b': [], 'd88b4c1604002268': [1751726638698, 1751726757672, 1751726778691, 1751726798312, 1751726879500], 'd88b4c1604002182': [], 'd88b4c1604003e76': [], 'd88b4c010008a200': [], 'd88b4c02000797cf': [], 'd88b4c040006a122': [], 'd88b4c01000abf03': [], 'd88b4c010005482d': []} 2025-07-05 10:47:59.501 Thread-3821 (transfer_data) udi_interface DEBUG yoLink_init_V3:transfer_data: publish_data: yl-home/a2c4d5280e864c3fa820376edc5c5d59/d88b4c1604002268/request - {"method": "SpeakerHub.playAudio", "targetDevice": "d88b4c1604002268", "token": "36D6FD222DDB834F455F516C82A6412A", "params": {"tone": "Tip", "volume": 10, "repeat": 0, "message": "Basement Fridge or Freezer Door is Open"}, "time": "1751726879501"} 2025-07-05 10:47:59.500 Command udi_interface DEBUG yoLink_init_V3:publish_data: publishThread - starting 2025-07-05 10:47:59.590 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_publish: on_publish 2025-07-05 10:47:59.721 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: on_message: {'method': 'SpeakerHub.playAudio', 'targetDevice': 'd88b4c1604002268', 'token': '36D6FD222DDB834F455F516C82A6412A', 'params': {'tone': 'Tip', 'volume': 10, 'repeat': 0, 'message': 'Basement Fridge or Freezer Door is Open'}, 'time': '1751726879501'} 2025-07-05 10:47:59.721 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: Message received and put in queue (size : 1) 2025-07-05 10:47:59.721 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: Creating threads to handle the received messages 2025-07-05 10:47:59.721 Thread-3822 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: Received message - Q size=0 2025-07-05 10:47:59.721 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: 1 on_message threads starting 2025-07-05 10:47:59.721 Thread-3822 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: process_message : {'method': 'SpeakerHub.playAudio', 'targetDevice': 'd88b4c1604002268', 'token': '36D6FD222DDB834F455F516C82A6412A', 'params': {'tone': 'Tip', 'volume': 10, 'repeat': 0, 'message': 'Basement Fridge or Freezer Door is Open'}, 'time': '1751726879501'} 2025-07-05 10:47:59.721 Thread-3822 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: process_message for d88b4c1604002268: {'method': 'SpeakerHub.playAudio', 'targetDevice': 'd88b4c1604002268', 'token': '36D6FD222DDB834F455F516C82A6412A', 'params': {'tone': 'Tip', 'volume': 10, 'repeat': 0, 'message': 'Basement Fridge or Freezer Door is Open'}, 'time': '1751726879501'} yl-home/a2c4d5280e864c3fa820376edc5c5d59/d88b4c1604002268/request 2025-07-05 10:47:59.722 Thread-3822 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: porcessing request - no action: {'method': 'SpeakerHub.playAudio', 'targetDevice': 'd88b4c1604002268', 'token': '36D6FD222DDB834F455F516C82A6412A', 'params': {'tone': 'Tip', 'volume': 10, 'repeat': 0, 'message': 'Basement Fridge or Freezer Door is Open'}, 'time': '1751726879501'} 2025-07-05 10:47:59.847 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: on_message: {'code': '000000', 'time': 1751726879811, 'msgid': '1751726879501', 'method': 'SpeakerHub.playAudio', 'data': {}, 'targetDevice': 'd88b4c1604002268'} 2025-07-05 10:47:59.848 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: Message received and put in queue (size : 1) 2025-07-05 10:47:59.848 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: Creating threads to handle the received messages 2025-07-05 10:47:59.848 Thread-3823 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: Received message - Q size=0 2025-07-05 10:47:59.848 paho-mqtt-client-a2c4d5280e864c3fa820376edc5c5d59 udi_interface DEBUG yoLink_init_V3:on_message: 1 on_message threads starting 2025-07-05 10:47:59.848 Thread-3823 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: process_message : {'code': '000000', 'time': 1751726879811, 'msgid': '1751726879501', 'method': 'SpeakerHub.playAudio', 'data': {}, 'targetDevice': 'd88b4c1604002268'} 2025-07-05 10:47:59.848 Thread-3823 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: process_message for d88b4c1604002268: {'code': '000000', 'time': 1751726879811, 'msgid': '1751726879501', 'method': 'SpeakerHub.playAudio', 'data': {}, 'targetDevice': 'd88b4c1604002268'} yl-home/a2c4d5280e864c3fa820376edc5c5d59/d88b4c1604002268/response 2025-07-05 10:47:59.848 Thread-3823 (process_message) udi_interface DEBUG yoLink_init_V3:process_message: porcessing response: {'code': '000000', 'time': 1751726879811, 'msgid': '1751726879501', 'method': 'SpeakerHub.playAudio', 'data': {}, 'targetDevice': 'd88b4c1604002268'} 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface INFO udiYoSpeakerHubV2:updateStatus: updateStatus - speakerHub 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG udi_interface:write: SpeakerHub update data {'code': '000000', 'time': 1751726879811, 'msgid': '1751726879501', 'method': 'SpeakerHub.playAudio', 'data': {}, 'targetDevice': 'd88b4c1604002268'} 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG yolink_mqtt_classV3:updateCallbackStatus: SpeakerHub - updateCallbackStatus : {'code': '000000', 'time': 1751726879811, 'msgid': '1751726879501', 'method': 'SpeakerHub.playAudio', 'data': {}, 'targetDevice': 'd88b4c1604002268'} 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG yolink_mqtt_classV3:updateCallbackStatus: Method detected 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG yolink_mqtt_classV3:Status: Status : {'code': '000000', 'time': 1751726879811, 'msgid': '1751726879501', 'method': 'SpeakerHub.playAudio', 'data': {}, 'targetDevice': 'd88b4c1604002268'} 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG yolink_mqtt_classV3:Status: code selected 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG yolink_mqtt_classV3:updateCallbackStatus: Do Nothing for now 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV0 10 None 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV0 to 10 to Polyglot 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 10 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV1 1 None 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV1 to 1 to Polyglot 2025-07-05 10:47:59.849 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 1 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV2 0 None 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV2 to 0 to Polyglot 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV3 0 None 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV3 to 0 to Polyglot 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV4 0 None 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV4 to 0 to Polyglot 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV5 0 None 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV5 to 0 to Polyglot 2025-07-05 10:47:59.850 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV0', 'value': '10', 'uom': 107, 'text': None}]} 2025-07-05 10:47:59.850 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2025-07-05 10:47:59.851 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV1', 'value': '1', 'uom': 25, 'text': None}]} 2025-07-05 10:47:59.851 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : ST 1 None 2025-07-05 10:47:59.851 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV2', 'value': '0', 'uom': 25, 'text': None}]} 2025-07-05 10:47:59.851 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set ST to 1 to Polyglot 2025-07-05 10:47:59.852 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV3', 'value': '0', 'uom': 25, 'text': None}]} 2025-07-05 10:47:59.852 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 1 2025-07-05 10:47:59.852 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV4', 'value': '0', 'uom': 25, 'text': None}]} 2025-07-05 10:47:59.852 Thread-3823 (process_message) udi_interface DEBUG udiYolinkLib:my_setDriver: my_setDriver : GV20 0 None 2025-07-05 10:47:59.852 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV5', 'value': '0', 'uom': 107, 'text': None}]} 2025-07-05 10:47:59.852 Thread-3823 (process_message) udi_interface.node DEBUG node:setDriver: 8b4c1604002268:SpeakerHub master bathroom Reporting set GV20 to 0 to Polyglot 2025-07-05 10:47:59.853 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'ST', 'value': '1', 'uom': 25, 'text': None}]} 2025-07-05 10:47:59.853 Thread-3823 (process_message) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2025-07-05 10:47:59.864 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '8b4c1604002268', 'driver': 'GV20', 'value': '0', 'uom': 25, 'text': None}]} 2025-07-05 10:47:59.880 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV0 to 10 UOM 107 2025-07-05 10:47:59.968 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV1 to 1 UOM 25 2025-07-05 10:48:00.008 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV2 to 0 UOM 25 2025-07-05 10:48:00.065 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV3 to 0 UOM 25 2025-07-05 10:48:00.112 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV4 to 0 UOM 25 2025-07-05 10:48:00.171 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV5 to 0 UOM 107 2025-07-05 10:48:00.213 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: ST to 1 UOM 25 2025-07-05 10:48:00.268 MQTT udi_interface.interface INFO interface:_message: Successfully set 8b4c1604002268 :: GV20 to 0 UOM 25

There's almost nothing on the screen to really interact with. From my understanding this can be a controller and you can link other devices to it, or at least that's how I read the instructions but in homeseer I could always detect a button press or a hold down or a fast on etc. and was able to set an interaction based on that. I bought these a really long time ago but there is no support for them that I'm aware of. I do have a switch close to my tank and I'm thinking about putting a zooz zen32 switch in its place. That will at least allow me to get some special buttons back to use with my tank. I'm surprised no one has a good keypad only option for Zwave either AC power or a handheld like this one. Eaton made one and I had a few of those but there was always something lacking with them and I had a hard time to get them to work reliably. Thanks for that reminder on the backing up of Zwave devices, homeseer also had that same issue that you had to back up the zwave stuff separately and I got burned on a restore once and had to start from scratch. When doing a backup maybe they should have a popup to warn you to also back that up and have it included in the zip you download so you have the most current information for the restore. It was a real let down that the backup wasn't all there. It's literally an entire day pissed away having to relearn the devices and then fix the events/programs.

I'm not familiar with ratgdo, so you may want to ask in that sub forum.

Can you post a screenshot of the ZY110 Controller window. It's remote possibility that those pending writes might be causing an issue. You should get that cleaned up. If you're still then having issues with BW8510US I would then exclude it, do a factory reset on it then do an include. Also, don't forget to do a Zwave backup any time you make changes to your Zwave devices as Zwave is NOT included in the regular eisy backup

Those are different devices, Not sure why they haven't finished with writing. I like that idea of moving the other stuff out of the main into another folder. It is way to crowded and hard to find stuff. I'm gonna keep plugging away on this, sooner or later I'll get these things working or find a different keypad option.

I noticed you have pending writes to ZY107 and ZY105. Are those your BW8510US? If so, put them into the linking mode, one at a time, and right click on the device and click on write updates. Being that Zwave devices are designed to work with various controllers, the names on its node may not reflect its actual purpose. You might also end up with nodes that you don't need in which case you can create a folder and move them into the folder in order to clean up your device tree.

Yes I am using the usb board that UD recommended. Everything is working fine so far. The 2 kwikset 916 locks took some work but I finally got through that. It only creates those 2 items at the bottom left. So all I can select in the events is like a battery query or a device responding. It should allow me to pick any of the 8 buttons dependiing on how I push the buttons but those options just don't show up. I have 2 of these and they both do the same thing. I've tried reinterviewing and switching compatibility mode.

Are you using the UD Zwave/Matter board in your eisy? Do you have other Zwave devices that are working correctly? In your device tree do you see nodes for the BW8510US?

@apostolakisl Thank-you! John

I'm using the Eisy 5.91. I just got this about a week ago and have almost everything working perfectly except those 2 remotes. They are kinda important to me to automate my fish tank stuff when I need to turn pumps and lights oon and off while I clean it.

Are you using an EISY, POLISY or ISY994, and what's the firmware version?

@JoelW Be sure to follow the replace PLM procedure. See attached Replace PLM Procedure (EISY or POLISY).pdf

You can view the programs in a backup. Identifying a specific program and restoring it is rather painful. Copy one of your backups to a separate directory in case things go bad. The 1st screenshot below is the result of an UnZip of one of my backups. Use 7Zip or something similar to open your backup .Zip. Windows explorer will NOT work. You will see the file "uuid.xx.xx.xx.xx.xx.xx.zip". Unzip this to your directory. Open the "uuid.xx.xx.xx.xx.xx.xx.zip" file in 7Zip as well. Extract the CONF folder. Within the CONF folder you will find a D2D folder. This contains your program files. The "*.PGM" files are in XML format. Your challenge will be to identify which file you want to restore (not easy). You can export your current programs to try to determine the program numbering (ID) and what is missing. Beware that Exporting the entire "My Programs Folder" produces an XML file that can't be interrogated by any XML viewer that I have found (format error). I have been successful in exporting individual program folders (non-nested). I'm quite sure this is not the answer you were hoping for. Unfortunately, it's all I can offer. Directory showing Backup Zip, UUID Zip, and CONF file folder CONF Folder contents: D2D Folder Containing Program Files 000A.PGM Contents

.... ok, scratch my original answer... I saw remotelinc in the text and not Remotec BW8510US.. I'm not a zwave user so can't help.

I've been migrating away from homeseer and have a few 8 button remotec scene controllers. When I add it in it shows up as a controller and an awake icon. There doesn't seem to be a way to detect the scenes when you push one of the buttons. I've tried redetecting it, interviewiing it, used compatibility mode etc, but I am just stuck and have run out of ideas how to get these things to work. Has anyone used these and can offer some insight on how to get them to work. Thanks

Verify the easy IP address with your router. Then click on the add button in the Launcher and add the IP address manually.

No, it does not have a value. it is a rated garage door opener. Interestingly, my other eisy (at another house) displays a value for a similar ratgdo node and I can customize it. Should I delete the node from eisy then add back?

You don't need parenthesis at all for this. There is no functional difference between either of the two options you showed as well as no parenthesis at all. Mostly you would use parenthesis when you have two sets of conditions not connected by the same and/or. ie. (1 and 2 and 3) or (4 and 5) (1 or 2 or 3) and (4 or 5) the following are all functionally identical (1 and 2 and 3) (1 and 2) and 3 1 and (2 and 3) 1 and 2 and 3 (1 and 3) and 2

Bug discovered in version 1.2.9 - 1.2.10. Causes failure on back navigation from folders on home tab and automations tab. Fixed in 1.2.11

I don't think you are mistaken.

Is there anyway to view programs in a backup without restoring the backup to an ISY unit? I deleted a whole series of programs about a year ago and want them back now. Restoring that backup, however would get rid of a bunch of changes I want. I suppose I could make a backup, restore the old one, copy the programs and the restore the backup I just made. However, I really don't want to do that. Seems like more opportunities for things to go wrong.

FYI... Reflashing the EISY and restoring Backup worked great.

I'd try un-plugging power to the eisy, wait 10 seconds, and replug, retry

I'm Following along on this page => https://developer.isy.io/docs/getstarted/dev_env going to use VS Code on my windows machine. I'm going to be remote because I can't put a monitor and keyboard on my device -- its in a closet. When I get to step #2 its not finding the IDE script. I've update the eISY to 14.3 and installed the dev packages from the admin screen but when I connect its not finding this script. Thanks Andy