-
Notifications
You must be signed in to change notification settings - Fork 611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eeese Carl dehumidifier #2866
Comments
I'll look at the differences between 2024.12.1 and 2024.12.2 in detail. The change you highlighted would only affect the tank sensor, not detection of the device, so there is a more fundamental problem there, but it does fit with a sudden increase in reports of devices returning no data. Possibly there was an upgrade to the underlying tinytuya library around then that caused something to go wrong at a lower protocol level. |
You seem to be reporting two separate issues here.
Is the second problem also happening since 2024.12.2? Is is the start of that problem a different version? |
The first issue is fixed in the latest release, but the second issue is one I want to track down, as I am not sure where it is coming from and there are multiple reports starting about 2-3 weeks ago about devices suddenly not being detectable since they are not returning any data. Based on information on other reports, it is not related to the tinytuya library upgrade as I first thought, and your information backs that up, as it would have appeared in 2025.1.0 and gone away again in 2025.1.1 if that was the cause. |
Is the second problem also happening since 2024.12.2? Is is the start of that problem a different version? I haven't tested all version, by deleting the device and adding it again, only in version 2025.1.1 But I can test it, are there any specific logs you would like to see when I do it? |
Just the warning message that comes out showing the dps received and closest matching config. |
Okay, I will test as much as I can and collect all logs, and report back today or tomorrow. :) |
Abd probably Device Diagnostics from one working and one non-working version. (I guess for the non-working one you will need to choose one of the listed wrong devices) |
So..... This is random, but it works now with adding the dehumidifier.. Short info: 2024.12.1 - Add device Works, and water tank works 2024.12.2 - Add device Works, and water tank doesn't work 2025.1.0 - Add device Works, and water tank doesn't work 2025.1.1 - Add device Works, and water tank doesn't work 2025.1.2 - Add device Works, and water tank works after the issue was fixed. |
I have found this that only is in the logs after ver. 2024.12.1 and is in all other versions WARNING (MainThread) [custom_components.tuya_local.config_flow] Unable to fetch data model from cloud: 'str' object has no attribute 'keys' |
Description
Hey :)
For som time now. Eeese Carl dehumidifier stopped working properly.
Controls work as they should. (If you don't remove the device and start over)
But the Diagnostic reports incorrectly
The "Tank" status is not working.
2024.12.1 - Works
2024.12.2 - Do not work properly
2025.1.0 - Do not work properly
2025.1.1 - Do not work properly
If I remove the device and start from scratch, in the new versions it can't find the Eeese Carl dehumidifier anymore.
If I go back to 2024.12.1 everything works as it should.
I assume some changes have been made that affect this device?
Maybe this is the reason why it doesn't work anymore?
#2703
I don't want to go crazy and send a bunch of logs now, but if there's anything needed, then I will send it.
Steps to reproduce
No response
Expected behaviour
No response
Additional context
No response
Confirmation
I am sure this is a bug or improvement, that is well enough described that it can be implemented.
If this is for a specific device, the device config is mentioned above, or diagnostics are included.
Log messages or diagnostics relevant to the issue are included.
This is not requesting addition of a new device.
The text was updated successfully, but these errors were encountered: