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
305 stars 96 forks source link

Wrong buttons showing and expected buttons missing #555

Closed rubernck21 closed 1 year ago

rubernck21 commented 1 year ago

I have a Broadlink RM4 Pro that I just purchased. got it setup on my network and its controlling my wall mounted Twinstar Home heater.

I just installed this plugin and going through the JSON code I believe that I have it setup right, but only the Learn & Scan Frequency buttons are showing...even though they should be turned off. I am a JSON noob, so it's probably my fault, but I asked in the Facebook Hoobs group and only 1 person who replied said that the plugin is broken...so I'm here now.

https://pastebin.com/r98fFf5E

Hoobs version: 4.2.8 Node version: 16.19.0 Homebridge version: 1.5.0

tientmit88 commented 1 year ago

it should be like this one Your devices have to under accessories "hosts": [{ "address": "192.168.0.208", "mac": "EC:0B:AE:D8:A0:60", "isRFSupported": true, "isRM4": true }], "accessories": [ "type": "switch", "data": { "power on": "xxx", "power off": "xxx" } ]

rubernck21 commented 1 year ago

Thank you for responding to my issue.

So, im taking this to believe that the extra { and } are not needed? When I run this in jsonlint, I keep getting errors. Here is what Ive been able to get together without jsonlint giving me any errors.

{ "platform": "homebridge-broadlink-rm-pro", "name": "Wall Heater", "hideScanFrequencyButton": true, "hideLearnButton": true, "hideWelcomeMessage": true, "hosts": [ { "address": "192.168.0.208", "mac": "EC:0B:AE:D8:A0:60", "isRFSupported": true, "isRM4": true } ], "accessories": [ { "type": "switch", "data": { "power on": "26001e012a0d2a0c0f272a0d", "power off": "26000401270e280e0e29280e" } } ] }

tientmit88 commented 1 year ago
image

here is the full config You should change bridge & config port. I added switch name I think it will work

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.