Hello, I have a Stelpro SMT402 Thermostat. It is connected to an Aeotec hub v3. After the last update to the Zigbee Thermostat Driver Version 2023-06-13T18:57:32.680371772 and Controller Version 2.3.22-2 the thermostat stays on Heating even though the set point heat temperature is 41 degrees and the room temperature is 78.8 degrees.
As you can imagine in the hot summer, this is a significant and urgent problem to resolve! Can anyone please help/suggest? I’ve followed ST’s suggestion to uninstall the app and reinstall – no luck!
Welcome to the SmartThings Community, @stscot!
I see in the ticket you opened with Customer Support that you provided some info for them to report it. That should help to continue with the investigation of why it is happening.
I would suggest that you also provide support access so that when they escalate the issue, the team can see your device’s config:
- If your SmartThings account email is not the same as here and the ticket, provide the email in that ticket.
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (⋮) and choose Settings
- Toggle on Account Data Access
- Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
If the value of the thermostat state isn’t changing, we should check if once you change the temperature, the device also sends the event of thermostat changing from heating to cooling for example. That should be seen in the driver logs which can be enabled by:
- Setting up the SmartThings CLI (here are the instructions) and running the command below:
The IP address of the Hub can be found in the IDE or in the CLI by getting the details of the Hub.
To get the Hub device ID, you can make this request first:
smartthings devices --type=HUB
This command will provide some details of the Hub and you’ll find a property called “localIP”:
smartthings devices HubDeviceId -y
Thanks for the reply. Unfortunately I’m not on-premise (local) at the moment so I’m not able to run the logcat command.