Item State not Updating

Good test and good to know.

I assumed the default would depend on your system settings.

There should be no differences.

It might help to shunt the logging for the CalDav binding to it’s own file. See Log4j2 Sample Config for an example.

2019-02-27 21:00:00.052 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 72
2019-02-27 21:00:00.058 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 75
2019-02-27 23:30:00.023 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 67
2019-02-27 23:30:00.043 [vent.ItemStateChangedEvent] - SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin changed from 72.0 °F to 67.0 °F
2019-02-27 23:30:00.052 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 75
2019-02-28 00:00:00.073 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 67
2019-02-28 00:00:00.085 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 75
2019-02-28 02:39:59.280 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 67
2019-02-28 02:39:59.285 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 75
2019-02-28 03:00:00.059 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 67
2019-02-28 03:00:00.079 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 76
2019-02-28 06:45:00.013 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin' received command 72
2019-02-28 06:45:00.026 [ome.event.ItemCommandEvent] - Item 'SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMax' received command 76
2019-02-28 06:45:00.036 [vent.ItemStateChangedEvent] - SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureMin changed from 67.0 °F to 72.0 °F

2019-02-28 03:00:00.079
This event should have generated a changed from log message since the value was 75 (and it is… “stuck” at 75) and the change should have been to 76… but it didn’t do anything.

The two items I have set up in CalDav doesn’t generate that much log “traffic”. It was easy to capture all activity related to these two Items using grep.

OK, I bit the bullet and changed all instances of SPT_house_VT_hallway_wall_sensor_thermostat_TargetTemperatureM to sptHouse_VT_thermostat_TargetTemperatureM and both newly named Items appear to be updating as expected (at least at this point in time). I’ll watch the next couple schedule transitions to make sure both values are updating.

2019-02-28 14:00:18.440 [ome.event.ItemCommandEvent] - Item 'sptHouse_VT_thermostat_TargetTemperatureMin' received command 72
2019-02-28 14:00:18.444 [ome.event.ItemCommandEvent] - Item 'sptHouse_VT_thermostat_TargetTemperatureMax' received command 75
2019-02-28 14:00:18.454 [vent.ItemStateChangedEvent] - sptHouse_VT_thermostat_TargetTemperatureMin changed from NULL to 72.0 °F
2019-02-28 14:00:18.460 [vent.ItemStateChangedEvent] - sptHouse_VT_thermostat_TargetTemperatureMax changed from NULL to 75.0 °F

Perhaps it was an Item name length issue. I’m more inclined to think that it was simply creating a new Item that set this on its way. However, if this issue is related to the length of the Item name, then there is some underlying bug or undocumented name length limit in OH that ought to be logged as a potential issue to investigate.

I would say that this topic can be CLOSED… but it is not SOLVED.

Mike

I think you just had a “damaged” Item in some way - a possible fix would be to delete it from the internal JSON store and allow it to be recreated from file on reboot.

Yeah, that could explain it. Unfortunately, I’ve probably removed all traces of it now that I’ve renamed everything.

Actually I’ll bet it’s still there, and regressing to “original long names” will reappear the issue. You might not want that nausea :smiley: