A new service rinnaitouch.rinnai_set_time is now available in addition to a time setting binary sensor that monitors if the unit is in time setting mode.
If the unit goes into time setting mode by itself (an issue reported in the community), this sensor can be monitored and the service call be made. One should be careful not to make the call too soon as not to interfere with an actual time setting event.
An automation like this should fix your problem @groutley :
Awesome!
I’ve updated to the latest release and setup automations,
One question to clarify,
In the Call service for the perform Action, I gather I do not select the ‘set time’ option and it will therefore set it to the HA system time?
When I try to call service under dev tools, if I select set time or not, it is not updating the time on my nc-6
Which out of interest is flashing the incorrect time, and your time seting mode sensor is ‘on’ currently
Hi, sorry for delay, daughters birthday put a delay to my plans, not entirely sure what happened,
Because I had debug enabled, it was filling the logs so fast with errors that HA ran out of space and crashed. I had to purge all of user.log and syslog to free up 60G and get HA up again.
Bottom line I lost all the logs.
When HA was down, I tried using the Brivis app, and it just showed ‘initializing’ once it connected to the module. So I manually set the time on the nc-6 and the Brivis app came good.
Closed that app and got HA up and running and all good/normal again.
So, I missed the debug capture, lost all logs of the condition and havn’t tried manually testing time change yet… maybe tomorrow!
Yes it was only selectively added for this addon.
But from what I saw of it, there were 10’s of lines per second being added every second due to comms issue. Not what should be a normal situation.
Parsing the data should not take too long, but when I had a look last week, there are a lot of values I have no clue what they could mean. I can make a list of them and we may be able to figure them out together by you changing settings on the unit and observing the debug logs and we can build from there.
So next steps: parse the system state into something useful that can be mapped and allow raw commands to be send via another service.
This week is incredibly busy, but I’ll try next week.
Revisiting this topic after a while and noticed the new HACS integration. I have an Evap (with pump and fan). I have the homebridge method setup and working and am considering moving over to HACS integration. I installed it but it only finds the fan (not the pump).
Do I need to shut down the homebridge setup up first? Does anyone have any ideas about the best way to migrate from the Homebridge setup to the HACS setup?
Thanks in advance.
** Update **
I disabled the plugin within homebridge and restarted the Rinnai box and I can now see the pump and wetting sensors and pump switch is now active.
Thanks for that… just reading through the documentation, a couple of questions:
“There is support for an external temperature sensor, to avoid having 0 degrees in the UI all the time” - how do I add this or can it only be set through setup? Do I need to set a zone for this?
“You can manipulate the Fan as required.” - Can the fan speed be set or is it only on/off?
When setting up, you can specify the name of the sensor entity. It cannot be done later. You may have to redo the setup.
The fan speed can be set when using fan only mode for heater or manual preset mode for evap. You can achieve fan only for by turning the pump off in manual mode. The fan speed will still display as degrees Celsius in the UI, nothing I can do to change that.
Team - I’m stuck! very much a newby to HA so hopefully I’m just doing something basic wrong that one of you clever people can help me with, I’ve installed as per instructions in github, then added the integration, then added the IP address and other info as requested… but… nothing. Just say’s it’s unavailable. Any ideas?