Yeah, saw that too. If the current states are right, which it looks like they are except battery, but the mobile app is showing doubles like that; then I have no idea what in the world is going on. I’ve seen a lot of funky stuff with the new app, but that’s a first. Congrats?! LOL, just kidding.
Aside from having you remove the device and readd it, you might want to email support with what you’re seeing because it’s definitely not right, and it may just be a sync or back end issue they can resolve.
Calling smartthings support didn’t seem to help. I’ve tried removing the thermostat and adding it again. Now its showing the the current temperature as 0 and the heating and cooling set temperatures as 40 and 40 in the new app.
I’m still using this DTH and it works perfectly with the new app.
Basically the steps boil down to:
Get yourself set up in the IDE if you haven’t done that yet (https://account.smartthings.com/). Use your the same account you use to log in to the mobile app.
Create a custom DTH using the code above. Make sure to Save and then click on the “Publish” -> “For Me” button
If you haven’t joined the thermostat, go ahead and do it and it should find and use your custom code.
If you already joined the thermo, or if it did not use your DTH when it joined, edit the device (in the IDE) and change the Type field to use your code.
If the mobile app doesn’t update, then you may need to clear your cache, or sometimes just rename the device in the IDE and name it back again.
That’s probably because ST hasn’t received a status update for that capability from the device yet. You can remove the thermo cover and put it back on to trigger a battery and power source report. That’s what I’ve done to get that state to update, or you can wait for the device to send ST a value.
I’m definitely not seeing that happen in the mobile app, but what’s really really weird that I’ve never seen before is the IDE having duplicates, and not the mobile app, check this out:
I can tell you for certain that something changed on ST’s end to have the IDE look like that for this device.
@jody.albritton, what would have caused a situation like that to happen? I’ve never seen anything like this before. It’s only happening on my 2 thermostats so far, but I’ll look through my other devices today to see if this behavior is happening elsewhere.
Looks like something may have changed under the hood with the recent update. Had no problems using this DTH with the new app for many months, but when I had to re-link my voice assistant yesterday, things went weird.
Just like you I’m also seeing the duplicates in the app and on the website’s IDE. Also the app keeps wanting to display the current temperature in Celsius even though the thermostat and website report correctly in Fahrenheit (changing it on the app doesn’t seem to save).
I tested using the generic ZigBee thermostat profile and the app duplicates went away (but not the website) but the weird Celsius/Fahrenheit bug still remained.
I’ll keep poking around too and see if I can find out what may be causing this too…
Duplication of settings fields with DTH “My Centralite Thermostat”
Degree C in current Temp field and Degree F in Set Temp Fields with DTH “My Centralite Thermostat”
The following has not been reported in my reading:
Current Temp field populated with Low Set Point value in both detail screen and tile.
As other have observed:
While on batteries, reported as “AC Power Supply”.
Here is a new observation.
When DTH is set to “ZigBee Thermostat” #1, 2 and 3 are correct albit Power Source and battery level are always reported incorrectly.
However if I switch DTH to “My Centralite Thermostat” and back to “ZigBee Thermostat” #1, 2 and 3 may or may not be in the error state.
I can’t say when this fell apart given my migration of three locations to the new app and each location having a Centralite Pearl thermostat.
One of the three locations is otherwise offline unless the DTH has recently been changed and it will go back offline within minutes and then remain in that state.
Very Frustrating.
Any help is appreciated.
Went back and set he device handler to the published generic Zigbee Thermostat profile and it seems to be behaving better. With the exception of the battery level the other functions on the app are back to normal (no duplicates, correct operating state, F/C units, etc). Google assistant is also able to control the thermostat again.
Interestingly on the website it still shows duplicate fields but that doesn’t appear to be carrying over to the app. I’ll see what is different in that code VS the one listed on this post which worked before the update.
I’m new to SmartThings. Just installed Pearl and paired with SmartThings Hub. Now, I can’t seem to find a way to program the schedule in the SmartThings mobile app. This is the same whether I use the default device handler, or the one posted here by OP.
Perhaps I need to install a third party SmartApp like:
By default there is nothing when I try to add from the mobile app. I had to paste the above source code in the ST cloud. Am I missing anything?
Most device handlers do not have scheduling built in, as you’ve discovered. A SmartApp like @rboy’s is what you need if you do not want to build Automations in the ST mobile app.
@johnconstantelo
I used this updated code/handler from the built-in handler and now both of my thermostats work great with the new Smartthings/Alexa integration. Thank you very much. I’ve had no issues with C vs F or any of the other issues described in this thread. Thanks Agin!
Hi @johnconstantelo & @jwilkinson74,
Can you point me to the file with the latest DTH for Centralite Pearl Thermometer? I clicked on the link further back in this thread, but that one shows last updated on 03-01-2020. Given that this thread is more recent, is there a newer version of the DTH somewhere? For reference, here’s the link I was looking at. If that is, indeed, the latest, let me know!
Thank you @johnconstantelo,
I installed your DTH to fix several problems with the stock Centralite Thermostat DTH:
Duplicate Temperature Setting Controls
Duplicate Operating Mode Setting Controls
Duplicate Fan Mode Setting Controls
Operating State always shows “Heating” even when idle
Your DTH fixed the first one, but not the other three. I still had two operating mode and two fan mode controls in the app, and operating state was still showing “Heating” all the time.
I then changed to the generic “Zigbee Thermostat” DTH and everything is fixed and working properly. However, now the thermostat is showing on AC power with 0% battery even though it’s not on AC power and the batteries are new.
Has anyone else experienced this? My thermostats are only controlling a hot water heating system with no cooling and no fan, so I just have two wires connected (Rh and W1).
That’s the one I use and other than a duplicate of some items, this works great for me. The thermostat hasn’t changed and along this still works, it’s my understanding that there no need for a newer version. Have you tried this one yet?
I have 2 of these thermostats, one has duplicates and the other is fine. In the IDE, both show duplicate states. Who knows when that happened, but it was never like that and I’ve had these devices for a couple or 3 years, at a minimum.
I have time this weekend to delete and readd one of them to see if it resolves the duplicates.
