Can someone pls guide me why my danfoss lc13 which was only connected via smarthings to my app do not show temerature control? It was all working fine until today but its just showing battery not the temeratire seems
Same her. All four danfoss controll options are gone from the new app.
Here too! I’m using default dth for lc13. Also google assistant can’t still control lc13 (been that way from begining). Maybe dth needs to be updated with some capabilities?
You aren’t the only one, there was an ST update over the weekend which has caused heating setpoint controls to disappear for all devices using it. Stelpro Maestro SMT402 unable to adjust temperature in SmartThings after Controller v. 2.1.19-7
Report it to email@example.com and indicate your urgency so they can prioritize it accordingly.
I have the same problem with my Popp Z-Wave Thermostats. I’m not sure if it is since when I included the thermostats, but they are using currently the generic Z-Wave Radiator Valve Thermostat DTH. I will send a mail to the support as well
Update: By the way, I can control the thermostat temperatures with automations. As workaround it should be able to set a specific temperature when clicking a virtual button or something like that. Just a quick thought
What the flying F?
I’ve just had a look on my TRVs. It is indeed gone.
@blake.arnold, are these the steps what should make this platform better? If you wouldn’t have killed the Classic app, then I could go back there and change the values from there, but now I have no idea what temperature setpoint my TRVs stuck on and for how long. And was any of my automations changing them…
@steven.green, do you know what is actually happening with the heating setpoint control? It seems to be you were working on the thermostat DHs recently and must be something was going on with the UX as well.
Are you sure that your automations doesn’t change the temperature setpoint? For me my automations and webcore pistons still are changing the setpoints correctly. Only the manually control of the setpoint isn’t working for me.
On the screenshot you can see that the setpoint (in German Heiztemperatur) has been successfully changed yesterday evening and today because of my automations (heating before going to bed) and webcore pistons (setpoint to 10 degrees Celsius if window has been opened)
You must be right. I must have looked on a TRV which hasn’t been added to any Automation.
But that doesn’t change the fact that a basic feature has been removed for some unknown reason and you have to do kirks to be able control a thermostat.
My TRVs hasn’t got any display to read the setpoint off. And basically no way to tell is it open or closed neither, just by touching the radiator or forcing it to close.
sigh I have a suspicion about what happened. I’m checking to see if support has escalated anything to the internal ticketing system, and to see if I can track down the right individuals to fix this.
I just wanted to leave a note that there is a high priority ticket to track the progress of this. There are no updates right now.
Just guessing, but it feels like the Capability Presentation has been messed up, and it is missing the Heating Setpoint from there. But I can never know what has been done in the background with the UX plug-in for that capability. As it was noted before, the Automation part seems to be actually working, so that must be still there.
Thanks for looking at it!
Unbelievable. If I would maintain/release software like this I would be sacked.
Thanks for the info! Look forward to getting the correction.
I have the same issue on my Popp TRV. I have noticed I can still control it by the old Smartthings app, bit it has disappeared from the new app. I can also control it by a task as a workaround.