This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official
Comments
I was wondering if this App would also work with the Devolo Home Control Radiatorthermostaat (http://www.devolo.nl/producten/devolo-home-control-radiatorthermostaat/) or the Popp TRV (http://www.popp.eu/thermostat/). Both are essentially the same as the Danfoss.
The interesting thing about these devices is that they have a patched firmware which allows them to send back the ACTUAL temperature. Something the Danfoss can not do.
Can anyone confirm these devices will work also with the Danfoss App?
they are a different brands
devolo has multiple devices, so an own brand thing. and their own app already in app store (even though not the thermostatic is implemented)
popp (device of this brand already in app store) is a daughter company of Düwi (someone working on app for this brand), also a company that makes different devices..
don't try to make it more complicated for people by adding different brands into 1 app just because they look-a-like
This helps me in understanding how Apps / Devices work and why a Devolo wouldn't work in a Danfoss App. Through http://products.z-wavealliance.org/ I found out that the PID's indeed are different. What it does mean however, is that it would probably be relatively simple to port your Danfoss code over to the Devolo App.
My reason to prefer the Devolo is that it sends back the actual temperature, a command class (right?) that the Danfoss does not support. So event though the App would not support it from the start, at least the Devolo has more options for future use.
Perhaps I can find the time and help integrating both, all though a lot of this is totally new to me. Any pointers (on how to actually test communication with a device, a lot of sample code I can find on github myself) would be appreciated.
Cannot GET /app/com.danfoss/drivers/LC13/assets/learnmode.svg
Is the app broken?
I'm very new here, but probably the app store has it's own copy of the github code which is missing the svg file. Maybe an earlier version?
You could try to clone the repo (git clone https://github.com/athombv/com.danfoss) and upload the App manually with the CLI (athom project --run or --install).
I just forked the original Danfoss App in order to integrate it with the Devolo App, so that it supports the Devolo Home Control Radiator Thermostat. When testing that, I didn't get the errormessage.
there is only the icon in the asset folder of the LC13 driver
Ah... found it. I cloned the repo at https://github.com/kasteleman/com.danfoss instead of https://github.com/kasteleman/com.danfoss
The former one does have the learnmode.svg... Is this something for Athom to solve?
that moment he uses 2 of the same links to compare
but yes, @kasteleman ;made the initial try, @RobinBolscher ;finished it, but forgot the learnmode.svg (hé he's still human.!?)
Did you solve the E5 error? I just encoutered the same problem. Will try a shorter wake up intervall now...
It's just a workaround but the error is still present if you try to adjust manually.
The error means that the thermostat can not connect to Homey. But obviously Homey can send data to the thermostat... It seems to be like a one way street.
Github issue is created.
Because een week ago, when i was on firmware 0.8.39 with the "old" zwave classes, it worked fine with homey.
I did not want to go to 0.10 because at that time the danfoss app was not ready and it is cold outside... But this week the app was ready so i also upgraded homey, removed my old zwave devices and re-connect them with the danfoss app.
That all seems to work, it did see the device. But setting temperature thru the devices panel, does not seem to work. It does not "remembers" the temperature i just had set.
so i tried it with a flow. Same as before, but now i get a red warning sign without further information.
Maybe it is a range problem, but then again, why can it "see" the device when pairing. And why did it work without app on the old firmware.
It seems strange to me that some people with the same device can get it to work and some don't.
Almost same experience here...
@ version 0.10.7 using the most actual danfoss update of yesterday I still see E5 on all my devices. And since I'm still in testing phase, the units are not yet installed on the radiators I can see that not all my set point are proccessed on all devices. Note, to avoid zwave issue's the devices are less then 2 meters from Homey.
Any experience to share on troubleshooting and solving the issue?
the set temperature will only be applied to the danfoss when the thermostatic wakes up on it's own interval or if you wake it up manually, the new app sets that wakeup timer by default to every 5 minutes (if you included it in the latest version of the app)
So you need to wait a max of 5 minutes before the set temperature gets properly saved inside the thermostatic
this is something that is not changeable since all battery powered devices work this way
The manual states to the E5 error: "The thermostat is not receiving the expected replies from the control system. Check that you have a Z-wave certified controller running and it has the necessary functionality to control the thermostat (see “Technical requirements”)."
Therefore I think that the error is caused by Homey as it is the control system.
You can find the manual with the Technical requirements right here: http://www.benext.eu/static/manual/danfoss/livingconnect.pdf
waiting 5 minutes has nothing to do with the problem i mentioned. It gives an error sign, and temperature is not set!
also in the previous app it showed the temperature in homey direct after setting it, also when my danfoss did not recieve it yet.
That is the way you would want it to be, you want to be able to see to what you have set it.
it receives the "old" value from the valve itself the old version used it's own memory to show what value was set on the valve itself,
and why do you want to see within 5 minutes on what temperature you had put it on... are you that uncertain about your decisions?
i would it this way, then i am certain if the valve ever changed its value without having to look on the valve itself.
especially if you put the wake-up time higher... 5 minutes is way too pulling on the batteries. (high battery usage)
the error message (E5) is just strange since it receives it's values just fine, both ways
i dont have an E5 error on my valves, they work perfect manually. That was someone else.
About wanting to see what has been set. What If my wife is upstairs en checking on her app the temperature set. At my home the danfoss only refreshes once every 25 minutes. So there is a change see wil see nothing set.
I think It is stupid not to see what has been set, especially because it did work in the older version. And does your thermostat at home also forgets what you set it to? No, it shows both values. Homey could do the same, show in red the color set and in blue if the valve has got them
Ofcourse you may think otherwise, but showing it my way does not harm you.