eschava / broadlink-mqtt

MQTT client to control BroadLink devices
MIT License
222 stars 61 forks source link

No temperature data from RM Pro+ #40

Closed Sc0th closed 5 years ago

Sc0th commented 5 years ago

Hi, Thanks for this tool, it is excellent!

Only thing missing is the lack of temperature date from the RM Pro+, is this in the pipeline?

Cheers!

eschava commented 5 years ago

Have you tried config parameter broadlink_rm_temperature_interval ? Instructions are here https://github.com/eschava/broadlink-mqtt#subscription-to-current-temperature-rm2-device

Sc0th commented 5 years ago

Hi, thanks for getting back to me, I have 5 devices in total, the 3 'RM Pro' devices are publishing the temperature perfectly, the two 'RM Pro+' devices report 0.0 - so it does appear to be a specific issue with the + models.

broadlink/RM2_ee_fd_32/temperature 28.4 broadlink/RM2_18_09_a8/temperature 0.0 broadlink/RM2_ee_fe_d6/temperature 32.0 broadlink/RM2_ee_fd_62/temperature 26.9

Noticed that since adding the + devices, I am seeing this very frequently in the log -

[2019-04-28 16:45:29,929] ERROR Error Traceback (most recent call last): File "/apps/broadlink-mqtt/broadlink-mqtt.py", line 311, in broadlink_rm_temperature_timer temperature = str(device.check_temperature()) File "/usr/lib/python2.7/site-packages/broadlink/init.py", line 570, in check_temperature response = self.send_packet(0x6a, packet) File "/usr/lib/python2.7/site-packages/broadlink/init.py", line 305, in send_packet response = self.cs.recvfrom(2048) timeout: timed out

eschava commented 5 years ago

Issue https://github.com/mjg59/python-broadlink/issues/133 says that RM Pro+ has no temperature sensor

Sc0th commented 5 years ago

Hehe, yes that is indeed correct, I will get back under my rock, thank you for humouring me :)