toddhutch

Ok, so hopefully this helps someone. This has been working the whole time, I didn't realize you had to hit the buttons to set the values on the right side.

One more note, is that the interview default time doesn't appear to be working the way I expected. I set the interview timeout to 20 seconds, but it is taking a very long time.

Last troubleshooting attempt was to turn of S2 and include the device. The device acted the same I could query, but I was unable to make changes in the console admin that would be sent to the thermostat. So I wonder if the S2 Secure inclusion is working correctly.

I don't know if this makes a difference but the S2 key starts with 00 and when I put in the S2 key it trims the zeros. I'm new to Z-Wave and haven't done this before so I don't know if this is normal behavior.

New to Z-Wave so hopefully I'm just doing something wrong, but after 4 hours of messing around with this, I'm posting. Eisy Firmware 5.8.4 Z-wave Matter dongle from Universal Devices I have the event viewer running, and I see the queries coming through and the updates showing when I make changes on the device. The changes made in the Admin console never make it to the thermostat. I've tired to hit the write changes button, just leave it, and they just reset to what is on the device. It's like it is on read only mode. I've excluded the device and added it back 3 times, and each time when I add it. I see non-conforming features. I attached the event view level 3 below. Any help would be appreciated. Based on what I've read this thermostat is supposed to justt work. But I'm new to this, and I don't have another zwave device to test with. Fri 09/20/2024 08:36:48 PM : Z-Wave Listening for Z-Wave devices to remove from the network Fri 09/20/2024 08:37:00 PM : Create REST U7 [/rest/profiles/ns/3/connection] Fri 09/20/2024 08:37:00 PM : Create REST U7 [/rest/profiles/ns/0/connection] Fri 09/20/2024 08:37:01 PM : Z-Wave Z-Wave device detected, start removing from network Fri 09/20/2024 08:37:01 PM : Z-Wave Z-Wave device removed Fri 09/20/2024 08:37:01 PM : REMOVING NODE [ZY005_309] Fri 09/20/2024 08:37:01 PM : [All ] Writing 0 bytes to devices Fri 09/20/2024 08:37:01 PM : REMOVING PRIMARY NODE [ZY005_1] Fri 09/20/2024 08:37:01 PM : [All ] Writing 0 bytes to devices Fri 09/20/2024 08:37:01 PM : Z-Wave Idle Fri 09/20/2024 08:37:01 PM : Z-Wave Idle Fri 09/20/2024 08:37:21 PM : ---- Start Adding Devices - S2 Standard --- Fri 09/20/2024 08:37:21 PM : [ZWAVE-INCL-S2STD] Start Include with S0/S2 or non-secure Fri 09/20/2024 08:37:21 PM : [ZWAVE-INCL-S2STD] Added 'CommandAdded' callback 0xe26ce28 Fri 09/20/2024 08:37:21 PM : Z-Wave Listening for Z-Wave devices to add to the network Fri 09/20/2024 08:37:32 PM : Z-Wave Z-Wave device detected, start adding to network Fri 09/20/2024 08:37:32 PM : Z-Wave Z-Wave device detected, retrieving info Fri 09/20/2024 08:37:32 PM : [ZW-INTERVIEW-38 ] Add interview running entry for 6 Fri 09/20/2024 08:37:32 PM : Z-Wave Z-Wave device added Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=32 (0x20) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=49 (0x31) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=64 (0x40) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=66 (0x42) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=67 (0x43) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=68 (0x44) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=69 (0x45) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=85 (0x55) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=89 (0x59) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=90 (0x5A) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=94 (0x5E) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=108 (0x6C) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=112 (0x70) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=113 (0x71) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=114 (0x72) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=115 (0x73) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=122 (0x7A) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=128 (0x80) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=129 (0x81) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=133 (0x85) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=134 (0x86) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=135 (0x87) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=142 (0x8E) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=159 (0x9F) : uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: processing ccId=0x9F uid=6.0 Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: Adding 'requestedKeys' callback Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: Adding 'publicKey' callback Fri 09/20/2024 08:37:32 PM : [ZWAVE-INCL-S2STD] Callback to requestedKeys/publicKey added Fri 09/20/2024 08:37:32 PM : Z-Wave Idle Fri 09/20/2024 08:37:32 PM : Z-Wave Idle Fri 09/20/2024 08:37:32 PM : Z-Wave Idle Fri 09/20/2024 08:37:34 PM : [ZWAVE-INCL-S2STD] In 'requestedKeys' callback Fri 09/20/2024 08:37:34 PM : [ZWAVE-INCL-S2STD] Unregistering 'requestedKeys' callback for 6 Fri 09/20/2024 08:37:34 PM : [ZWAVE-INCL-S2STD] 'requestedKeys': last included device = 6 (expect 6) Fri 09/20/2024 08:37:34 PM : [ZWAVE-INCL-S2STD] 'requestedKeys': reading key requests for 6 Fri 09/20/2024 08:37:36 PM : [Device 6] Waiting on S2 inclusion process to complete (timeout in 5200 ticks) Fri 09/20/2024 08:37:38 PM : [Device 6] Waiting on interview complete (timeout in 5160) Fri 09/20/2024 08:37:40 PM : [Device 6] Waiting on interview complete (timeout in 5120) Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] 'requestedKeys': getting last included device (expect 6) Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] 'requestedKeys': last included device = 6 (expect 6) Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] 'requestedKeys': reading key requests for 6 Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] Granting 'S2 Authenticated' to 6.0 Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] Granting keys for 6.0 complete Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] In 'publicKey' callback for 6 Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] Unregistering 'publicKey' callback for 6 Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] 'verifyPublicKey': last included device = 6 (expect 6) Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] 'publicKey': reading public key for 6 Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] 'publicKey': reading public key verify flag for 6 Fri 09/20/2024 08:37:42 PM : [ZWAVE-INCL-S2STD] Public key verification required for device 6, show Verify Key Popup Fri 09/20/2024 08:37:42 PM : [Device 6] Waiting on interview complete (timeout in 5197) Fri 09/20/2024 08:37:44 PM : [Device 6] Waiting on interview complete (timeout in 5180) Fri 09/20/2024 08:37:46 PM : [ZWAVE-INCL-S2STD] 'publicKey': getting last included device (expect 6) Fri 09/20/2024 08:37:46 PM : [ZWAVE-INCL-S2STD] 'publicKey': last included device = 6 (expect 6) Fri 09/20/2024 08:37:46 PM : [ZWAVE-INCL-S2STD] 'publicKey': reading public key for 6 Fri 09/20/2024 08:37:46 PM : [ZWAVE-INCL-S2STD] 'publicKey': reading public key verify flag for 6 Fri 09/20/2024 08:37:46 PM : [ZWAVE-INCL-S2STD] 'publicKey': user verified public key for 6 Fri 09/20/2024 08:37:46 PM : [ZWAVE-INCL-S2STD] 'publicKey': writing verified public key for 6 Fri 09/20/2024 08:37:46 PM : [ZWAVE-INCL-S2STD] 'publicKey': Done (success) for 6 Fri 09/20/2024 08:37:46 PM : [Device 6] Finished Waiting on S2, continuing interview (timeout in 400 ticks) Fri 09/20/2024 08:37:46 PM : [Device 6] Waiting on interview complete (timeout in 400) Fri 09/20/2024 08:37:48 PM : [Device 6] Waiting on interview complete (timeout in 360) Fri 09/20/2024 08:37:50 PM : [Device 6] Waiting on interview complete (timeout in 320) Fri 09/20/2024 08:37:52 PM : [Device 6] Waiting on interview complete (timeout in 280) Fri 09/20/2024 08:37:54 PM : [Device 6] Waiting on interview complete (timeout in 400) Fri 09/20/2024 08:37:56 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:37:58 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:00 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:38:02 PM : [Device 6] Waiting on interview complete (timeout in 374) Fri 09/20/2024 08:38:04 PM : [Device 6] Waiting on interview complete (timeout in 376) Fri 09/20/2024 08:38:06 PM : [Device 6] Waiting on interview complete (timeout in 379) Fri 09/20/2024 08:38:08 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:38:10 PM : [Device 6] Waiting on interview complete (timeout in 397) Fri 09/20/2024 08:38:12 PM : [Device 6] Waiting on interview complete (timeout in 393) Fri 09/20/2024 08:38:14 PM : [Device 6] Waiting on interview complete (timeout in 396) Fri 09/20/2024 08:38:16 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:18 PM : [Device 6] Waiting on interview complete (timeout in 359) Fri 09/20/2024 08:38:20 PM : [Device 6] Waiting on interview complete (timeout in 388) Fri 09/20/2024 08:38:22 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:24 PM : [Device 6] Waiting on interview complete (timeout in 363) Fri 09/20/2024 08:38:26 PM : [Device 6] Waiting on interview complete (timeout in 380) Fri 09/20/2024 08:38:28 PM : [Device 6] Waiting on interview complete (timeout in 396) Fri 09/20/2024 08:38:30 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:38:32 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:34 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:38:36 PM : [Device 6] Waiting on interview complete (timeout in 390) Fri 09/20/2024 08:38:38 PM : [Device 6] Waiting on interview complete (timeout in 394) Fri 09/20/2024 08:38:40 PM : [Device 6] Waiting on interview complete (timeout in 397) Fri 09/20/2024 08:38:42 PM : [Device 6] Waiting on interview complete (timeout in 381) Fri 09/20/2024 08:38:44 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:46 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:38:47 PM : [Device 6] Waiting on interview complete (timeout in 396) Fri 09/20/2024 08:38:49 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:51 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CF 11 01 LTONRR (01) Fri 09/20/2024 08:38:51 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:38:51 PM : [D2D EVENT ] Event [4F 87 EF 1] [DON] [1] uom=0 prec=-1 Fri 09/20/2024 08:38:51 PM : [4F 87 EF 1 ] DON 1 Fri 09/20/2024 08:38:51 PM : [D2D EVENT ] Event [4F 87 EF 1] [ST] [255] uom=100 prec=0 Fri 09/20/2024 08:38:51 PM : [4F 87 EF 1 ] ST 255 (uom=100 prec=0) Fri 09/20/2024 08:38:51 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST Converted values Event=100 Condition=100 prec=0 Fri 09/20/2024 08:38:51 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST op=1 Event(val=255 uom=100 prec=0) is Condition(val=100 uom=51 prec=0) --> true Fri 09/20/2024 08:38:51 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:52 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CF 11 01 LTONRR (01) Fri 09/20/2024 08:38:52 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:38:52 PM : [D2D EVENT ] Event [4F 87 EF 1] [DON] [1] uom=0 prec=-1 Fri 09/20/2024 08:38:52 PM : [4F 87 EF 1 ] DON 1 Fri 09/20/2024 08:38:52 PM : [INST-SRX ] 02 50 4F.87.EF 34.E6.20 40 11 01 LTONRR (01) Fri 09/20/2024 08:38:52 PM : [Std-Cleanup ] 4F.87.EF-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Fri 09/20/2024 08:38:52 PM : [INST-DUP 2 ] Previous message ignored. Fri 09/20/2024 08:38:52 PM : [INST-SRX ] 02 50 4F.87.EF 11.01.01 CF 06 00 (00) Fri 09/20/2024 08:38:52 PM : [Std-Group ] 4F.87.EF-->11.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:38:52 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:38:52 PM : [INST-SRX ] 02 50 4F.87.EF 11.01.01 CF 06 00 (00) Fri 09/20/2024 08:38:52 PM : [Std-Group ] 4F.87.EF-->11.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:38:52 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:38:53 PM : [Device 6] Waiting on interview complete (timeout in 372) Fri 09/20/2024 08:38:55 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:38:56 PM : [INST-SRX ] 02 50 4F.C6.6C 00.00.01 CF 11 00 LTONRR (00) Fri 09/20/2024 08:38:56 PM : [Std-Group ] 4F.C6.6C-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:38:56 PM : [D2D EVENT ] Event [4F C6 6C 1] [DON] [0] uom=0 prec=-1 Fri 09/20/2024 08:38:56 PM : [4F C6 6C 1 ] DON 0 Fri 09/20/2024 08:38:56 PM : [D2D EVENT ] Event [4F C6 6C 1] [ST] [255] uom=100 prec=0 Fri 09/20/2024 08:38:56 PM : [4F C6 6C 1 ] ST 255 (uom=100 prec=0) Fri 09/20/2024 08:38:56 PM : [INST-SRX ] 02 50 4F.C6.6C 34.E6.20 40 11 01 LTONRR (01) Fri 09/20/2024 08:38:56 PM : [Std-Cleanup ] 4F.C6.6C-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Fri 09/20/2024 08:38:56 PM : [INST-DUP 2 ] Previous message ignored. Fri 09/20/2024 08:38:57 PM : [INST-SRX ] 02 50 4F.C6.6C 11.01.01 CF 06 00 (00) Fri 09/20/2024 08:38:57 PM : [Std-Group ] 4F.C6.6C-->11.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:38:57 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:38:57 PM : [Device 6] Waiting on interview complete (timeout in 393) Fri 09/20/2024 08:38:59 PM : [Device 6] Waiting on interview complete (timeout in 397) Fri 09/20/2024 08:39:01 PM : [Device 6] Waiting on interview complete (timeout in 367) Fri 09/20/2024 08:39:03 PM : [Device 6] Waiting on interview complete (timeout in 379) Fri 09/20/2024 08:39:05 PM : [Device 6] Waiting on interview complete (timeout in 381) Fri 09/20/2024 08:39:06 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CB 13 01 LTOFFRR(01) Fri 09/20/2024 08:39:06 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=2 Fri 09/20/2024 08:39:06 PM : [D2D EVENT ] Event [4F 87 EF 1] [DOF] [1] uom=0 prec=-1 Fri 09/20/2024 08:39:06 PM : [4F 87 EF 1 ] DOF 1 Fri 09/20/2024 08:39:06 PM : [D2D EVENT ] Event [4F 87 EF 1] [ST] [0] uom=100 prec=0 Fri 09/20/2024 08:39:06 PM : [4F 87 EF 1 ] ST 0 (uom=100 prec=0) Fri 09/20/2024 08:39:06 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST Converted values Event=0 Condition=100 prec=0 Fri 09/20/2024 08:39:06 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST op=1 Event(val=0 uom=100 prec=0) is Condition(val=100 uom=51 prec=0) --> false Fri 09/20/2024 08:39:07 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CF 13 01 LTOFFRR(01) Fri 09/20/2024 08:39:07 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:07 PM : [D2D EVENT ] Event [4F 87 EF 1] [DOF] [1] uom=0 prec=-1 Fri 09/20/2024 08:39:07 PM : [4F 87 EF 1 ] DOF 1 Fri 09/20/2024 08:39:07 PM : [INST-SRX ] 02 50 4F.87.EF 34.E6.20 40 13 01 LTOFFRR(01) Fri 09/20/2024 08:39:07 PM : [Std-Cleanup ] 4F.87.EF-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Fri 09/20/2024 08:39:07 PM : [INST-DUP 2 ] Previous message ignored. Fri 09/20/2024 08:39:07 PM : [INST-SRX ] 02 50 4F.87.EF 13.01.01 CF 06 00 (00) Fri 09/20/2024 08:39:07 PM : [Std-Group ] 4F.87.EF-->13.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:07 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:39:07 PM : [Device 6] Waiting on interview complete (timeout in 390) Fri 09/20/2024 08:39:07 PM : [INST-SRX ] 02 50 4F.87.EF 13.01.01 CF 06 00 (00) Fri 09/20/2024 08:39:07 PM : [Std-Group ] 4F.87.EF-->13.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:07 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:39:09 PM : [Device 6] Waiting on interview complete (timeout in 396) Fri 09/20/2024 08:39:11 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:39:13 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:39:15 PM : [Device 6] Waiting on interview complete (timeout in 397) Fri 09/20/2024 08:39:17 PM : [Device 6] Waiting on interview complete (timeout in 391) Fri 09/20/2024 08:39:19 PM : [Device 6] Waiting on interview complete (timeout in 397) Fri 09/20/2024 08:39:21 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:39:23 PM : [Device 6] Waiting on interview complete (timeout in 397) Fri 09/20/2024 08:39:25 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:39:27 PM : [Device 6] Waiting on interview complete (timeout in 394) Fri 09/20/2024 08:39:29 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:39:31 PM : [Device 6] Waiting on interview complete (timeout in 390) Fri 09/20/2024 08:39:33 PM : [Device 6] Waiting on interview complete (timeout in 397) Fri 09/20/2024 08:39:35 PM : [Device 6] Waiting on interview complete (timeout in 400) Fri 09/20/2024 08:39:37 PM : [Device 6] Waiting on interview complete (timeout in 389) Fri 09/20/2024 08:39:37 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CF 11 01 LTONRR (01) Fri 09/20/2024 08:39:37 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:37 PM : [D2D EVENT ] Event [4F 87 EF 1] [DON] [1] uom=0 prec=-1 Fri 09/20/2024 08:39:37 PM : [4F 87 EF 1 ] DON 1 Fri 09/20/2024 08:39:37 PM : [D2D EVENT ] Event [4F 87 EF 1] [ST] [255] uom=100 prec=0 Fri 09/20/2024 08:39:37 PM : [4F 87 EF 1 ] ST 255 (uom=100 prec=0) Fri 09/20/2024 08:39:37 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST Converted values Event=100 Condition=100 prec=0 Fri 09/20/2024 08:39:37 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST op=1 Event(val=255 uom=100 prec=0) is Condition(val=100 uom=51 prec=0) --> true Fri 09/20/2024 08:39:38 PM : [INST-SRX ] 02 50 4F.C6.6C 00.00.01 CF 13 00 LTOFFRR(00) Fri 09/20/2024 08:39:38 PM : [Std-Group ] 4F.C6.6C-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:38 PM : [D2D EVENT ] Event [4F C6 6C 1] [DOF] [0] uom=0 prec=-1 Fri 09/20/2024 08:39:38 PM : [4F C6 6C 1 ] DOF 0 Fri 09/20/2024 08:39:38 PM : [D2D EVENT ] Event [4F C6 6C 1] [ST] [0] uom=100 prec=0 Fri 09/20/2024 08:39:38 PM : [4F C6 6C 1 ] ST 0 (uom=100 prec=0) Fri 09/20/2024 08:39:38 PM : [INST-SRX ] 02 50 4F.C6.6C 34.E6.20 40 13 01 LTOFFRR(01) Fri 09/20/2024 08:39:38 PM : [Std-Cleanup ] 4F.C6.6C-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Fri 09/20/2024 08:39:38 PM : [INST-DUP 2 ] Previous message ignored. Fri 09/20/2024 08:39:38 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CB 11 01 LTONRR (01) Fri 09/20/2024 08:39:38 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=2 Fri 09/20/2024 08:39:38 PM : [D2D EVENT ] Event [4F 87 EF 1] [DON] [1] uom=0 prec=-1 Fri 09/20/2024 08:39:38 PM : [4F 87 EF 1 ] DON 1 Fri 09/20/2024 08:39:38 PM : [INST-SRX ] 02 50 4F.C6.6C 34.E6.20 46 13 01 LTOFFRR(01) Fri 09/20/2024 08:39:38 PM : [Std-Cleanup ] 4F.C6.6C-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Fri 09/20/2024 08:39:38 PM : [D2D EVENT ] Event [4F C6 6C 1] [DOF] [0] uom=0 prec=-1 Fri 09/20/2024 08:39:38 PM : [4F C6 6C 1 ] DOF 0 Fri 09/20/2024 08:39:38 PM : [INST-SRX ] 02 50 4F.C6.6C 13.01.01 CF 06 00 (00) Fri 09/20/2024 08:39:38 PM : [Std-Group ] 4F.C6.6C-->13.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:38 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:39:38 PM : [INST-SRX ] 02 50 4F.87.EF 34.E6.20 46 11 01 LTONRR (01) Fri 09/20/2024 08:39:38 PM : [Std-Cleanup ] 4F.87.EF-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Fri 09/20/2024 08:39:38 PM : [D2D EVENT ] Event [4F 87 EF 1] [DON] [0] uom=0 prec=-1 Fri 09/20/2024 08:39:38 PM : [4F 87 EF 1 ] DON 0 Fri 09/20/2024 08:39:39 PM : [INST-SRX ] 02 50 4F.87.EF 11.01.01 CF 06 00 (00) Fri 09/20/2024 08:39:39 PM : [Std-Group ] 4F.87.EF-->11.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:39 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:39:39 PM : [Device 6] Waiting on interview complete (timeout in 396) Fri 09/20/2024 08:39:39 PM : [INST-SRX ] 02 50 4F.87.EF 11.01.01 CF 06 00 (00) Fri 09/20/2024 08:39:39 PM : [Std-Group ] 4F.87.EF-->11.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:39:39 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:39:41 PM : [Device 6] Waiting on interview complete (timeout in 396) Fri 09/20/2024 08:39:43 PM : [Device 6] Waiting on interview complete (timeout in 393) Fri 09/20/2024 08:39:45 PM : [Device 6] Waiting on interview complete (timeout in 395) Fri 09/20/2024 08:39:47 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:39:49 PM : [Device 6] Waiting on interview complete (timeout in 390) Fri 09/20/2024 08:39:51 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:39:53 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:39:55 PM : [Device 6] Waiting on interview complete (timeout in 396) Fri 09/20/2024 08:39:57 PM : [Device 6] Waiting on interview complete (timeout in 399) Fri 09/20/2024 08:39:59 PM : [Device 6] Waiting on interview complete (timeout in 393) Fri 09/20/2024 08:40:01 PM : [Device 6] Waiting on interview complete (timeout in 398) Fri 09/20/2024 08:40:03 PM : [Device 6] Waiting on interview complete (timeout in 378) Fri 09/20/2024 08:40:05 PM : [Device 6] Waiting on interview complete (timeout in 338) Fri 09/20/2024 08:40:06 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CF 13 01 LTOFFRR(01) Fri 09/20/2024 08:40:06 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:40:06 PM : [D2D EVENT ] Event [4F 87 EF 1] [DOF] [1] uom=0 prec=-1 Fri 09/20/2024 08:40:06 PM : [4F 87 EF 1 ] DOF 1 Fri 09/20/2024 08:40:06 PM : [D2D EVENT ] Event [4F 87 EF 1] [ST] [0] uom=100 prec=0 Fri 09/20/2024 08:40:06 PM : [4F 87 EF 1 ] ST 0 (uom=100 prec=0) Fri 09/20/2024 08:40:06 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST Converted values Event=0 Condition=100 prec=0 Fri 09/20/2024 08:40:06 PM : [D2D-CMP 0013] STS [4F 87 EF 1] ST op=1 Event(val=0 uom=100 prec=0) is Condition(val=100 uom=51 prec=0) --> false Fri 09/20/2024 08:40:06 PM : [INST-SRX ] 02 50 4F.87.EF 00.00.01 CF 13 01 LTOFFRR(01) Fri 09/20/2024 08:40:06 PM : [Std-Group ] 4F.87.EF-->Group=1, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:40:06 PM : [D2D EVENT ] Event [4F 87 EF 1] [DOF] [1] uom=0 prec=-1 Fri 09/20/2024 08:40:06 PM : [4F 87 EF 1 ] DOF 1 Fri 09/20/2024 08:40:06 PM : [INST-SRX ] 02 50 4F.87.EF 34.E6.20 40 13 01 LTOFFRR(01) Fri 09/20/2024 08:40:06 PM : [Std-Cleanup ] 4F.87.EF-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Fri 09/20/2024 08:40:06 PM : [INST-DUP 2 ] Previous message ignored. Fri 09/20/2024 08:40:06 PM : [INST-SRX ] 02 50 4F.87.EF 13.01.01 CF 06 00 (00) Fri 09/20/2024 08:40:06 PM : [Std-Group ] 4F.87.EF-->13.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:40:06 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:40:07 PM : [Device 6] Waiting on interview complete (timeout in 298) Fri 09/20/2024 08:40:07 PM : [INST-SRX ] 02 50 4F.87.EF 13.01.01 CF 06 00 (00) Fri 09/20/2024 08:40:07 PM : [Std-Group ] 4F.87.EF-->13.01.01, Max Hops=3, Hops Left=3 Fri 09/20/2024 08:40:07 PM : [INST-INFO ] Previous message ignored. Fri 09/20/2024 08:40:09 PM : [Device 6] Waiting on interview complete (timeout in 258) Fri 09/20/2024 08:40:11 PM : [Device 6] Waiting on interview complete (timeout in 218) Fri 09/20/2024 08:40:13 PM : [Device 6] Waiting on interview complete (timeout in 178) Fri 09/20/2024 08:40:15 PM : [Device 6] Waiting on interview complete (timeout in 138) Fri 09/20/2024 08:40:17 PM : [Device 6] Waiting on interview complete (timeout in 98) Fri 09/20/2024 08:40:19 PM : [Device 6] Waiting on interview complete (timeout in 58) Fri 09/20/2024 08:40:21 PM : [Device 6] Waiting on interview complete (timeout in 18) Fri 09/20/2024 08:40:23 PM : [Device 6] Waiting on interview complete (timeout in 0) Fri 09/20/2024 08:40:23 PM : [ZW-INTERVIEW-38 ] Device 6 : Interview Done with some non-conforming features : total=24 successful=22 attempted=24 Fri 09/20/2024 08:40:23 PM : ZWAVE-WORKQ-35 Queue sync device 6 (initialize) Fri 09/20/2024 08:40:23 PM : ZWAVE-WORKQ-35 Start sync device 6 Fri 09/20/2024 08:40:23 PM : [ZWAVE-SYNC 6] Rebuilding all existing ISY files/objects for Z-Wave device Fri 09/20/2024 08:40:23 PM : [SYNC-DEVICE 6.0] Root database 4.8.6 mfg=1051.17.9 Fri 09/20/2024 08:40:23 PM : [SYNC-DEVICE 6.0] Set commands will now be accepted by the controller Fri 09/20/2024 08:40:23 PM : [ZWAVE-SYNC 6] Not multichannel Fri 09/20/2024 08:40:23 PM : [SYNC-DEVICE 6] Initializing associations to ISY Fri 09/20/2024 08:40:23 PM : ZWAVE-WORKQ-36 Queue write device updates for node 6, full=false Fri 09/20/2024 08:40:23 PM : ZWAVE-WORKQ-35 Finished sync device 6 Fri 09/20/2024 08:40:23 PM : ZWAVE-WORKQ-36 Start write device updates for node 6, full=false Fri 09/20/2024 08:40:23 PM : [ZW-TX-Q 00238 6.0 ] Association Get group=1 Fri 09/20/2024 08:40:23 PM : [ZW-DONE 00238 6.0 ] Association Get group=1 Fri 09/20/2024 08:40:23 PM : [ZW-TX-Q 00239 6.0 ] Multichannel Assoc Get group=1 Fri 09/20/2024 08:40:23 PM : [ZW-DONE 00239 6.0 ] Multichannel Assoc Get group=1 Fri 09/20/2024 08:40:23 PM : [ZW-TX-Q 00240 6.0 ] Association Set group=1 node=1 Fri 09/20/2024 08:40:23 PM : [ZW-DONE 00240 6.0 ] Association Set group=1 node=1 Fri 09/20/2024 08:40:23 PM : [ZWAVE 6.0] Association Set in group 1 : Controller 6.0, Responder 1 Fri 09/20/2024 08:40:23 PM : ZWAVE-WORKQ-36 Finished write device updates for node 6, full=false Fri 09/20/2024 08:41:58 PM : Create REST U7 [/rest/profiles/ns/3/connection] Fri 09/20/2024 08:41:58 PM : Create REST U7 [/rest/profiles/ns/0/connection]

(Early adopter) I was able to update to to 5.8, and 3.1.4, but the commands weren't working with alexa. To narrow this down, I tried to run the "run then" for the program that I have. That didn't work. I had to highlight the command, and click the update in the add to program window, then save the changes, and it worked. Seems like the eisy device while visually looked correct, the acition set for door1 close won't work until the action was updated and save. I'm not really thinking this is an issue with the plugin, but the mechanism which things were changed and how eisy handles this. I had to updated each open and close command for the doors. I'm glad I made this variable based, so I only had to update it in 6 places. But I wonder if there was a simple way to refresh those programs. Everything seems to work great now. Thank you @Goose66

The device accepts power from USB. So 12 volt battery -> cigarette usb power adapter -> standard USB cable -> micro usb port on ratgdo. It must be converting the 5 Volts from the USB to 3.3 on it's own. USB doesn't supply 3.3 volts. See the white cord. My solution takes some soldering albeit, super easy, just attaching the wire to the positive terminal and negative terminal on the cigarette adapter. Everything else doesn't require soldering. I used this to connect to the battery wires, only because I had them. Better would be using something with copper to avoid the very long way down the road corrosion. https://a.co/d/8WGxLVE

I decided to go with a car usb outlet, and connect to the ratdgo via a micro USB cable. Just pop the top off, take out of enclosure, a weld wire to terminals and you have a very inexpensive power supply, that you can connect to the battery. https://www.amazon.com/dp/B09CPSXJ98 They sell in 1, 2 and 5 units.

@Goose66 Thank you for taking that approach, I had just updated all my programs. 3.0.3 Door State fix works great!

I'm using the default installed MQTT and not xKing's MQTT Node server. Logs incase that would be helpful. 2023-12-21 14:47:43,479 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door2 - stateData: {'door': 'closed'} 2023-12-21 14:47:43,479 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door2_lt - stateData: {'door': 'closed'} 2023-12-21 14:47:43,601 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: ST to 0 UOM 97 2023-12-21 14:47:46,485 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door1 Light(door1_lt) 2023-12-21 14:47:46,508 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door2(door2) 2023-12-21 14:47:46,570 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door2 Light(door2_lt) 2023-12-21 14:47:46,578 MQTT udi_interface.interface INFO interface:_message: Successfully set door1_lt :: ST to 0 UOM 78 2023-12-21 14:47:46,578 MQTT udi_interface.interface INFO interface:_message: Successfully set door1_lt :: GV0 to 1 UOM 2 2023-12-21 14:47:46,760 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closed'} 2023-12-21 14:47:46,760 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closed'} 2023-12-21 14:47:46,782 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: ST to 0 UOM 97 2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV0 to 1 UOM 2 2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV1 to 0 UOM 25 2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV2 to 101 UOM 25 2023-12-21 14:47:46,921 MQTT udi_interface.interface INFO interface:_message: Successfully set door2_lt :: ST to 100 UOM 78 2023-12-21 14:47:46,921 MQTT udi_interface.interface INFO interface:_message: Successfully set door2_lt :: GV0 to 1 UOM 2 2023-12-21 14:47:46,962 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 0 UOM 97 2023-12-21 14:49:10,540 Command udi_interface INFO nodes:_cmdDON: Opening door for door3 in DON command handler: {'address': 'door3', 'cmd': 'DON', 'query': {}} 2023-12-21 14:49:12,506 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'opening'} 2023-12-21 14:49:12,506 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'opening'} 2023-12-21 14:49:12,626 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 4 UOM 97 2023-12-21 14:49:21,207 Command udi_interface INFO nodes:_cmdSTOP: Stopping door for door3 in STOP command handler: {'address': 'door3', 'cmd': 'STOP', 'query': {}} 2023-12-21 14:49:23,640 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'stopped'} 2023-12-21 14:49:23,641 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'stopped'} 2023-12-21 14:49:23,717 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 9 UOM 97 2023-12-21 14:49:27,693 Command udi_interface INFO nodes:_cmdDOF: Closing door for door3 in DOF command handler: {'address': 'door3', 'cmd': 'DOF', 'query': {}} 2023-12-21 14:49:29,579 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closing'} 2023-12-21 14:49:29,580 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closing'} 2023-12-21 14:49:29,696 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 3 UOM 97 2023-12-21 14:49:43,444 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closed'} 2023-12-21 14:49:43,445 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closed'} 2023-12-21 14:49:43,562 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 0 UOM 97 2023-12-21 14:50:03,674 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message setLogLevel

Thank you for the quick response, door1,2,3 are installed. I closed and opened the Admin console (environment is windows using IoX Launcher and Java) No joy. I clicked the Load Profile in the plyglot V3 ratgdo details screen. Restarted the Admin console. No joy. Rebooted the Eisy box. No Joy. Only the closed state is shown correctly for Door State.

Do you want feedback from the releases here? I just updated to 3.02, and I think there might be a bug. Door3 state when open is 1%, door status when opening is 4%, door status when closing is 3% Door2 state when open is 1%, door status when opening is 4% and when closing is 3% Still working on installing Door1

@Goose66 worked as expected. It wasn't clear, that the IoX Eisy has MQTT installed by default. I almost installed the MTQQ in the store that king released. I did some more reading and found a thread stating it was part the base software. So it might be worth adding that note in the document, that MQTT is already there. 👍👍👍

Any idea when the charge showed up for the order? I ordered on the 6th as well, but maybe it didn't come through until the 7th. 👍👍👍 https://paulwieland.github.io/ratgdo/order_status.html

The people who have receive their Ratgdo, did you receive a shipping notification before your product was shipped? I was hoping to have receive my product by now, but I haven't. I've assumed that since this was backordered, that the charge and email about the order wouldn't happen until the product was in. I don't want to order a second set of 3 units, if the ones that I already order have already shipped. Could someone who has received their order elaborate on the process, like what type of email notification did you get? Thx!

Good afternoon, Local access it ideal, and required. Second for me is to not us a device that relies exclusively on polling for status.

The ratgdo option will not trigger the same action as the remote close using the myQ app. The lights won't flash and beep before it closes right?

@jkosharek Thank you for sharing. So now under $160, and better functionality, that pushes me over the edge. Ordering 3 of the ratgdo's. @Goose66 I was going to offer to send you one, but I see you've bought one as well. 👍👍 I really appreciate the work you put into this over the YEARS Goose, and I'll PM you about your day job. We develop software products, and are in the middle of setting up a partnership on a scale I'm looking for some wisdom on. 👍

Thank you for sharing that @Goose66 I like the concept of the ratgdo, with 3 doors, so that would be under $130. Looks like a project for the winter. I'll have to look more closely at this, as my doors have the battery backup option. We lose power up in the hill country where we live, and it's nice to be able to open the doors even when the power is out. The home automation is all on UPS's so depending on the complications it may or may not be viable to leverage the battery which is 12 volt. I like this because it was what I was expecting liftmaster was going to do with their product. I won't need my wireless door sensors anymore, as this look like the open and close detection is real time, and can be queried. 👍👍👍 Do you think we should wait a while to see if they respond to Michael, or the request for partner access? Or has that ship sailed?

I had been grandfathered in from lift master to access to the service. When they first said payment required to access the garages features remotely, the marketing on the packaging stated it was included. This was more than 10 years ago. I have a login to their service, but at least for me I don’t think the devices show up there anymore. But I have the same question, I’d be willing to pay for access until there is another way without it directly via their/my local hardware. This has motivated me to try harder to sniff the network. Now I have two projects to do the same thing for, this and the Hayward OmniLogic pool controller. i suspect if I speak to the CTO about their decision, he will have a list of reasons why they don’t give local access for home automation. Having a solid suggested method for that discussion would be useful. Any solid recommendations?

This might have been mentioned before, the the insteon wireless window sensor works great for a garage door. Just use some tape and gavity is all you need. 👍

@Goose66 I left the short and long default, I just started the service, and it worked perfectly. I think it was probably because I had the polyglot v2 running up until minutes before I did this. All good!

Everything was working great until early September when MyQ stopped working for Ployglot v2, so I bought the eisy. The migration was frustrating as all heck. Getting the local access using a PC was way less frustrating then the mobile app. The big missing piece was -- default login info for local eisy is admin admin. I purchased the 12.95 subscription from @Goose66, and thank you for your work on this. I think that I went wrong when I said upgrade the polyglot slot, which was the only slot 3. I didn't want to have to go in and redo program references so I hoped it would work. It looked like it didn't but there is an error when it tries to log in. See log below, removed password and email. 2023-10-01 13:20:49,504 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-10-01 13:20:49,504 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-10-01 13:20:49,504 MainThread udi_interface INFO __init__:<module>: User=0021b9026703_3 2023-10-01 13:20:49,504 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026703_3 2023-10-01 13:20:49,505 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026703_3 2023-10-01 13:20:49,505 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6Njc6MDMiLCJwcm9maWxlTnVtIjozLCJsb2dMZXZlbCI6IkRFQlVHIiwidG9rZW4iOiJySVQ5UEkhPUwxKk5PV0VIIiwibXF0dEhvc3QiOiJsb2NhbGhvc3QiLCJtcXR0UG9ydCI6ODg4Mywic2VjdXJlIjoxLCJpc1BHM3giOnRydWUsInBnM1ZlcnNpb24iOiIzLjIuOCIsImlzeVZlcnNpb24iOiI1LjcuMCIsImVkaXRpb24iOiJGcmVlIn0= 2023-10-01 13:20:49,505 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-10-01 13:20:49,558 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-10-01 13:20:49,997 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-10-01 13:20:50,211 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-10-01 13:20:50,211 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-10-01 13:20:50,211 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-10-01 13:20:50,212 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-10-01 13:20:50,212 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-10-01 13:20:50,212 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.2 Starting... 2023-10-01 13:20:50,243 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.8 [ISY: 5.7.0, Slot: 3] 2023-10-01 13:20:50,243 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.111.229', 'netmask': '255.255.255.0', 'broadcast': '192.168.111.255'} 2023-10-01 13:20:50,244 MainThread udi_interface INFO myqns:run: Starting MyQ node server... 2023-10-01 13:20:50,244 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-10-01 13:20:50,244 MainThread udi_interface.interface WARNING interface:_get_server_data: get_server_data: failed to read file server.json: [Errno 2] No such file or directory: 'server.json' 2023-10-01 13:20:50,245 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026703_3.cert key: 0021b9026703_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-10-01 13:20:50,245 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '3.2.22', 'requestId': False}} 2023-10-01 13:20:50,295 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-10-01 13:20:50,295 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:67:03_3 - MID: 2 Result: 0 2023-10-01 13:20:50,338 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-10-01 13:20:53,264 MainThread udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-10-01 13:20:53,290 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2023-10-01 13:20:53,290 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2023-10-01 13:20:53,290 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: load {'username': '########@gmail.com', 'password': '##################'} 2023-10-01 13:20:53,290 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'login_error': 'There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver.'} 2023-10-01 13:20:53,291 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking username / ########@gmail.com 2023-10-01 13:20:53,291 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking login_error / There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver. 2023-10-01 13:20:53,291 Thread-2 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking password / ################## 2023-10-01 13:20:53,291 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2023-10-01 13:20:53,292 Command udi_interface.interface DEBUG interface:_handleInput: Key oauth should be passed to node server. 2023-10-01 13:20:53,292 Thread-7 udi_interface DEBUG myqns:start: In Nodeserver start()... 2023-10-01 13:20:53,293 Thread-7 udi_interface.custom DEBUG custom:clear: CUSTOM: Clear ...saving 2023-10-01 13:20:53,293 Thread-7 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-10-01 13:20:53,293 Thread-7 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {}}]} 2023-10-01 13:20:53,293 Thread-7 udi_interface.node DEBUG node:_updateDrivers: Update service default GPV to 1 / 25 2023-10-01 13:20:53,294 Thread-7 udi_interface.node DEBUG node:_updateDrivers: Update service default ST to 0 / 2 2023-10-01 13:20:53,294 Thread-7 udi_interface.custom DEBUG custom:__init__: CUSTOM: Initialzing _rawdata to empty 2023-10-01 13:20:53,294 Thread-7 udi_interface.interface INFO interface:addNode: Adding node MyQ Service(service) [None] 2023-10-01 13:20:53,294 Thread-7 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'service', 'name': 'MyQ Service', 'nodeDefId': 'SERVICE', 'primaryNode': 'service', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 2}, {'driver': 'GPV', 'value': '1', 'uom': 25}], 'hint': [0, 0, 0, 0], 'private': None, 'rename': False}]} 2023-10-01 13:20:53,294 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getNsInfo 2023-10-01 13:20:53,295 Thread-7 udi_interface.interface INFO interface:setController: Using node "service", driver "GPV" for connection status. 2023-10-01 13:20:53,295 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getNsInfo 2023-10-01 13:20:53,295 Thread-7 udi_interface.interface DEBUG interface:send: PUBLISHING {'setController': {'node': 'service', 'driver': 'GPV'}} 2023-10-01 13:20:53,314 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h2>MyQ NodeServer Configuration</h2>\n\n<p>Add the required Custom Configuration Parameters for "username" and "password" below for your MyQ account. Note that the node server won\'t work with accounts tied to an Amazon, Google, or Apple login -- you must have a MyQ account. Once the "MyQ Service" appears in the Admin Console, click the "Discover Devices" button for the node to discover MyQ bridges (hubs) and devices linked to your account. If your account has devices linked for different homes, enter the "homename" Custom Configuration Parameter below to specify which home to load devices for.</p>\n\n<h4>Advanced Configuration:</h4>\n\n<ul>\n<li>key: shortPoll, value: polling interval for MyQ cloud service in "active" polling mode (defaults to 20 seconds - minimum polling interval).</li>\n<li>key: longPoll, value: polling interval for MyQ cloud service when not in "active" polling mode (defaults to 60 seconds).</li>\n</ul>\n\n<h4>Custom Configuration Parameters:</h4>\n\n<ul>\n<li>key: username, value: username (email address) for MyQ online account (required)</li>\n<li>key: password, value: password for MyQ online account (required)</li>\n<li>key: homename, value: home name from which to load devices (if your account has access to multiple homes) (optional)</li>\n</ul>\n'} 2023-10-01 13:20:53,316 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-10-01 13:20:53,357 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-10-01 13:20:53,357 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-10-01 13:20:53,358 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-10-01 13:20:53,358 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2023-10-01 13:20:53,398 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message setController 2023-10-01 13:20:53,398 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING setController 2023-10-01 13:20:53,398 Command udi_interface.interface DEBUG interface:_handleInput: connection status node/driver update 2023-10-01 13:20:53,458 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2023-10-01 13:20:53,500 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2023-10-01 13:20:53,500 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2023-10-01 13:20:53,501 Thread-9 udi_interface DEBUG nodes:start: In start() for MyQ Service node... 2023-10-01 13:20:53,501 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '47acc836-0694-40dd-b73b-3eb40da72c1f', 'uuid': '00:21:b9:02:67:03', 'profileNum': 3, 'address': 'service', 'name': 'MyQ Service', 'nodeDefId': 'SERVICE', 'nls': None, 'hint': '0x00000000', 'controller': 1, 'primaryNode': 'service', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1696188718719, 'timeModified': 1696191653347, 'dbVersion': 1} 2023-10-01 13:20:53,501 Thread-9 udi_interface INFO nodes:start: Establishing initial MyQ connection... 2023-10-01 13:20:53,501 Thread-9 udi_interface DEBUG myqapi:loginToService: in API loginToService()... 2023-10-01 13:20:53,502 Thread-9 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-10-01 13:20:53,574 Thread-9 udi_interface WARNING myqapi:_oAuthRequest: Network/server error logging into MyQ service: 429 Client Error: Too Many Requests for url: https://partner-identity.myq-cloud.com/connect/authorize?client_id=IOS_CGI_MYQ&code_challenge=FCziqTLLAGz_Gdngx19K61LAt6tSyAwDVDfsK-Qp250&code_challenge_method=S256&redirect_uri=com.myqops%3A%2F%2Fios&response_type=code&scope=MyQ_Residential+offline_access 2023-10-01 13:20:53,574 Thread-9 udi_interface DEBUG myqapi:_oAuthRetrieveToken: Error in Step 1 of oAuth flow. 2023-10-01 13:20:53,574 Thread-9 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: login_error = There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver. ...saving 2023-10-01 13:20:53,574 Thread-9 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-10-01 13:20:53,574 Thread-9 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {'login_error': 'There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver.'}}]} 2023-10-01 13:20:53,576 Thread-9 udi_interface.node DEBUG node:setDriver: service:MyQ Service No change in ST's value 2023-10-01 13:20:53,593 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-10-01 13:20:53,593 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-10-01 13:20:53,594 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'login_error': 'There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver.'} 2023-10-01 13:20:53,594 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking login_error / There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver. 2023-10-01 13:20:53,635 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices I've stopped it an maybe it will work in a while, but I'm thinking this might be something to do with the agent not being updated since I used the same node, and it's not unique to me. 👍👍

Thank you for your response. I'm open for any solution at this point, and open to solutions that use other manufactures devices for the automation. Dimming to 1% is required and having no visible artifacts is required.

I have a number of places in the house where we have 24 VDC LED strips. Right now they are being driven with a on off switch that goes to the LED Driver. I'd like to change these to dimmable switches and I'm wondering which LED driver is recommended for this application. I've search online about this, and there are discussions from 2016 and some that are a little newer. I looked at a Magnitude and found that their drivers were not recommended for Insteon 2477DH which I'm using 2477D. My understanding is H is just the high wattage designation. https://magnitudeinc.com/wp-content/uploads/2021/04/E-Series-24V-Dimmer-Compatiblity-List-REV012.pdf I'm using their E40L24DC-KO for the simple on off now and it works great. When I try and dim, it works down to about 20% then it starts to flicker. So what LED driver should be used in when wanting to dim 24 VDC LED strips? I'm not finding LED drivers that reference insteon. Thank you in advanced! Todd