Insteon 8-Button Keypad All Buttons Lighting Up #115502
Comments
|
Hey there @teharris1, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) insteon documentation |
|
Well, I see what is happening but let me confirm some assumptions:
Is that correct? |
|
@teharris1 - responses below:
Please let me know if I can provide any further information! |
|
Thanks for reminding me of the past issue. Do you know when this issue showed up? The recent releases with changes to the Insteon module were:
What I can see is there is a race condition going on but I cannot tell from the logs you copied above what is causing the race condition to even start. The logs only show a section of the Insteon traffic so I could use a broader log file. Can you restart HA, turn logging back on, recreate the problem and upload the full log? Please note the time when the problem occurs so I can focus my attention in the log file. |
|
I actually have the full log (attached in this comment). The log that has "04122024" in the name is associated with the snippet that I pasted in for you to initially look at. I also added two other logs from two previous days where I was also doing similar testing. home-assistant.log.has_keypad_lightup_from_upstairs_switch_fast_toggling_04102024.txt To answer your question about when this issue showed up, unfortunately I am not sure, it has been happening sporadically for a very long time and I have kind of just been living with it, but I finally decided to write up a bug report now, so that's my bad, I know that is not super helpful. I really only remember things being a 100% smooth and functional prior to 2021.12.10 when I wrote up that previous bug report around that time. |
|
Great. Looking at the 04122024 log, I see a device 33.88.F6 that seems to be the trigger for the KPL 33.15.31 to potentially change. Are those two devices liked in any way? Every time this device 33.88.F6 changes the KPL is requested to provide status. There are two status messages for a KPL, the first status request is for the main power button and the second is for the b-h buttons. The issue is that the two status requests are overlapping. It is hard to explain without getting into a lot of detail about the Insteon protocol, but the two status messages are getting confused and the status of the main button is looking like the status of the b-h buttons and vice versa. I have an idea on how to address that but I need to think about it a little bit. BTW, thanks for writing this up. |
|
Yes! 33.88.F6 are indeed linked. I manually linked the keypad and switch using the devices themselves. I believe that 33.86.F6 is linked to button c on the keypad, and 33.88.F6 is the switch that I was using (toggling it on and off) to try to reproduce the problem, so your observation makes sense. Thanks for looking into it! If you need to talk back and forth about any further observations or anything else, feel free to let me know. |
|
I think I have a solution to this issue but I am not 100% sure. I will get the change into HA soon. How technical are you? If you want to try to use the new code, I can give it to you but it will involve making some manual edits to some things in order to get it to work. Will require the ability to log into your HA system at the operating system level and entering some file changes. |
|
I'd be happy to try something out, I'm sure I can figure it out. I run HA
using Docker, I'll be able to get into the container and make some hot
edits if needed. If you can provide me instructions on how to install the
software and which edits you'd like me to make, I'll give it a shot.
…On Mon, Apr 29, 2024, 2:20 PM Tom Harris ***@***.***> wrote:
I think I have a solution to this issue but I am not 100% sure. I will get
the change into HA soon.
How technical are you? If you want to try to use the new code, I can give
it to you but it will involve making some manual edits to some things in
order to get it to work. Will require the ability to log into your HA
system at the operating system level and entering some file changes.
—
Reply to this email directly, view it on GitHub
<#115502 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOYOE5D6SKI37BYN6ON3GWDY72FNVAVCNFSM6AAAAABGE4GO66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTGM3TANJXHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Cool. Here is what you can do: This will upgrade your |
|
Sounds easy enough, I'll try that in a few minutes. One question before I
start - once I restart the container, is there an easy way for me to
confirm that I am in fact using the new version of software just so that I
am confident that I am testing with the right thing?
…On Mon, Apr 29, 2024, 5:51 PM Tom Harris ***@***.***> wrote:
Cool. Here is what you can do:
1. Open an command prompt in the docker host
2. Run `docker exec homeassistant -it /bin/bash`
3. `cd /usr/src/homeassistant/homeassistant/components/insteon`
4. Edit the `manifest.json` file with whatever editor you are good with (emac, vi, etc)
5. Change `pyinsteon==1.5.3` to `pyinsteon==1.5.4` and save
6. Back on the command prompt run `cd /config`
7. `git clone https://github.com/pyinsteon/pyinsteon.git` <https://github.com/pyinsteon/pyinsteon.git>
8. `cd pyinsteon`
9. `pip install --upgrade .`
10. Restart Home Assistant
This will upgrade your pyinsteon module to 1.5.4 which is not released
yet.
—
Reply to this email directly, view it on GitHub
<#115502 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOYOE5HLBYR6II6FMUBIOB3Y726HJAVCNFSM6AAAAABGE4GO66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTG42DKNZUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
The pip command in step 9 will tell you if it was successful. After you restart you can repeat step 2 and use this command: |
|
So first thing, this is working MUCH better! I only observed all keypad button status in the logs in two spots (i.e. I was trying to see if I could find the same issue I noted in my previous logs), and this was towards the beginning of the log (and just one instance per keypad I have, of which I have two), so maybe it was just initialization. I went through the following steps with keypad 33.15.31:
The above sequence produced no observable issues in the log or keypad! Next, I tried a similar experiment with my other keypad, and I did see one issue pop up. This test was slightly different in that it involved toggling a switch quickly that was paired with the keypad's main button. This was for keypad 49.F0.3D, and I started this test after timestamp 2024-04-29 18:47:20.718 in the log:
I have attached the log from this testing here. Again, things seem MUCH improved, thanks for the update! There was just that one problem that I observed when toggling something paired with the main button mentioned above. home-assistant.log_den_keypad_kitchen_lights_off_wrong_04292024.txt |
|
Just popping back in here - I actually saw another instance where all keypad buttons lit up. I am not 100% sure what was going on at the time, I just noticed that all buttons (except for the main one) were lit up on keypad at one point during the day. I also don't know when this happened, but FYI, around 16:10:30 I did turn each button off myself manually. I have attached the log to this post. |
|
I saw one more instance of a keypad button being triggered unexpectedly. Since I was not specifically testing, I do not have the exact time at which this happened, but it was around 21:21 on 5/4/2024. Log is attached here. |
|
2 questions
|
|
I did not change anything since putting in the patched code. When I noticed
all the buttons lit up on the one keypad, I did go back into the container
and check that I was still using the 1.5.4 version of pyinsteon. I did not
check after the second time I noticed a problem though, I can check later
when I get back home.
I am using the hub v2, but I do not use the app at all.
…On Sun, May 5, 2024, 11:48 AM Tom Harris ***@***.***> wrote:
2 questions
1. Did you upgrade since putting in the patched code?
2. Are you using a hub?
—
Reply to this email directly, view it on GitHub
<#115502 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOYOE5AUH6JW2FQEZ5VYZ2TZAZIERAVCNFSM6AAAAABGE4GO66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUHA2TOMBYGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I went through both logs. The log from 3-May is clear. All of the buttons on the KPL 49.F0.3D were manually turned on at the switch between 15:55:25 and 15:55:38. The logs definately show All-Link Broadcast commands coming into HA which indicates a manual change at the switch itself. Someone is pushing your buttons : ) I could not tell what was going on in the second file. I looked at both KPLs 49.F0.3D and 33.15.31 but I don't see abnormal behavior in either of them. |
|
So funny thing, I did some detective work based on your first comment, and APPARENTLY my wife said her friend decided to push all the buttons on the keypad a few days ago - UGH! Of course this was while I was trying to keep an eye on things to see how the software updates were holding up, so bad timing. Sorry for wasting your time on that one. As for the second log - it's possible that that was caused by something wrong with one of my automations, so I'll just keep an eye on that on my end. I think I am good with how everything has been performing recently; we don't have a ton of runtime with the updates, but I have not been able to reproduce the original issue with my testing, so I think I am good to call this closed. Thanks for the quick fix! |
The problem
First, here is an overview of my setup:
The problem:
Sometimes when Insteon light switches are toggled, all Insteon keypad buttons turn on on the keypads that I have. Often when this happens, when looking at debug logs, the buttons all turn on (observed by seeing topic messages in the debug logs), then almost immediately turn off, so the keypad does not always visibly light up due to the quick toggle. There are cases; however, where the buttons turn on and there is not a subsequent "off" action observed, so I do see all buttons actually light up on the keypad in that case.
As a note, for the observation mentioned above, I disabled all of my automations that involve Insteon devices. Further, I went through the process of factory resetting ALL of my Insteon devices, including the hub, and the issue still persists. At this point I cannot tell if there is something going on with the Insteon devices themselves, or if it is something with pyinsteon. This issue has been going on for a very long time for me. The only time I remember it not being a problem was with Home Assistant version 2021.12.10 and prior (I had posted an issue for a version after 2021.12.10 where things were not working at all; things have much improved since then, but the aforementioned issue still exists. For reference, that issue was: #65857)
In the log snippet that I provided in the "Diagnostic Information" section, the keypad buttons all light up at 2024-04-12 16:15:47.534.
What version of Home Assistant Core has the issue?
2024.4.1
What was the last working version of Home Assistant Core?
2021.12.10
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Insteon
Link to integration documentation on our website
https://www.home-assistant.io/integrations/insteon/
Diagnostics information
2024-04-12 16:15:43.909 DEBUG (MainThread) [pyinsteon.topics] Topic: send.status_request.direct data: {'address': 331531, 'status_type': 1}
2024-04-12 16:15:43.909 DEBUG (MainThread) [pyinsteon.messages] TX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x01 2024-04-12 16:15:44.451 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x01, ack: 0x06 2024-04-12 16:15:44.451 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.331531.status_request.direct data: {'cmd1': 25, 'cmd2': 1, 'user_data': None} 2024-04-12 16:15:44.452 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 331531, target: 49e6a4, flags: 0x25, cmd1: 0x11, cmd2: 0x09 2024-04-12 16:15:44.452 DEBUG (MainThread) [pyinsteon.topics] Topic: 331531.on.direct_ack data: {'cmd1': 17, 'cmd2': 9, 'target': 49e6a4, 'user_data': None, 'hops_left': 1} 2024-04-12 16:15:44.513 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.331531.1.status_request.direct data: {'db_version': 17, 'status': 9} 2024-04-12 16:15:45.055 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 000001, flags: 0xcf, cmd1: 0x11, cmd2: 0x00 2024-04-12 16:15:45.056 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.1.on.all_link_broadcast data: {'cmd1': 17, 'cmd2': 0, 'target': 000001, 'user_data': None, 'hops_left': 3}
2024-04-12 16:15:45.056 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.3388f6.1.on.all_link_broadcast data: {'on_level': 255} 2024-04-12 16:15:45.056 DEBUG (MainThread) [pyinsteon.topics] Topic: subscriber_3388f6_on_1_broadcast data: {'on_level': 255} 2024-04-12 16:15:45.056 DEBUG (MainThread) [pyinsteon.topics] Topic: state_3388f6_dimmable_light_1 data: {'name': 'dimmable_light', 'address': '3388f6', 'value': 255, 'group': 1} 2024-04-12 16:15:45.056 DEBUG (MainThread) [pyinsteon.topics] Topic: event_3388f6_1_on_event data: {'name': 'on_event', 'address': '3388f6', 'group': 1, 'button': 'dimmable_light'} 2024-04-12 16:15:45.057 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 000001, flags: 0xcf, cmd1: 0x13, cmd2: 0x00 2024-04-12 16:15:45.057 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.1.off.all_link_broadcast data: {'cmd1': 19, 'cmd2': 0, 'target': 000001, 'user_data': None, 'hops_left': 3}
2024-04-12 16:15:45.057 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.3388f6.1.off.all_link_broadcast data: {'on_level': 0} 2024-04-12 16:15:45.057 DEBUG (MainThread) [pyinsteon.topics] Topic: subscriber_3388f6_off_1_broadcast data: {'on_level': 0} 2024-04-12 16:15:45.057 DEBUG (MainThread) [pyinsteon.topics] Topic: state_3388f6_dimmable_light_1 data: {'name': 'dimmable_light', 'address': '3388f6', 'value': 0, 'group': 1} 2024-04-12 16:15:45.057 DEBUG (MainThread) [pyinsteon.topics] Topic: event_3388f6_1_off_event data: {'name': 'off_event', 'address': '3388f6', 'group': 1, 'button': 'dimmable_light'} 2024-04-12 16:15:45.058 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 49e6a4, flags: 0x40, cmd1: 0x13, cmd2: 0x01 2024-04-12 16:15:45.058 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.1.off.all_link_cleanup data: {'cmd1': 19, 'cmd2': 1, 'target': 49e6a4, 'user_data': None, 'hops_left': 0}
2024-04-12 16:15:45.058 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.3388f6.1.off.all_link_cleanup data: {}
2024-04-12 16:15:45.059 DEBUG (MainThread) [pyinsteon.topics] Topic: send.status_request.direct data: {'address': 331531, 'status_type': 2}
2024-04-12 16:15:45.061 DEBUG (MainThread) [pyinsteon.messages] TX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x02
2024-04-12 16:15:45.660 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x02, ack: 0x06
2024-04-12 16:15:45.660 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.331531.status_request.direct data: {'cmd1': 25, 'cmd2': 2, 'user_data': None}
2024-04-12 16:15:45.661 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 331531, target: 49e6a4, flags: 0x20, cmd1: 0x19, cmd2: 0xfe
2024-04-12 16:15:45.661 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 000001, flags: 0xcf, cmd1: 0x11, cmd2: 0x00 2024-04-12 16:15:45.661 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.1.on.all_link_broadcast data: {'cmd1': 17, 'cmd2': 0, 'target': 000001, 'user_data': None, 'hops_left': 3}
2024-04-12 16:15:45.662 DEBUG (MainThread) [pyinsteon.topics] Topic: send.status_request.direct data: {'address': 331531, 'status_type': 2}
2024-04-12 16:15:45.663 DEBUG (MainThread) [pyinsteon.messages] TX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x02
2024-04-12 16:15:45.722 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.331531.2.status_request.direct data: {'db_version': 25, 'status': 254}
2024-04-12 16:15:45.723 DEBUG (MainThread) [pyinsteon.topics] Topic: send.status_request.direct data: {'address': 331531, 'status_type': 1}
2024-04-12 16:15:46.188 DEBUG (MainThread) [pyinsteon.messages] TX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x01
2024-04-12 16:15:46.265 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x02, ack: 0x06
2024-04-12 16:15:46.265 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.331531.status_request.direct data: {'cmd1': 25, 'cmd2': 2, 'user_data': None}
2024-04-12 16:15:46.266 DEBUG (MainThread) [pyinsteon.topics] Topic: send.status_request.direct data: {'address': 331531, 'status_type': 2}
2024-04-12 16:15:46.790 DEBUG (MainThread) [pyinsteon.messages] TX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x02
2024-04-12 16:15:46.869 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x01, ack: 0x06
2024-04-12 16:15:46.869 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.331531.status_request.direct data: {'cmd1': 25, 'cmd2': 1, 'user_data': None}
2024-04-12 16:15:47.473 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 331531, target: 49e6a4, flags: 0x23, cmd1: 0x19, cmd2: 0xfe
2024-04-12 16:15:47.473 DEBUG (MainThread) [pyinsteon.topics] Topic: 331531.status_request.direct_ack data: {'cmd1': 25, 'cmd2': 254, 'target': 49e6a4, 'user_data': None, 'hops_left': 0}
2024-04-12 16:15:47.533 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.331531.2.status_request.direct data: {'db_version': 25, 'status': 254}
2024-04-12 16:15:47.534 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.331531.1.status_request.direct data: {'db_version': 25, 'status': 254}
2024-04-12 16:15:47.534 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_b_2 data: {'name': 'on_off_switch_b', 'address': '331531', 'value': 1, 'group': 2}
2024-04-12 16:15:47.534 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_c_3 data: {'name': 'on_off_switch_c', 'address': '331531', 'value': 1, 'group': 3}
2024-04-12 16:15:47.534 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_e_5 data: {'name': 'on_off_switch_e', 'address': '331531', 'value': 1, 'group': 5}
2024-04-12 16:15:47.535 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_f_6 data: {'name': 'on_off_switch_f', 'address': '331531', 'value': 1, 'group': 6}
2024-04-12 16:15:47.535 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_g_7 data: {'name': 'on_off_switch_g', 'address': '331531', 'value': 1, 'group': 7}
2024-04-12 16:15:47.535 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_h_8 data: {'name': 'on_off_switch_h', 'address': '331531', 'value': 1, 'group': 8}
2024-04-12 16:15:47.537 DEBUG (MainThread) [pyinsteon.topics] Topic: send.status_request.direct data: {'address': 331531, 'status_type': 1}
2024-04-12 16:15:47.538 DEBUG (MainThread) [pyinsteon.messages] TX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x01
2024-04-12 16:15:48.076 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x62, address: 331531, flags: 0x0f, cmd1: 0x19, cmd2: 0x01, ack: 0x06
2024-04-12 16:15:48.076 DEBUG (MainThread) [pyinsteon.topics] Topic: ack.331531.status_request.direct data: {'cmd1': 25, 'cmd2': 1, 'user_data': None}
2024-04-12 16:15:48.076 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 331531, target: 49e6a4, flags: 0x2f, cmd1: 0x11, cmd2: 0x09
2024-04-12 16:15:48.076 DEBUG (MainThread) [pyinsteon.topics] Topic: 331531.on.direct_ack data: {'cmd1': 17, 'cmd2': 9, 'target': 49e6a4, 'user_data': None, 'hops_left': 3}
2024-04-12 16:15:48.137 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.331531.1.status_request.direct data: {'db_version': 17, 'status': 9}
2024-04-12 16:15:48.137 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_b_2 data: {'name': 'on_off_switch_b', 'address': '331531', 'value': 0, 'group': 2}
2024-04-12 16:15:48.138 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_c_3 data: {'name': 'on_off_switch_c', 'address': '331531', 'value': 0, 'group': 3}
2024-04-12 16:15:48.138 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_e_5 data: {'name': 'on_off_switch_e', 'address': '331531', 'value': 0, 'group': 5}
2024-04-12 16:15:48.138 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_f_6 data: {'name': 'on_off_switch_f', 'address': '331531', 'value': 0, 'group': 6} 2024-04-12 16:15:48.138 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_g_7 data: {'name': 'on_off_switch_g', 'address': '331531', 'value': 0, 'group': 7} 2024-04-12 16:15:48.138 DEBUG (MainThread) [pyinsteon.topics] Topic: state_331531_on_off_switch_h_8 data: {'name': 'on_off_switch_h', 'address': '331531', 'value': 0, 'group': 8}
2024-04-12 16:15:48.682 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 000001, flags: 0xcf, cmd1: 0x13, cmd2: 0x00
2024-04-12 16:15:48.682 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.1.off.all_link_broadcast data: {'cmd1': 19, 'cmd2': 0, 'target': 000001, 'user_data': None, 'hops_left': 3}
2024-04-12 16:15:48.682 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.3388f6.1.off.all_link_broadcast data: {'on_level': 0}
2024-04-12 16:15:48.682 DEBUG (MainThread) [pyinsteon.topics] Topic: subscriber_3388f6_off_1_broadcast data: {'on_level': 0}
2024-04-12 16:15:48.682 DEBUG (MainThread) [pyinsteon.topics] Topic: event_3388f6_1_off_event data: {'name': 'off_event', 'address': '3388f6', 'group': 1, 'button': 'dimmable_light'}
2024-04-12 16:15:48.683 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 49e6a4, flags: 0x40, cmd1: 0x13, cmd2: 0x01
2024-04-12 16:15:48.683 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.1.off.all_link_cleanup data: {'cmd1': 19, 'cmd2': 1, 'target': 49e6a4, 'user_data': None, 'hops_left': 0}
2024-04-12 16:15:48.683 DEBUG (MainThread) [pyinsteon.topics] Topic: handler.3388f6.1.off.all_link_cleanup data: {}
2024-04-12 16:15:49.286 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 130201, flags: 0xcb, cmd1: 0x06, cmd2: 0x00
2024-04-12 16:15:49.287 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.all_link_cleanup_status_report.all_link_broadcast data: {'cmd1': 6, 'cmd2': 0, 'target': 130201, 'user_data': None, 'hops_left': 2}
2024-04-12 16:15:49.287 DEBUG (MainThread) [pyinsteon.messages] RX: msg_id: 0x50, address: 3388f6, target: 000001, flags: 0xcf, cmd1: 0x11, cmd2: 0x00 2024-04-12 16:15:49.287 DEBUG (MainThread) [pyinsteon.topics] Topic: 3388f6.1.on.all_link_broadcast data: {'cmd1': 17, 'cmd2': 0, 'target': 000001, 'user_data': None, 'hops_left': 3}
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: