Linux openHABianPi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l Release = Raspbian GNU/Linux 9 (stretch) Kernel = Linux 4.14.98-v7+ Platform = Raspberry Pi 3 Model B Rev 1.2 openjdk version "1.8.0_152" OpenJDK Runtime Environment (Zulu Embedded 220.127.116.11-linux-aarch32hf) (build 1.8.0_152-b76) OpenJDK Client VM (Zulu Embedded 18.104.22.168-linux-aarch32hf) (build 25.152-b76, mixed mode, Evaluation) openHAB 2.4.0-1 (Release Build)
// Thermostat Scheduled stored in openHAB Google Calendar - CalDav Number:Temperature SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin "Target Temperature Min [%.1f %unit%]" Number:Temperature SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax "Target Temperature Max [%.1f %unit%]"
These Items are set via the CalDav binding (see below as to why I do not believe the problem is with the binding) which retrieves the values from my Google Calendar with multiple changes throughout each day which recur day-to-day, week-to-week.
When I first set this up and got it configured properly, it worked as expected. However, in the last several days, one of the two Item states is no longer being updated. “Min” updates as expected. “Max” is “stuck” and does not update.
At first I thought it might be an issue with the CalDav binding. The log shows that the commands are being sent to the Items on my set schedule.
2019-02-27 06:45:00.009 ItemCommandEvent Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 72 2019-02-27 06:45:00.018 ItemCommandEvent Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 76 2019-02-27 09:40:18.754 ItemCommandEvent Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 72 2019-02-27 09:40:18.764 ItemCommandEvent Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 76
However, Max is not being updated to the values in my schedule.
I have stop/started, rebooted, cleared the cache & temp files, etc. None of these have had an effect.
I have been trying to troubleshoot this as a problem somewhere in CalDav or my configuration, or my Item and Sitemap declarations. Nothing appears to be wrong there.
Today I decided to use the REST UI to work my way upward toward the CalDav binding. I used the Item POST to send a value to the Item followed by an Item GET to look at the state.
These log entries are as the result of my interaction with the REST UI.
2019-02-27 09:41:56.366 ItemCommandEvent Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 78 2019-02-27 09:45:19.142 ItemCommandEvent Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 71
The images below show that the “Max” (name appears truncated due to length of Item name vs. the length of the text box) POST completed successfully (200), yet when I look at the Item state it does not match the value I just set. In fact, it is the value at which the Item has been stuck at since this problem started.
When I perform the same actions for the “Min” Item, it updates as it should. The images show that as well.
REST UI Actions for "Max"
REST UI Actions for "Min"
Any ideas where I can continue to explore to troubleshoot this issue?