Closed tretabyte closed 2 years ago
Hello @tretabyte, the MSXH0 implementation provides both:
Thus the humidifier function is not implemented as a standard humidifier in HA but you'll have the option to use the corresponding 'select' to choose the working mode. I've tried in the past to use the HA humidifier entity for the matter but it was behaving a bit erratically and the UI was 'inconsistent' with the device state: the MSXH0, as an humidifier, is pretty different than what HA thinks an humidifier should behave so the choice to use a plain 'select' entity to set the working mode of the device.
I see it would be nicer to have a standard humidifier card for the device but it really didn't work well at the time. I'll maybe take the time to re-test this and see if something has changed on the HA side in order to correctly manage the MSXH0 (the code is still there..just a bit commented out..)
The main issue lies in the fact that the HA control for humidifier works by managing the humidity level (like a thermostat) which the MSXH0 does not provide.
Hi @krahabb,
Thank you for the feedback, any advice on how we could turn this into something useful, I mean we know we can control the type of vapour we want to release using the select entity and I'm guessing the light is just that, to light it up and pick some colour, simple 2 entity card with a bit of extra magic maybe?
Hello @tretabyte , Sorry, I've just lost track of issues and the likes during summer season... To be honest I'm really bad at designing UI's so I really have no idea :(
Version of the custom_component
Latest available (v2.6.1)
Configuration
Describe the bug
The MSXH0 gets detected by the integration and added to HA, the entity it created to turn on/off gets mapped as light instead of something else that could be used on humidifier cards. Maybe I'm lacking some skills on HA that could change this internally and if that's the case I'm sorry for raising this "bug"
Debug log