It’s a combination of what is in the GitHub repository and my own. I started doing it before the GitHub yaml data was there. His is much more eloquent than mine because I am a beginner in Modbus.
I’d use the GitHub version and just pick and choose what you want. I didn’t want everything because I was more interested in monitoring than controlling. I figured one wrong command from me could stuff things up.
So does my EVO heat. I got sick of it, and now I just have an automation that turns on both the heatpump and the booster at 11 am, when my free power starts. I set the time on the unit to 5min slow and then set the timer on the unit to 11 am also. At least that way I have a fail-safe. I have also set my booster target temp to 80 degrees that way I know the boost will run for the 3 hours, even when the heatpump stops at 60 degrees.
Ok so thanks to this thread. I have my iStore 270 reporting in home assistant. I used the atom and the yaml in the github. I have some questions though.
In my verbose logging, i get some warning messages and some timeout messages I need clarification on.
I get these every now and then. theres a few different hex codes though.
I get a heap of CRC when I try to turn heatpump on or off also
[09:40:46][W][modbus:135]: Modbus CRC Check failed! 89B1!=4C80
[09:41:01][W][modbus:135]: Modbus CRC Check failed! 3D19!=B4
[09:41:01][W][modbus:135]: Modbus CRC Check failed! C071!=00
[09:41:01][W][modbus:135]: Modbus CRC Check failed! C071!=00
[09:41:01][W][modbus:135]: Modbus CRC Check failed! C071!=00
[09:41:01][W][modbus:135]: Modbus CRC Check failed! 20CD!=C01
[09:41:01][W][modbus:135]: Modbus CRC Check failed! C071!=00
[09:41:01][W][modbus:135]: Modbus CRC Check failed! C071!=5200
[09:41:01][W][modbus:135]: Modbus CRC Check failed! 601E!=A2
[09:41:01][W][modbus:135]: Modbus CRC Check failed! C071!=00
Can I ask anyone with an iStore what the “disinfection target temp” was on their units? Know it’s for legionella removal just curious what others have theirs on.
I had a go at doing this myself too. I couldnt even get the hours and minutes to read. I ignored the internal tag just to see what it would get, only reads 0.
I don’t think I changed mine, and it’s reporting as 70 degrees currently.
What app are you using? My wifi module only shows up in the Handy Heat Pump app not the AquaTemp one, but I can’t login to the HA plugin with any of the options it just says invalid credentials
@TravCorp
I have a wifi for module for EvoHeat if you want it. I am in Melbourne.
I dug into this a little bit with my limited knowledge. I was able to use the enable/disable bit for the clock to reset the clock somehow. Im not exactly sure on its true usage but it definitely changed the time and date. I was wondering if a script could periodically set the hour/minutes based on HA internal time?
I get lots of CRC Check failed in the logs too.
The only thing I can find in researching it is that it might be something to do with the wiring, but I can’t make it go away. It does not seem to affect operation.
I was thinking same. Maybe some pink shielded cat 6 would work better. Not really worried about it for now though. They’re only warnings.
Hey mate,
would there be any reason I couldnt use a tail-485 module rather than the base you used here?
Im talking about these ones. I realise I’d have to change the pin defines.
I don’t see why not. But I am not an expert in it. I just followed what @epayne787 did as a path of least resistance.