Hello! I’ve been wondering about a few things, perhaps you could help me understand…
What is the (original) purpose of EVU function? I can’t even figure out what it stands for, and Danfoss installation manual only mentions it briefly. It seems activating EVU prevents the compressor, the electric heater, and the flowline pump from running. But how is that functionally different from just putting the heatpump into an “off” mode? How are you using the EVU?
Another thing are the registers d102 Legionella peak heating enable, and d103 Legionella peak heating durations. Can these be used to trigger legionella function? Or is this simply enabling the internal scheduled run?
In my case, both of these registers were (and still are) set to 0. Does that mean the whole anti-legionella functionality is off for me? I haven’t changed the registers through ThermIQ, and these are not even accessible from the screen service menu, so that makes me a bit confused.
The best match for EVU I’ve found is “Elektrizitäts Versorgungs Unternehmen” and it will basically park the heatpump algorithms AND stopp all pumps until released. If adding a 10k resistor you will instead get “Lowered Night temperature” based on your settings in reg 59. ThermIQ-room2 boards with a mechanical switch has this implemented on board.
The benefit, I see think, is that the algorithm will start from where it was. A negative integral will remain and cause an immediate start wheras the OFF function will reset all states in the algorith (including salmonella cycles I believe)
I don’t think you can do that, there are somde discussions that these regs are wrongly named but in spite off better names they keep their current. There are still som exploration to do…
This “dashboard” code works on beta version 2.0.2. I have also tested versione 2.0.5 but it did not work for me. Let’s hope there will be an update soon.
I can’t see any obvious problems with the lovelace in 2.0.5. Just tried a copy paste from github into HA which looks good, at least form me.
Could it be that you are editing in the wrong place? You should do it as stated in the top of lovelace file…
# ################################################
# ##### ThermIQ Lovelace config. Add in Raw configuration editor
In HA do “Edit Dashbord” - “Raw configuration editor”, then copy and paste the lovelace file. Please replace _vp1 with _yourid if you customize your install or if adding more than one instance.
@ThermIQ The formatting in the file from github is incorrect.
@RH_Dreambox What didn’t work for you? I’ve looked at it now, and those things I tried was functional. Any specifics I can look for to see if I get the same?
@ThermIQ
When I, eirik_nor and most others create an object in the dashboard, we create it via the GUI and then the code from Github doesn’t work until it’s cleaned of unwanted characters.
Copying in the code as you suggest works, but I want more control over what I do because programming is not my best skill
And the reason I write Dashboard is because the name Lovelace is no longer used.
I’m also going to try upgrading to 2.0.5 again, but previous attempts have ended with the interface running amok and the heat pump switching to electric power.
EDIT
Now I tried again to update to 2.0.5 and it seems to work now. Maybe I did something wrong before.
Then I tried copying the Lovelace config directly into the raw configurator, but it didn’t work.
I got this error message…
Det går inte att analysera YAML: YAMLException: bad indentation of a mapping entry (2003:13) 2000 | badges: [] 2001 | cards: [] 2002 | title: Tablet i hallen 2003 | - type: entities --------------------^ 2004 | title: ThermIQ 2005 | theme: default
Ok,
If you want to add it as a “Add Card → Manual” the you currently have to unindent the lovelace_config file so that the first line starting with “-type: entities” appears without indentation.
There seems to be a bit of change ongoing, lovelace → dashboard as well as some new inbuilt statistics etc. I will put these fixes on the backlog and continue makeing sure the base functionality of the integration is working ok.
@ThermIQ
You have mentioned on your ThermIQ forum that if I want a “night-time temperature drop”, then I should do this by lowering the “Room indoor target temp”.
But if I instead connect the ThermIQ-ROOM2 EVU (307-308) in series with a 10 kOhm resistor, won’t I get a “night-time temperature drop” function when the EVU is activated?
Or is the ThermIQ EVU only intended to turn off the heat pump?
EVU function by adding a 10k resistor you will instead get “Lowered Night temperature” based on your settings in reg 59. ThermIQ-room2 boards with a mechanical switch has this 10k resistor implemented on board. Look at the labeling of the switch…
My ThermIQ-ROOM2 (3 months old) has no extra switch as you mention. Is there another model that has this switch or do I have an old model?
EDIT
Now I see that there is an LP model with an extra switch.
Possible bug.
I tested activating the EVU (without external resistor) and then the heat pump stopped immediately which is correct.
When I then deactivated the EVU, the pump started again, but now there is a red flashing square in the top window of the animation.
In the WEB interface there is no flashing square which I think is correct.
So what does the flashing square mean?
EDIT
The red flashing square disappeared after HA restart.
The red square is supposed to mean “stopped” and should be blinking as long as EVU is acitve. AND There’s a bug here, will fix…
The thermiq hw has gone through a couple of rapid changes during 2022 to accommodate for the explosive interest in energy monitoring. The new “daughterboard” kind of solution has the switch whereas the “cableconnected” solution exists in two version with one having a black jumper which can be removed for “10k mode”, the other not.
The “10k mode” is as of to today not advertised as a feature for any of the versions but might be there.
The new generation of thermia pumps, Atlas etc, are modbus whereas previous generations have mostly proprietary interfaces. I suggest asking Thermia for specs.
@ThermIQ
Is it possible to update the MQTT values from ThermIQ more regularly?
I log values to Influx in HA but some values are updated extremely rarely so there are big gaps in the graphs (up to 4 hours for some values).
It would be best if they were always updated every minute.
If you look at the MQTT message you will see that all values are Sent every 30s. The ThermIQ integration updates with every message, what happens after that is beyond my understanding
