Skip to content
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

Open
2 of 4 tasks
EmilionDK opened this issue Jan 28, 2025 · 9 comments
Open
2 of 4 tasks

Eeese Carl dehumidifier #2866

EmilionDK opened this issue Jan 28, 2025 · 9 comments
Labels
awaiting feedback Needs more information bug Something isn't working

Comments

@EmilionDK
Copy link

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.

@EmilionDK EmilionDK added the bug Something isn't working label Jan 28, 2025
@make-all make-all added awaiting feedback Needs more information device improvement Improvement to an existing device config bug Something isn't working and removed bug Something isn't working awaiting feedback Needs more information device improvement Improvement to an existing device config labels Jan 29, 2025
@make-all make-all moved this to 🔖 Ready in Tuya Local Jan 29, 2025
@make-all
Copy link
Owner

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.

@make-all make-all added the awaiting feedback Needs more information label Jan 29, 2025
@make-all make-all moved this from 🔖 Ready to 🏗 Stalled in Tuya Local Jan 29, 2025
@make-all
Copy link
Owner

You seem to be reporting two separate issues here.

  1. The Tank sensor is not working since 2024.12.2 due to the change you highlighted.
  2. If you try to set up the device again, it is not detected correctly.

Is the second problem also happening since 2024.12.2? Is is the start of that problem a different version?

make-all added a commit that referenced this issue Jan 29, 2025
The PR that introduced this change made the change for two models at once,
maybe on an assumption that if their Eeese Otto was different then the Carl
must be too. But another Carl user has reporting this is incorrect.

Issue #2866, partially reverts PR #2703
@make-all
Copy link
Owner

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.

@EmilionDK
Copy link
Author

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?

@make-all
Copy link
Owner

Just the warning message that comes out showing the dps received and closest matching config.
Don't bother going any further back than 2024.12.1, the reports of this issue (and there are many, but unfortunately no clear data) definitely started late December at the earliest.

@EmilionDK
Copy link
Author

Okay, I will test as much as I can and collect all logs, and report back today or tomorrow. :)

@make-all
Copy link
Owner

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)

@EmilionDK
Copy link
Author

So..... This is random, but it works now with adding the dehumidifier..
And there are no errors in the logs.

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.

@EmilionDK
Copy link
Author

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'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback Needs more information bug Something isn't working
Projects
Status: 🏗 Stalled
Development

No branches or pull requests

2 participants