Very strange, there should be lots of stuff appearing in the log.
My guess is that the Connect has not associated itself with the Hub correctly. Might be worth trying to remove it and re-join it again.
Yea, itâs very strange!
Just tried to remove it from ST and pulled out the batteries from the Connect, before connecting it again to the hub by searching for the Connect via the SmartThings app.
The hub finds the Connect, but it seems like they stop communicating afterwards. Could it be that the firmware on my Connect is newer than yours?
I noticed from your earlier screenshots that your device has a different raw description. I think that comes from the Connect device, if anyone can confirm that Iâve got that correct?
Yours:
Mine:
And that you have an older model? or maybe I have 
That could be an issue. I think mine is a new version - correct me if Iâm wrong 
Hereâs a picture of the thermostat:
Anyone with the same model as me?
Just for the benefit of others who got into the E5 issues even after the DH was confirmed working perfectlyâŚ
I bought a whole lot of Devolo TRV but kept getting the error on the few installed since beginning of the year (so since AprilâŚ) - ignored it as the central heating itself is still controllable on the boiler. Finally got the rest of the radiators changed and for the last couple of weeks been struggling to find a solution. After ploughing through post after post and came across a snippet of someone elseâs IDE screen and realised there is a Danfoss TRV LC-13 Device Type that I wasnât usingâŚproper rookie errorâŚhours and hours I could never get backâŚ
I normally quite good with instructions but somehow I missed that small details and probably installed something else that triggered the auto selection of âZWave TRV deviceâ or something that wouldnât set the setpoint or receive commands properly and led to disconnection to the hub.
Lesson learned!!
Thanks for Tommy for the DH.
Anyone with the same model as me? Iâm thinking about returning it now and track down another version
So far, thanks for all the help
I have this version, it seems to work ok with the smartthings dh but not the custom dh as discussed in not to many posts above
I might have found the reason why my Connect doesnât work
Apparently, mine (4.02) does not support z-wave protocol, but my hub is able to discover it?
Is there any chance to adapt this handler to Eurotronic Spirit Z-Wave TRV? I asume they work pretty much the same way.
2 Likes
In theory it should be possible but in practice youâd need one of physical devices to figure it out and troubleshoot the differences.
Iâve got one actually, but I donât really understand where shall I start. Before migrating to ST I was using RaZberry Z-Way, and had no problems with this TRV. In ST it is recognised as Z-Wave Dimmer. When I press buttons on TRV, it sends some commands to ST, I can see them in logs, but what I have to do with this information - no idea.
It sounds like youâll need to do a bit of coding, to get this to work. The first steps are understanding the events and also the z-wave commands you can send to the thermostat. This helps with that https://graph.api.smartthings.com/ide/doc/zwave-utils.html
The danfoss device handler here and other handlers, are not a bad place to copy from but the danfoss handler is largely built around it being a sleepy device (only wakes up every x minutes and checks in for commands to receive) and some of itâs quirks.
1 Like
Received the Devolo version of this thermostat yesterday. Appears to be the same except that it can report room temperature back to smartthings.
Initial install defaulted to âz-wave thermostatâ This doesnât work well (at all) in terms of control but was reporting back the temperature from the room.
I tried the standard LC-13 DH and this custom one and like the custom one better but would be nice to be able to report back temp so I can then use the 5-2 scheduler without a separate temp sensor, sounds like itâd be a cut and past of code from the âz-wave thermostatâ to a custom DH but Iâm new to this stuffâŚ
Also canât seem to get the polling to update, itâs stuck on 30 minutes.
I donât have any specific tips on how to exactly do it, as I donât have a Devolo. But if the Develo is the same as the danfoss one minus the temperature reporting. Youâre best approach might be to start with the custom handler. From there you can start to do something with the temperature it reports back.
Hi all,
Has anyone had any luck with integrating the Danfoss room thermostat (DRS21)? It reports in when using the handler for the TRV, but obviously doesnât report the temperature.
When using a generic thermostat handler, the temperature is reported⌠however the device becomes âunavailableâ after a few hours and does not report in until the device is manually awoken.
Iâm hoping to use it to control the heating set point of multiple TRVs in one room, and report temperature of the room as well.
I am getting an error when I try to install @tommysqueakâs device handler from his Github repository.
I can see âdevicetypes/tommysqueak/danfoss-living-connect-radiator-thermostat.src/danfoss-living-connect-radiator-thermostat.groovyâ in the New â(only in Github)â window when I click on âUpdate from Repoâ but I get a generic âUpdated 0 devices and created 0 new devices, 0 published (1 skipped due to errors)â when I âExecute Updateâ.
The DTH handler installs OK if I copy and paste and I can update other repoâs OK. Any ideas?
@yvesracine does you app allow different schedules based on mode? I.e. If mode is Mode-1 use schedule A, if mode is Mode-2 use schedule B, if mode is Mode-2 use schedule C. Also, does it integrate with Nest to turn the boiler on if a temperature sensor calls for heat?
Hi,
-
By mode, I guess you mean âST location modeâ like Home,Away, Night⌠Yes, the schedulesâ start & end time can be associated to one or many location modes (optional) in ScheduleTstatZones.
-
In the âScheduleTstatZonesâ smartapp, for each room, you can associate a room sensor. The scheduled zones will then use all room sensors (not only one) and adjust the thermostatâs setpoints according to the avg calculation (by default). You may also use other calculation methods like median, min, max, heat/min; cool/max⌠The setpoint adjustment does not automatically mean that the smartapp will call for heat, but if your far away rooms are colder than the ambient temperature at the thermostat, then, there is a good chance for the heat call.
-
For the Nest, in order to leverage all smartappâs powerful logic (there is a tight integration with my Nest integration in order to detect manual overrides), youâd need to contribute to My NextTstat DTH which is also available at my store. In fact, you should take advantage of MyNextBundle at my store if youâre planning to use âScheduleTstatZonesâ.
For the full list of supported features and use cases, refer to the ST community wiki:
http://thingsthataresmart.wiki/index.php?title=ScheduleTstatZones
For MyNextTstat, refer to
http://thingsthataresmart.wiki/index.php?title=My_Next_Tstat
Or the following thread:
Regards.
Thanks for the quick and comprehensive response 
Hi Tommy,
I have installed my Danfoss LC13âs and updated to your device handler but the Wake up reporting that is typically seen every 5 mins has now stopped.
This worked on the original Default Handler via Smartthings.
Can a confirm that the device is waking up every 5 minutes but just not logging a wake up?
Also, does the LC13 not give read ambient temperture. They do not appear on the list of Temp Sensors for ScheduleTstatZones
Thanks