You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
I do use insteon-mqtt with success for my switches and dimmers.
I try to configure my 4 motion sensors without success. Most likely it's probably an issue on my side, but my research does not point to anything about motion configuration
I did the join command, and I think I have an issue with the pair command and the refresh. The refresh command was done by pressing the set button and then issue the refresh command on that specific device.
With insteon-terminal, I issue a ping command on the device and got a ACK from it.
The insteon-mqtt get-devices command return the device
{"37.c3.5b": {"type": "battery_sensor", "label": "l0_motion_sdb"}}
Hi
I do use insteon-mqtt with success for my switches and dimmers.
I try to configure my 4 motion sensors without success. Most likely it's probably an issue on my side, but my research does not point to anything about motion configuration
I did the join command, and I think I have an issue with the pair command and the refresh. The refresh command was done by pressing the set button and then issue the refresh command on that specific device.
With insteon-terminal, I issue a ping command on the device and got a ACK from it.
The insteon-mqtt get-devices command return the device
{"37.c3.5b": {"type": "battery_sensor", "label": "l0_motion_sdb"}}
I do include the output of the pair.
[2019-11-10 22:06:25] insteon/command/37.c3.5b {"cmd": "pair", "session": "2048748167"}
rch[2019-11-10 22:06:25] insteon/command/37.c3.5b/session/2048748167 {"type": "MESSAGE", "data": "Commanding battery_sensor device 37.c3.5b (l0_motion_sdb) cmd=pair"}
[2019-11-10 22:06:26] insteon/command/37.c3.5b/session/2048748167 {"type": "MESSAGE", "data": "Device database is current at delta 25"}
[2019-11-10 22:06:26] insteon/command/37.c3.5b/session/2048748167 {"type": "MESSAGE", "data": "BatterySensor 37.c3.5b refresh on = False"}
[2019-11-10 22:06:26] insteon/37.c3.5b/state OFF
[2019-11-10 22:06:26] insteon/command/37.c3.5b/session/2048748167 {"type": "ERROR", "data": "Operation failed - wrong cmd"}
[2019-11-10 22:06:26] insteon/command/37.c3.5b/session/2048748167 {"type": "END", "data": null}
root@maison:/home/insteon/insteon-mqtt# ./bin/insteon-mqtt config.yaml pair 37.c3.5b
Commanding battery_sensor device 37.c3.5b (l0_motion_sdb) cmd=pair
Device database is current at delta 25
BatterySensor 37.c3.5b refresh on = False
ERROR: Operation failed - wrong cmd
2019-11-10 22:06:25 INFO Mqtt: MQTT message insteon/command/37.c3.5b b'{"cmd": "pair", "session": "2048748167"}'
2019-11-10 22:06:25 UI Mqtt: Commanding battery_sensor device 37.c3.5b (l0_motion_sdb) cmd=pair
2019-11-10 22:06:25 DEBUG Mqtt: MQTT publish insteon/command/37.c3.5b/session/2048748167 {"type": "MESSAGE", "data": "Commanding battery_sensor device 37.c3.5b (l0_motion_sdb) cmd=pair"} qos=0 ret=False
2019-11-10 22:06:25 INFO BatterySensor: BatterySensor 37.c3.5b pairing
2019-11-10 22:06:25 DEBUG CommandSeq: Running command 1 of 5
2019-11-10 22:06:25 INFO Base: Device 37.c3.5b (l0_motion_sdb) cmd: status refresh
2019-11-10 22:06:25 DEBUG CommandSeq: Running command 1 of 2
2019-11-10 22:06:25 INFO Protocol: Write message to modem: Std: 37.c3.5b, Type.DIRECT, 19 00
2019-11-10 22:06:25 DEBUG Protocol: Write bytes to modem: b'\x02b7\xc3[\x0f\x19\x00'
2019-11-10 22:06:25 DEBUG Serial: Wrote 8 bytes to serial /dev/ttyUSB0
2019-11-10 22:06:25 DEBUG Mqtt: MQTT writing
2019-11-10 22:06:25 INFO Protocol: Read 0x62: Std: 37.c3.5b, Type.DIRECT, 19 00 ack: True
2019-11-10 22:06:25 DEBUG Protocol: Passing msg to write handler: DeviceRefresh handler
2019-11-10 22:06:25 DEBUG DeviceRefresh: 37.c3.5b ACK response
2019-11-10 22:06:26 INFO Protocol: Read 0x50: Std: 37.c3.5b->4c.14.97 Type.DIRECT_ACK cmd: 19 00
2019-11-10 22:06:26 DEBUG Protocol: Setting next write time: 1573441586.177488
2019-11-10 22:06:26 DEBUG MsgHistory: Received 1 hops, total 3 for 11 entries
2019-11-10 22:06:26 DEBUG Protocol: Passing msg to write handler: DeviceRefresh handler
2019-11-10 22:06:26 UI DeviceRefresh: Device database is current at delta 25
2019-11-10 22:06:26 DEBUG Mqtt: MQTT publish insteon/command/37.c3.5b/session/2048748167 {"type": "MESSAGE", "data": "Device database is current at delta 25"} qos=0 ret=False
2019-11-10 22:06:26 UI BatterySensor: BatterySensor 37.c3.5b refresh on = False
2019-11-10 22:06:26 DEBUG Mqtt: MQTT publish insteon/command/37.c3.5b/session/2048748167 {"type": "MESSAGE", "data": "BatterySensor 37.c3.5b refresh on = False"} qos=0 ret=False
2019-11-10 22:06:26 INFO BatterySensor: Setting device 37.c3.5b (l0_motion_sdb) on:False
2019-11-10 22:06:26 INFO BatterySensor: MQTT received on/off change 37.c3.5b (l0_motion_sdb) on: False
2019-11-10 22:06:26 DEBUG Mqtt: MQTT publish insteon/37.c3.5b/state OFF qos=1 ret=1
2019-11-10 22:06:26 DEBUG CommandSeq: Running command 2 of 2
2019-11-10 22:06:26 INFO Base: Device 37.c3.5b (l0_motion_sdb) cmd: get engine version
2019-11-10 22:06:26 DEBUG MsgHistory: Average hops 0.3, using 1
2019-11-10 22:06:26 DEBUG Protocol: Write handler finished
2019-11-10 22:06:26 INFO Protocol: Write message to modem: Std: 37.c3.5b, Type.DIRECT, 10 00
2019-11-10 22:06:26 DEBUG Protocol: Write bytes to modem: b'\x02b7\xc3[\x05\x10\x00'
2019-11-10 22:06:26 DEBUG Mqtt: MQTT writing
2019-11-10 22:06:26 DEBUG Serial: Wrote 8 bytes to serial /dev/ttyUSB0
2019-11-10 22:06:26 INFO Protocol: Read 0x62: Std: 37.c3.5b, Type.DIRECT, 10 00 ack: True
2019-11-10 22:06:26 DEBUG Protocol: Passing msg to write handler: BroadcastCmdResponse handler
2019-11-10 22:06:26 DEBUG BroadcastCmdResponse: 37.c3.5b got msg ACK
2019-11-10 22:06:26 INFO Protocol: Read 0x50: Std: 37.c3.5b->4c.14.97 Type.DIRECT_ACK cmd: 10 00
2019-11-10 22:06:26 DEBUG Protocol: Setting next write time: 1573441586.490052
2019-11-10 22:06:26 DEBUG MsgHistory: Received 0 hops, total 3 for 11 entries
2019-11-10 22:06:26 DEBUG Protocol: Passing msg to write handler: BroadcastCmdResponse handler
2019-11-10 22:06:26 INFO BroadcastCmdResponse: 37.c3.5b device ACK response, waiting for broadcast payload
2019-11-10 22:06:26 INFO Protocol: Read 0x50: Std: 37.c3.5b->10.01.44 Type.BROADCAST cmd: 02 44
2019-11-10 22:06:26 DEBUG Protocol: Setting next write time: 1573441586.776060
2019-11-10 22:06:26 DEBUG MsgHistory: Received 0 hops, total 3 for 11 entries
2019-11-10 22:06:26 DEBUG Protocol: Passing msg to write handler: BroadcastCmdResponse handler
2019-11-10 22:06:26 DEBUG Base: Device 37.c3.5b get_model response with wrong cmd 2
2019-11-10 22:06:26 ERROR Mqtt: Operation failed - wrong cmd
2019-11-10 22:06:26 DEBUG Mqtt: MQTT publish insteon/command/37.c3.5b/session/2048748167 {"type": "ERROR", "data": "Operation failed - wrong cmd"} qos=0 ret=False
2019-11-10 22:06:26 DEBUG Mqtt: MQTT publish insteon/command/37.c3.5b/session/2048748167 {"type": "END", "data": null} qos=0 ret=False
2019-11-10 22:06:26 DEBUG Protocol: Write handler finished
2019-11-10 22:06:26 DEBUG Mqtt: MQTT writing
The text was updated successfully, but these errors were encountered: