eschava / broadlink-mqtt

MQTT client to control BroadLink devices
MIT License
221 stars 60 forks source link

Issue with messages following upgrade #99

Closed oenc closed 2 years ago

oenc commented 2 years ago

Hi, I recently had to wipe my rPI which has been running a previous version of this from around 2018 (and it's been brilliant thank you!). I took a copy of the commands folder as I have 4 remotes programmed in.

I've re-installed everything with the updated instructions etc.. and I have the MQTT service running. However when I send it messages, the log shows "WARNING Unrecognized MQTT message replay" (or auto, or any other message I send).

I'm using the inbuild samsung commend to test rather than any that I copied over.

A bit of the log:

[2021-08-29 08:40:19,142] DEBUG Connected to 'RMPRO' Broadlink device at '192.168.0.3' (MAC b4:43:0d:ee:fc:48) and started listening to MQTT commands at 'broadlink/#'
[2021-08-29 08:40:19,174] DEBUG Connected to MQTT broker, subscribing to topic broadlink/#
[2021-08-29 08:40:27,759] DEBUG Received MQTT message broadlink/tv/samsung/power replay
[2021-08-29 08:40:27,760] WARNING Unrecognized MQTT message replay

I'm using mosquitto_pub to send this topic / message for testing, but will be using node-red to send the actual messages, and this is having the same issue when the messages arrive.

I haven't made any changes to mqtt.conf or custom.conf

Any thoughts on what to try next?

oenc commented 2 years ago

Resolved by adding:

or device.type == 'RMPRO'

to line 185 of mqtt.py

eschava commented 2 years ago

Thanks, integrated the fix