2432-2 Mini Remote butons not responding
Closed this issue · 5 comments
Hi,
I have paired an 8 button Mini Remote with insteon-mqtt but only 2 (b and c) of the 8 buttons seem to be recognized as traffic by the PLM. When I pair this with an ISY, all of the buttons generate traffic. Is there something about the linking that prevents this PLM from seeing all of the buttons?
This is a dump from the b button:
2021-03-27 14:33:26.127 INFO Protocol: Read 0x50: Std: 53.0e.49 Type.ALL_LINK_BROADCAST mh:3 hl:1 grp: 01 cmd: 11 00
2021-03-27 14:33:26.127 DEBUG Protocol: Setting next write time: 14:33:26.214
2021-03-27 14:33:26.128 DEBUG MsgHistory: Received 2 hops, total 11 for 11 entries
2021-03-27 14:33:26.128 INFO Broadcast: Handling all link broadcast for 53.0e.49 'None'
2021-03-27 14:33:26.128 DEBUG Protocol: Setting next write time: 14:33:27.150
2021-03-27 14:33:26.128 INFO Base: Device 53.0e.49 broadcast grp: 1 on: True mode: normal
2021-03-27 14:33:26.128 INFO Base: Setting device 53.0e.49 on True level None normal device
2021-03-27 14:33:26.129 INFO StateTopic: MQTT received state 53.0e.49 on: {'is_on': True, 'level': None, 'mode': <Mode.NORMAL: 'normal'>, 'button': 1, 'reason': 'device'}
2021-03-27 14:33:26.129 DEBUG Mqtt: MQTT publish insteon/53.0e.49/state/1 ON qos=1 ret=False
2021-03-27 14:33:26.129 DEBUG Base: Found 1 responders in group 1
2021-03-27 14:33:26.129 DEBUG Base: Group 1 -> ['49.fa.c1']
2021-03-27 14:33:26.130 INFO Base: 53.0e.49 broadcast to 49.fa.c1 for group 1
2021-03-27 14:33:26.130 DEBUG Mqtt: MQTT writing
2021-03-27 14:33:26.303 INFO Protocol: Read 0x50: Std: 53.0e.49 Type.ALL_LINK_BROADCAST mh:3 hl:2 grp: 01 cmd: 11 00
2021-03-27 14:33:26.303 DEBUG MsgHistory: Received 1 hops, total 11 for 11 entries
2021-03-27 14:33:27.071 INFO Protocol: Read 0x50: Std: 53.0e.49 Type.ALL_LINK_BROADCAST mh:3 hl:2 grp: 01 cmd: 06 00
2021-03-27 14:33:27.071 DEBUG Protocol: Setting next write time: 14:33:27.245
2021-03-27 14:33:27.071 DEBUG MsgHistory: Received 1 hops, total 12 for 11 entries
2021-03-27 14:33:27.072 DEBUG Protocol: Setting next write time: 14:33:27.072
2021-03-27 14:33:27.072 DEBUG Protocol: Setting next write time: 14:33:27.245
2021-03-27 14:33:27.072 DEBUG Broadcast: Cleanup report for 53.0e.49, grp 1 success.
2021-03-27 14:33:27.327 INFO Protocol: Read 0x50: Std: 53.0e.49 Type.ALL_LINK_BROADCAST mh:3 hl:1 grp: 01 cmd: 06 00
2021-03-27 14:33:27.327 DEBUG Protocol: Setting next write time: 14:33:27.414
2021-03-27 14:33:27.327 DEBUG MsgHistory: Received 2 hops, total 13 for 11 entries
2021-03-27 14:33:27.328 DEBUG Protocol: Setting next write time: 14:33:27.328
2021-03-27 14:33:27.328 DEBUG Protocol: Setting next write time: 14:33:27.414
2021-03-27 14:33:27.328 DEBUG Broadcast: Cleanup report for 53.0e.49, grp 1 success.
print-db:
Commanding mini_remote_8 device 53.0e.49 cmd=print_db
53.0e.49 device database
DeviceDb: (delta 42)
0fc7: 49.fa.c1 (modem) grp: 8 type: CTRL data: 0x03 0x00 0x00
0fcf: 49.fa.c1 (modem) grp: 7 type: CTRL data: 0x03 0x00 0x00
0fd7: 49.fa.c1 (modem) grp: 6 type: CTRL data: 0x03 0x00 0x00
0fdf: 49.fa.c1 (modem) grp: 5 type: CTRL data: 0x03 0x00 0x00
0fe7: 49.fa.c1 (modem) grp: 4 type: CTRL data: 0x03 0x00 0x00
0fef: 49.fa.c1 (modem) grp: 3 type: CTRL data: 0x03 0x00 0x00
0ff7: 49.fa.c1 (modem) grp: 2 type: CTRL data: 0x03 0x00 0x00
0fff: 49.fa.c1 (modem) grp: 1 type: CTRL data: 0x03 0x00 0x00
Unused:
0fbf: 00.00.00 grp: 0 type: RESP data: 0x00 0x00 0x00 (UNUSED) (LAST)
Last:
0fbf: 00.00.00 grp: 0 type: RESP data: 0x00 0x00 0x00 (UNUSED) (LAST)
GroupMap
1 -> ['49.fa.c1 (modem)']
2 -> ['49.fa.c1 (modem)']
3 -> ['49.fa.c1 (modem)']
4 -> ['49.fa.c1 (modem)']
5 -> ['49.fa.c1 (modem)']
6 -> ['49.fa.c1 (modem)']
7 -> ['49.fa.c1 (modem)']
8 -> ['49.fa.c1 (modem)']
Complete
Flags:
Commanding mini_remote_8 device 53.0e.49 cmd=get_flags
Device 53.0e.49 operating flags: 10100010
Operation complete
I suspect the ISY has erased or altered some links. Rather than printing the db, run a refresh to see what it actually has.
This is a brand new PLM (USB). The ISY setup is running in parallel - I just moved the remote between them with a full paid/join. I will do a refresh and report back.
Refresh seems fine but still same buttons. I also have a leak sensor that also seems to never show wet ON only wet OFF. Perhaps something is totally broken with this PLM? I did a factory reset and still have the same behaviors.
Commanding mini_remote_8 device 53.0e.49 cmd=refresh
Device database is current at delta 42
Device 53.0e.49 refresh cmd2 161
Device refreshed
There must be something wrong with this PLM. I just did the same setup with an Insteon hub via insteon-mqtt and it worked fine.
Relatively convinced there is a problem with this PLM.