Thanks for pointing this out. For some reason the default preferences don’t work in the new App. I’ll look at it.
I have posted an update, which deals with the issue reported by @DoubleDutch. I’m not sure whether this has fixed the issue reported by @cpetzny and @colcaff. I have changed the ‘vid’ to one which has less unnecessary tiles, but that change is not being reflected in what I can see on my mobile. I will try to find out why that is.
Not sure the defaults work as I’ve set my values now 
Having updated the device handler I still see the Cooling Temperature tile on the device which clearly is not applicable to the SRT323. Should have have dissapeared?
I’m aware of this issue and am trying to fix it. Are you getting the ‘fan mode’ tile, which also shouldn’t be there.
Can you try the following:
- in the IDE go to MY Devices and click on the Thermostat.
- At the bottom click Edit and then change the Type to (e.g.) Z-Wave radiator thermostat, then click Update.
- Go to the smartthings App and open the Thermostat page.
- Return to My Devices and change the Type back to my srt323-thermostat
- Retrn to the mobile app and open the thermostat again.
For some reason the ‘vid’, which controls the interface, doesn’t always change when the DH is updated. Changing the DH and then changing it back again appears to force the issue.
I now see a much simpler interface containing Temperature, Heating Temperature and Battery only.
That worked! Thank you!
@aonghusmor - Strike that. The interface is much simpler but the temp up/down doesn’t work anymore…
The log shows: 18:03:09: trace setHeatingSetpoint(17.5) set to 17 but it never changes up to 17.5 or beyond
OK! Back to the code. Looks like the interface goes up and down in 0.5 and the code in 1.
I’ve posted a temporary (but not very satisfactory) fix, which makes it go up and down in whole degrees, even if it says (e.g.) 17.5
Hi @DoubleDutch, @cpetzny,@colcaff and others.
The DH should now work properly in the new App.
In the course of trying to fix the problem that the temperature setting in the new Smartthings App wanted to go in steps of 0.5, I discovered that the firmware for the SRT323 device actually supports setting in steps of 0.1, even though only integers appear on the device’s screen. I suppose this is consistent with the fact that it can report the measured temperature also in steps of 0.1.
This means that the DH may show a temperature of (e.g.) 20.5C, when the hardware screen shows 21. I am observing the behaviour of the device under these circumstances to determine which is correct. At the moment I suspect the former.
Sometimes the vid (the interface in the new App) doesn’t renew properly, when the DH is updated. See message 65 in this thread for a solution, admittedly a clumsy one. This issue has been reported in other contexts. I hope Smartthings will provide a solution soon.
Thanks @aonghusmor - I updated the DH and it seems to work now. Thanks for your help!
That looks like it’s worked. Now showing correctly with just three tiles, Temperature, Heating temperature and Battery. I did have to do the workaround with changing the Type, but it’s working now. Also worth pointing out that having changed the Type, it took a while for the new app to update the tiles…
Thanks so much for making the update!!
Chris.
I posted another update to fix a potentially nasty bug, which had crept in as a side effect of yesterday’s changes. This should only affect people using the trick with T>100 .
I note that the temperature setpoint, the requested temperature, appears in the ‘recently’ list in the old app, but not in the ‘history’ in the new app. I’m trying to find out why that behaviour has changed.
It would be nice if the tile with the operating state, heating or idle, could be added. As a compromise, that information could appear in the ‘history’.
Hi
Please excuse me if this not the right place to post this question, but its one of the few active threads I can see for the Secure srt thermostats with smart things. I’ve a a few Srt321 which I’m having the same issue with… The all report back to smartthings when the setpoint is set on the device, however, when we set the setpoint on the app, it updates on smartthings but NEVER gets updated back to the thermostat device. I’ve been testing it with mdeaves DH and the one discussed on this thread for the SRT323 just to see if it would work. Ive also removed, factory defaulted and rejoined the device to the zwave network. If anyone has any theories, or can explain to approximalty where in DH code that the device should be retrieveing the setpoint from I’d appreciate it.
Thanks
Alan
Look for a line containing
zwave.thermostatSetpointV1.thermostatSetpointSet
thanks - I’ll take a closer look at it this evening and will pop in some debug lines to see if that function is been called.
I’ve just noticed that the temperature setting tile has disappeared since yesterday. I’ve made several attempts to fix it, without success. This looks like a change from Smartthings.
I just want to check whether you have been seeing the same phenomenon?
OK! I’ve sent a message to support. Let’s see if anything happens.
I suggested it might be an error and pointed out it doesn’t make sense for a thermostat not to have a mechanism to set the temperature.