Am I completely on the wrong track? Is python not the way forward and only the method with AppDaemon 4? I saw I had to install AppDaemon 4 as well when using your add-on from HACS, that’s why I have chosen to go for the python way as explained in this thread. I thought it would be easier. But if you say the App Daemon is the only way to go forward, please let me know.
I can see this thread hasn’t been used for a while… should I look somewhere else? is it outdated? I’m looking for a bit more explanation for the installation. I have been searching the whole day, so any help is very welcome.
@Kitser, what did you add to the configuration.yaml? (besides adding “python_script:” to enable HA for python)
I’m using python script and added the code to the automation.yaml and edited it to my temperature/sensors. I can see the Python script is being triggered as the last date/time is set, I cannot find a log (logger set to default: info)
I can see the script is reading the correct temperature but not setting it.
Could it have something to do with the naming of my entities? I see in this thread with python it shouldn’t matter…
You see several components of one Heltun thermostat (like the temperature of 12,8 C, the heating mode and heating mode temperature. I have it squared in red.
What I found out is the following. When setting the heating mode (rectangle at the right), like the following:
it changes the status in the Lovelace. However when setting the temperature to 18 C (rectangle on left side), it doesn’t change the set temperature in the Lovelace (it stays 15).
I must conclude the integration is causing the issue…
This is mainly because of Fibaro I guess.
It seems that the entity_id climate.schlafen_rechts_heating_mode_com_600 isn’t representing the rectangle on the left, but the rectangle on the right only. So, the current+set temperature aren’t attached to the Lovelace widget at all.
But the funny thing is, the right rectangle should have the entity_id name something like climate.schlafen_rechts_thermostat_mode_606 (according to Fibaro) and this entity_id cannot be found at all in my configuration (but although it influences the climate.schlafen_rechts_heating_mode_com_600 somehow)… hmmm
I first need to find out why the individual Heltun items aren’t integrated automatically into HA.
The fact I have to cope with, is that one Heltun thermostat with several functions are split into Fibaro as separate items like brightness, humidity, temperature, thermostat mode and set temperature. I have got even more functions, but which I hide in Fibaro and luckily didn’t integrate into HA. An example is “Dry Air”, which I can set separately the temperature. So different from the “Heating Mode COM” (from common).
I have further researched my issue.
Your automation works for me now (partially), however I still don’t have it working completely. Basically, it’s an issue between Fibaro and HA integration. I’m quite sure and I have documented this issue here:
Let’s wait for any reply. If nobody can help, I think I need to report at Github. Do you agree after reading the new thread?
Hi,
I am a new user and trying to connect my danfoss devices to HA. I have a thermostat (014g0013) and a temperature sensor (Danfoss Icon 088U1081) . I installed Z-Wave stick and used Z-Wave-JS and Z-Wave to MQTT. I can connect to these devices, but they are not recognized. My HA does not read anything from these devices. Can you help me ?
I have:
Z-Wave JS to MQTT Current version: 0.37.0,
HA 2022.3.7
Is it possible to integrate with danfoss in this version? If so, what do I have to do step by step?