Madimack Pool Heater no longer working about tuya-local HOT 10 CLOSED

Ensure the pool heater is on, and no other device (app) is connected to it.
The Tuya module only supports a single local connection, so if the app was started on a phone, it may block Home Assistant until the app is force closed, and if some time has passed, Home Assistant seems to mark the device as offline, and won't retry for quite some time unless you restart Home Assistant.

from tuya-local.

Was this problem ever cleared?

from tuya-local.

Running into this as well. All was working fine for the past months and then my Madimack heater is now unavailable as well. My logs show the exact same as @mvnixon. I checked the local key and also all the settings at iot.tuya.com and all looks well.

Has anyone found a fix? Or any suggestions on how to debug more?

The only thing was I did get an email from Tuya that my "Tuya IoT Platform" free trial was expiring (around the same time it stopped working in HA). Not sure if that is related. I see others discussing it as well:
https://community.home-assistant.io/t/email-from-from-tuya-iot-free-trial-is-expiring-today-tuya-official-integration/350181

from tuya-local.

Ah I think I got it working. Downgrading to v0.11.3 of tuya local in HACs and then removing and re-adding the integration got things going. I guess some issue with the device ID changes as per:
https://github.com/make-all/tuya-local/releases/tag/0.12.0

from tuya-local.

The unique id changes would not have affected the Madimack device, as it does not have any secondary entities. There was an update to the underlying version of tinytuya from 1.2.8 to 1.2.9 in 0.12.0 as well but I don't think those changes would have affected a previously working device either. The "latest version" on Aug 6 when this report was made was 0.9.1, so the original problem does not seem to be related to a change between 0.11.3 and 0.12.0 anyway. I suspect whatever is happening that removing and re-adding may be the solution independant of which version of the integration you are on. Removing the device from the integration config, rebooting and re-adding might work also if the problem is a corrupt device config.

from tuya-local.

If you have backups of the broken version, it might be interesting to compare the configs for the device in config/.storage/core.config_entries to see what is different.

from tuya-local.

You are 100% correct! It wasn't the version that made the difference, it was removing and re-adding the integration. I upgraded back to 0.13.0 and the device broke again. I then removed the integration and re-added it and it's all working again 👍

from tuya-local.

OK, but it does seem then that there is a problem with the migration for this device. Which is strange, as there does not seem to be a problem in general, and there isn't anything special about this device's config that I can see.

from tuya-local.

I had upgraded a few versions in the past and had no issue so maybe it was just jumping from one specific version to another and it will work fine in the future.

from tuya-local.

There seems to be a workaround available of re-adding the device, and it is unlikely that anyone will provide sufficient info to identify what the actual problem is after all this time, so I am closing this issue.

from tuya-local.