mqtt is broken - Githubissues

grzegorz914 / homebridge-melcloud-control

Homebridge plugin for Mitsubishi Air Conditioner, Heat Pump and Energy Recovery Ventilation, publish as dynamic external platform accessory.

MIT License

49 stars 2 forks source link

mqtt is broken #87

Closed tobuser closed 4 months ago

tobuser commented 4 months ago

Since Version 16.13 the mqtt messages are broken. I downgrade to test this issue with older version an the last version without mqtt problem was 16.02.

grzegorz914 commented 4 months ago

What is broken exactly?

peibol81 commented 4 months ago

Sorry, but wat is mqtt and why is important in this plugin?

tobuser commented 4 months ago

Its only important when you what send Infos/sensor states to another system. In my case Home Assistant. https://en.wikipedia.org/wiki/MQTT

peibol81 commented 4 months ago

Thank you for the explaining.

tobuser commented 4 months ago

With 16.17. the problem with mqtt doesn't change. No mqtt Infos.

grzegorz914 commented 4 months ago

@tobuser any log, Mqtt debug?

tobuser commented 4 months ago

Unfortunately, Melcloud is still very sensitive. The refresh is set to 400s. A reboot seems to access Melcloud too early. I've noticed a change by Melcloud. When Homebridge Melcloud Control reports the error 'Login error: AxiosError: Request failed with status code 429, reconnect in 401s.', I can directly control the devices with the iPhone Melcloud app without any issues. This was not possible some time ago, as both Melcloud Control and the Melcloud app were blocked. It seems that Melcloud is giving preference to the app over Melcloud Control. I will wait until tomorrow and then create the debug files.

grzegorz914 commented 4 months ago

I have set refresh time to 120sec and will never locked by melcloud server. Are you have other integrations like Home Assistant, etc… with Melcloud?

tobuser commented 4 months ago

I removed all Home Assistant integrations last week, but I found now another session of Melcloud Control on a different host that I forgot to stop. Thanks for the tip. Logs later

tobuser commented 4 months ago

Here the log with the mqtt issue.

homebridge.log (8).txt

grzegorz914 commented 4 months ago

Try latest beta and get the debug again

tobuser commented 4 months ago

homebridge.log (9).txt

Only one Device "AC Wohnzimmer" publish mqtt

grzegorz914 commented 4 months ago

try beta 8 and get the log again

tobuser commented 4 months ago

The device "AC Wohnzimmer" have now another mqtt topic name. But no other devices with mqtt publish homebridge.log (10).txt