It seems as if the Thermostat timer has stopped. To debug these cases it is good to see the CLI logs to see if the thermostat timer is running.
I know you are interested in knowing how it works. The driver has two timers:
Thermostat timer with mode other than Off: It runs every 20 sec. It checks the temperature and compares them to shoot actions.
Temperature timer with mode equal to Off: It is executed every 300 sec to synchronize the sensor temperature with the thermostat temperature.
A 300 sec timer that interrogates the temperature of the sensor when the thermostat timer is running.
These timers stop automatically when there is a reboot of the hub or a driver update, for example I do an inclusion of fingerprints or some modification.
When the driver is restarted, the timers that were running are reinitialized. I haven’t tried it on this particular driver because I don’t have any device, but having reviewed the code it seems to me that it should work fine.
If you put the logcat and in preferences you have disabled the debug mode, (by default it is disabled), in the end you will see this in the logs, if thethermostat mode is different of Off:
2022-12-09T15:25:03.367660751+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc <<< Cheking Temp >>>
2022-12-09T15:25:03.368645085+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc device: <ZigbeeDevice: 16fa2ff4-00ca-4b65-b1db-5af142511d65 [0x9CFB] (Termostato)>
2022-12-09T15:25:03.370003085+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostatOperatingState **** pending heat ****
2022-12-09T15:25:03.371205751+00:00 DEBUG Zigbee Temp Sensor with Thermostat Mc Termostato device thread event handled
2022-12-09T15:25:23.288151087+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc <<< Cheking Temp >>>
2022-12-09T15:25:23.305286754+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc device: <ZigbeeDevice: 16fa2ff4-00ca-4b65-b1db-5af142511d65 [0x9CFB] (Termostato)>
2022-12-09T15:25:23.308449420+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostatOperatingState **** pending heat ****
2022-12-09T15:25:23.354554754+00:00 DEBUG Zigbee Temp Sensor with Thermostat Mc Termostato device thread event handled
2022-12-09T15:25:32.663699421+00:00 DEBUG Zigbee Temp Sensor with Thermostat Mc driver device thread event handled
2022-12-09T15:25:43.283313423+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc <<< Cheking Temp >>>
2022-12-09T15:25:43.325282756+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc device: <ZigbeeDevice: 16fa2ff4-00ca-4b65-b1db-5af142511d65 [0x9CFB] (Termostato)>
2022-12-09T15:25:43.338695756+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostatOperatingState **** pending heat ****
If you have debug mode activated, you will see more data from the thermostat control points:
2022-12-09T16:05:33.287332867+00:00 DEBUG Zigbee Temp Sensor with Thermostat Mc driver device thread event handled
2022-12-09T16:05:44.150995872+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc <<< Cheking Temp >>>
2022-12-09T16:05:44.151996539+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc device: <ZigbeeDevice: 16fa2ff4-00ca-4b65-b1db-5af142511d65 [0x9CFB] (Termostato)>
2022-12-09T16:05:44.161378872+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostat_Run = running
2022-12-09T16:05:44.163582872+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostatOperatingState Before = idle
2022-12-09T16:05:44.165702539+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostat_Mode = rush hour
2022-12-09T16:05:44.167789206+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostatFan_Mode = auto
2022-12-09T16:05:44.169898872+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc cycleCurrent = stop
2022-12-09T16:05:44.172158206+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc device.preferences.floorRadaint = No
2022-12-09T16:05:44.174450872+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc device.preferences.temperature DiffStarStop = 0.6
2022-12-09T16:05:44.182486206+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc *** Current_temp *** 19.73 Celsius
2022-12-09T16:05:44.185301539+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc ## heating_Setpoint ## 20.0
2022-12-09T16:05:44.187410539+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc tempChangeToHeating <= 19.4
2022-12-09T16:05:44.189497872+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc tempChangeToPendingHeat > 19.7
2022-12-09T16:05:44.191898206+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc ## cooling_Setpoint ## 24.0
2022-12-09T16:05:44.194148206+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc tempChangeToCooling >= 24.6
2022-12-09T16:05:44.196270206+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc tempChangeToPendingCool < 24.3
2022-12-09T16:05:44.198386872+00:00 PRINT Zigbee Temp Sensor with Thermostat Mc thermostatOperatingState **** pending heat
I am looking more closely at the capture and the text and I think that what you are saying does not correspond to the chronology of the events:
You say that you have changed the heating set point from 23.5 to 22.5 and that was at 5:46 p.m. The value shown in infoPanel is before 5:42 p.m., when the heating set point was 23.5 (23.5 - 0.25 = 23.25 temperature to change state)
The new temperature value 22.7 arrives at 5:48 p.m. approximately, let’s not know the seconds and the mobile clock indicates 5.50 p.m.
The state change should occur in the next minute or so, depending on the history lag, which can be variable.
What actually happened in the details view in the 5 minutes after?
Could You retrieve and capture history from yesterday after 5:48 p.m. let’s see what happened next?
This is what I was wondering. With what you said before about timers, maybe I’m incorrectly expecting changes to the Info Panel to happen immediately.
Unfortunately, at 5:51an automation based on a motion sensor actvity changes the Thermostat Mode to off.
Perhaps I should be more patient. However, a 5 minute lag after changing a thermostat setpoint for the thermostat to take action seems excessive to me.
I’m trying to use an Aqara temp sensor as a thermostat to control a socket - how do I install the above to do this? (could try Samsung multi sensor too)?
Thanks for the help thou I’m very confused.
I’ve got driver installed and available in the hub setting in the app
I’ve reinstalled the multi sensor and it shows as a placeholder in the IDE and works in the app, try to select different drive in the app and shows “no results found”.
Where do I change the settings above?
When do you change it in preferences?
What do you mean exactly?
Do you not notice a change in the sensitivity of the device?
or when you read parameter 4 it still shows a value = 5?
If you can capture a log of when you change the preference from max to med I could see what is being sent and received.
Hello everybody.
I am very new to everything related to Smartthings, and I came accross this conversation while trying to do the exact same thing that is described in here. However, I am having some trouble trying to find information on how I could exactly make use of this edge driver.
I am trying to control a switch that turns on and off my boiler with an external SwitchBot temperature sensor. I see this works for Z-Wave devices, but I was wondering if it would be possible to make it work with mine.
Also, I would like to ask if anybody has a guide on how to install and make use of an edge driver like this one, as I am getting a bit lost with everything.
Please let me know as well if I am not using the proper forum for this!
Thank you very much.