For me the most important function is being able to switch off and on as well as to be able to read the temperature. Collector temp and temperature difference is not a big issue.
Hi Johann.
Which Sonoff device did you use?
(TH Origon, THE Elite, TH10 / TH16)
Would love to know how it is working out.
I have had a similar idea for a while, but did not know you could use their temp probe with Sonoff smart switches. I want to monitor and control the temp of the geyser based on a schedule, and turn off geyser during load shedding so it doesn’t drain the batteries on the inverter when insufficient PV solar.
I already have a Geyserwise TSE setup on a Thermal Solar Geyser, so probably replace that with Sonoff TH device and a Sonoff Power device to measure the consumption.
Thanks - I did this and its working great. localtuya for local access and fast home assistant access. Normal Tuya app for cloud access (as and when needed). Next step I need to automate my geyser schedule around loadshedding. I have the ESP integration and have the loadshedding schedule in HA. Any tried and testing automation yamls you can share for doing this?
I used the history_stats built in integration in home assistant to count the time the element is on, per day. This gives me a run time throughout the day, which I use as a proxy for my electricity spend for my geyser.
Thought I would add my setup to the discussion. I also went the route of removing the WBR and soldered a ESP32-C3 in its place. Thanks Jack for the pics showing which pins go where, it was a big help!
But instead pf going the custom firmware route I installed ESP Home and used the tuya component to get the board working. For those who are interested here is my complete ESP Home configuration file.
The baud rate needs to be set at 9600. I tried other values but the component stopped working.
Also if you use the marked UART (RX/TX) pins, these are the same pins that ESP Home uses for its serial logger so you need to disable the logger in the configuration.
This has worked very well for me and I am happy with the results.
I’ve figured this out now - posting incase anybody else is having the same issue.
So the default available attributes are based on “standard instruction” there is an option to change to “DP instruction” which modifies the standard payload and includes all attributes. To do this, you need to go to the device, and select “Configure Control Instruction Mode” then select “DP instruction mode”
Depends on your setup and how much info you want to control/report on. The standard instruction only exposes 3 attributes, if you want the additional attributes (14 in the case of the Geyser Wise Max) then you need to use DP.
I came across this post a few days ago. I bought a TSE1 Tuya board and replaced the Tuya module with a ESP-12F.
I am running ESPHome on my Home Assistant and I added the chip to it using code gtb put up earlier.
After installing the board it worked, I could turn on the geyser, check the temperature, set the max temp etc.
After a reboot of the ESP it stopped getting data. I can still manage the ESP fine but no data.
This is what I get.
[19:16:19][C][tuya:041]: Tuya:
[19:16:19][C][tuya:046]: Configuration will be reported when setup is complete. Current init_state: 0
[19:16:19][C][tuya:049]: If no further output is received, confirm that this is a supported Tuya device.
[19:16:20][E][tuya:433]: Initialization failed at init_state 0
[19:16:29][E][tuya:433]: Initialization failed at init_state 0
[19:16:44][E][tuya:433]: Initialization failed at init_state 0
Hi, I’m very new to HA, and have opted for localTuya, which is working. I’m battling however to get all the entities you’ve shown here. Also don’t have DSP 10 for current temperature. Have used Sensor, not sure if I should use climate.
Hi @HomeGeorge, please ignore my previous post on temperature. I got it working. I do however have a question around the enity type for DSP10. You used sensor, and it works well. I want to however use CLIMATE, because that will allow for an HVAC type control on a mushroom-climate card, which works pretty well too. Sensor entity type will unfortunately not cut it,
Any advice?
Will also be nice, to know what you used in your sample dashboard.
I’m assuming you have not done anything to the device (just the Tuya enabled Geyserwise board).
I am keen to create MQTT - Tuya link in the Homie standard to automatically populate devices discovered on Tuya to MQTT. I see it’s a little supported Home Assistant but the Homie standard is supported by OpenHab. In OpenHAB these devices are then autodiscovered based on Homie standard.
I’m using OpenHAB so not going to switch anytime soon.
I also want to summarise the approaches to solve this problem found on this thread:
Involves the Geyserwise WiFi module and their API. I don’t think this is sold anymore?
Geyserwise Tuya Boards which are sold and an easy upgrade to an existing Geyserwise Max or otherwie (e.g. @viv-01 's approach)
a) This device could be paired with the cloud and used as is using cloud connection.
b) This could also use a local tuya connection.
c) A combination of the above.
Geyserwise Tuya board but with a chip replacement and firmware for that chip (developed by @Jack_Kitley in this thread.
Are these all the solutions?
My questions relates to 2 (a-c). Does that allow access to the full range of variables (14 it seems to be for the Max product). @the_brains seems to have solved this? Does this apply to the Tuya solution? Is this cloud?