Hi
What problem were you having with the Tasmota? I have been using it without much problem with my Eq3s. I had no problem using it with one that I paired when I connected directly to an RPI I had HA running on.
Yeah odd. I think some of mine are 1.46. You sure it’s just not good enough signal from ESP32. Bring the 2 close together and see then if can alter temp setting etc…
mmm… no, I have not arrived to integrating it to homeassistant.
The device is discovered correctly and responds to some commands correctly.
I have discovered that it responds to state command too, but you need to add a payload like state 0, then it answers correctly.
I am just looking at mqtt and giving trv commands
May you provide any article describing how to correctly configure tasmota with EQ3 valves?
I have read the documentation and several other forum posts, but it does not seem to work correctly.
May you provide your BLE and setoption19 and setoption59?
Polling is not working.
And I see that there you need a lot of work to integrate it in homeassistant, not autodiscoverd as the tasmota sensors.
HA doesn’t discover it like normal Tasmota or mqtt. You create the entity in config.yaml like in my example above. I use a different current temp as EQ3 doesn’t use a real temp.
You shouldn’t have to reload core . Just go to developer tools and then Yaml and select manually configured Mqtt entities. Then it should make the new entity climate.your device. Even if you put my yaml in exactly it would still create the entity , but of course it wouldn’t get any values.
Now that it is working in tasmota, I have removed all from HA and reconfigured it.
Now I can see the thermostat correctly, and works. I couold add it to a panel.
Thank you for your help.
Now I need to learn more about how to configure devices in HA using yaml in order to get them working as I want.
Anyway, probably I am going the zigbee route.
These valves were interesting as being a cheap option, and having a tasmota device to read the temperature.
But now they have the same price in amazon as other zigbee valves that you don’t need to be polling in order to get their parameters, so the traffic in mqtt would be reduced.
The bad news are that you need a coordinator and configure other network with other protocol and deal with wifi/zigbee interferences.
I think I will try one with one zigbee coordinator to see how it works.
MQTT is very low resource user so wouldn’t worry about flooding it too much. Battery drainage is more a problem if poll often. For TRVs you don’t need to access every few seconds as temps change so slowly. I’ve found the batteries last about 8 months. I even pull them in the summer. Good luck with your search.
I am still trying them. I like their simplicity, not having to deal with zigbee protocol and network, and being able to configure from tasmota.
But their interface are not so good, and they respond slowly to commands.