The 101 seems to be True when the dehumidifier is disconnected from the power.
I’ve tried three Tuya integrations so far:
Cloud Tuya – very basic, you can just switch it on/off. It considers the dehumidifier to be a humidifier. It has an input for target humidity, but it is apparently ignored.
Localtuya. Not user friendly, but it seems to allow you to configure everything. Just after adding a device, it looks dodgy (device becomes unavailable), but after few Home Assistant restarts, it seems to work perfectly fine. At the moment, I’ve mostly replicated the functions of Tuya/Rohnson apps in Home Assistant. I don’t decode the dehumidifier state number. Target humidity cannot be set and it doesn’t work well at all (sometimes, it’s unavailable. Maybe it would work as an enum or a string. However, I don’t care much. This more or less duplicates the purpose of Home Assistant. There is also a timer field, which also works read-only, but maybe it cannot be set by the API; Even the official app doesn’t allow user to set it.
Tuya Local (not to be confused with localtuya). I was able to connect the devices but it doesn’t seem to be much powerful with this particular device. It didn’t even allow me to use dehumidifier type for this.
At this point, I am pretty ready to disable outbound connection for the dehumidifier. I’ve a basic dashboard that mostly replaces the app (and adds few extra things):
Just a correction to 101 and 105: As far as I see, they are always of or unavailable. I still think one of them signifies defrost, but I cannot confirm it in this weather.
Automation: I take values from multiple sensors, compute maximum and decide based on this maximum. There is a tri-state sensor (on/keep/off) that tells the dehumidifier what to do. The ”keep“ state is essentially a hysteresis.
Future automation: I’d like to put a humidity sensor on my drying rack. The automation will be a bit different, as it should probably start the dehumidifier at lower levels.
can you share the configuration you used to build the buttoms and getting the values (for temp and humidify).
I’m having a bit of issue trying to pull the values, I already identified which DP controls what and what’s the values that can be used but putting everything together it’s another fight.
The target humidify used by your config is a slider, on mine I have define values between 30% and 70%, does yours use something similar and you used the slider to go to those values in the background?
@v6ak How far did you get with this? It looks absolutely close enough for my use case. I just want to turn on/off based on weather and/or Windows open, etc.
I have localtuya installed and am using it for a space heater but what do I need to do to make this happen?
I’ve added all the field as separate entities. (This is true even for a fan that has it’s own entity type – the dedicated entity type didn’t work well.) You can look at the table above. The types aren’t explicitly mentioned (and I don’t remember them by heart), but they should be more or less obvious from the description.
So, as first, you can pick switch type, select id=1 (assuming you have the same numbering – I am afraid there isn’t easier way than to try it) and add entity for switch. When you finish adding the entity, you will be asked if you want to add another one. It isn’t much user friendly, but it’s doable.
Yeah, I think I’m getting there. My dehumidifier isn’t the same as yours so the mappings are a little different.
I can control it on/off and view current humidity and target humidity right now.
I can view fan speed too, also weirdly 0 and 3 for low and high but can’t set it or target humidity for some reason.
There are worse integrations though, heh.
EDIT: Actually, I was wrong with fan speed, it’s 0 and 2 for me and I am able to control it now. Attempting to control Target Humidity has been unsuccessful though. A sensor type allows me to view just fine. I’ve tried number type and select type and both, if I try and change anything at all, reset it back down to “CO”.
@tretabyte The slider comes from using the number type. It doesn’t work for me either though.
I ended up finding running status as well. So I have 1 variable left unmapped, no idea what it does. Been 0 every time I looked at it. Probably timer related but who knows. Don’t really use that.
I don’t use target humidity, because I control the dehumidifier via HA instead. In HA, I can use multiple humidity sensors and pick the highest value. Actually, the humidity at windows differs much from humidity at dehumidifier.
Obviously, I could do the same though. I have the humidity reading of course and can turn on/off on whatever I want. Just more about trying to get full functionality exposed.
Give a look to Inventor Eva ION Pro Wifi line of dehumidifiers: they’re wifi enabled and Home Assistant integrated through HACS… I’ve read excellent comments and probably I’ll go for one of them…
Is this available in the US? 5 minutes on Google doesn’t turn up much around here.
Either way though, the dehumidifier needs to be a dehumidifier first. Any bells and whistles are really secondary.
That being said, the one I linked above has been great and it’s integration through localtuya works perfectly now. I can’t imagine needing anything else.
I am considering splitting this topic to multiple parts:
For adding the dehumidifier to the HA, you need nothing from the code. You just need to decide between Tuya cloud (requires Internet, easier to do, supports just on/off) and localtuya (works without Internet, needs more initial config, all the features except timer and target humidity work for me, I think). More details are in [WIP] Smart dehumidifier - #9 by v6ak
You also might want to add some automation (e.g., run the dehumidifier when some humidity sensors reports high humidity) or a dashboard. That’s only useful after you have successfully added the dehumidifier. And that’s the point where you might want to use some of the code.
Add the dehumidifier using localtuya instead of Tuya cloud (as mentioned in my previous post). With Tuya Cloud, you probably can have just on/off, which is simply not enough for such dashboard.
Add some dashboard. You can either create your own (maybe just add entities created in the previous step) or use the code from my dashboard (and adapt it to your needs).
Some parts of my dashboard need some automations or sensors defined in the additional files. Maybe you will want to remove/adjust the parts of the dashboard, maybe you will want to add the automations/sensors.
Question, do you have the listing for what each property is for the Honeywell you linked? Ive got the same one and just ran into this post and now have a hankering to try it.
