search

kiwi-cam / homebridge-broadlink-rm

[This fork supports TV accessories] Broadlink RM Mini and Pro plugin for homebridge: https://github.com/nfarina/homebridge
Apache License 2.0
304 stars 95 forks source link

Error "ensure the device is not locked" but it is not #549

Closed bondskin closed 1 year ago

bondskin commented 1 year ago

I keep getting the following error message until I restart Homebridge. Then it fails again after a day or so

[18/12/2022, 21:08:31] [BroadlinkRM] [ERROR] Denon sendData (no device found at a0:43:b0:54:4d:89, ensure the device is not locked) [18/12/2022, 21:08:31] [BroadlinkRM] Acer setSwitchState: false [18/12/2022, 21:08:31] [BroadlinkRM] [ERROR] Acer sendData (no device found at a0:43:b0:54:4d:89, ensure the device is not locked) [18/12/2022, 21:08:31] [BroadlinkRM] LG setSwitchState: false [18/12/2022, 21:08:31] [BroadlinkRM] LG setSwitchState: already false (no data sent - B) [18/12/2022, 21:08:32] [BroadlinkRM] [ERROR] Acer sendData (no device found at a0:43:b0:54:4d:89, ensure the device is not locked) [18/12/2022, 21:10:25] [BroadlinkRM] Boxen setSwitchState: true

To Reproduce Restarting Homebridge and wait for another occurrence, mostly on a daily base.

Expected behavior Devices are correctly used

Config: "name": "Boxen", "type": "switch", "host": "ec:0b:ae:9e:9c:14", "data": { "on": "26006000000123951213123712131213123811131238123811131213123812371213123812371213123812371213123812180d1212381238121212131238121312371238121312121200051e0001254b12000c4d0001254b12000c4d0001254b12000d05000000000000", "off": "2600580000012692141114361311141114361411133614361411131114361436131114361436141014361436141014361411141114351436141114101436141114361336141114111400051b0001274914000c4c0001264a13000d050000000000000000000000000000" }

Additional context I added the section "hosts": [ { "address": "192.168.2.134", "mac": "a0:43:b0:54:4d:89", "isRFSupported": false }, { "address": "192.168.2.200", "mac": "ec:0b:ae:9e:9c:14", "isRFSupported": false } ],

but this did not help, actually the devices didn't react at all.

bondskin commented 1 year ago

seems to be linked to this bug report

OwenWright8 commented 1 year ago

I keep getting this exact error, hopefully, it gets fixed soon.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.