Cloud-Free Control for Niveo Smart Tuya Fan Heater Using OpenBeken and Home Assistant

You can't have empty client topic, how would you be able to tell the difference between two devices if they have the same blank name?

Futhermore, you can't change client topic after doing HASS Discovery. You must redo discovery after every client topic change.

>>21857259

I guess this is where I am new to OBK, haha. With Tasmota, the devices basically use their short name as the default, so I implicitly assumed the same. I got fooled by the HA discovery lines, where I thought it used the full name (also for the entities).

I will delete the device in HA and rediscover and report back.

Well I can add this behaviour for you, if you want.... it's certainly better than getting bugged mqtt topics

>>21857279

I think I do know now haha. It works!!! Thanks so much. I will then try to create a Home Assistant climate entity out of the single ones we have now and share it here as long as we do not have native climate entities in OBK.

As for MQTT, I think Tasmota did a decent job for sane default settings, maybe this is worth copying? Or just using the short name as default as this is anyway also used for HA auto-discovery, so it is a sensible default IMHO. And maybe just simply adding an error when base topic is empty?



We got this now in Home Assistant and the controls work, so it should be easy to construct a climate thermostat from that.


Added after 6 [hours] 30 [minutes]:

Beauty!
So I tweaked this a little and now we have a wonderful cloud-less thermostat for this heater!
This can easily be adapted probably also for other Tuya heaters with slight tweaks for the modes and so on.
I hope this is valuable!





niveoFA73D3 obviously has to be replaced with your MQTT base_topic. Be mindful this uses HA's 'MQTT climate' integration. You are basically free to map whatever for preset_modes, but modes have to be a subset of their default values. swing_modes is recommended to be just 'on' and 'off' then you get the nicest UI integration and localization.
fan_modes is again arbitrary and can be mapped by you.
I removed some of the preset modes as they do not really make sense when used with home assistant where doing automations is much more powerful than whatever they ship by default. You can of course comment them in if wanted. Just be careful to replicate the enum mapping exactly as in your autoexec.bat on the device otherwise it won't match, hence I have all values in the mapping even if they are not in the choice list.

Thanks again for everyone who participated here, pretty crackin result for one weekend I dare say.