I am currently updating my setup to use item metadata instead of labels for the Homekit integration.
At one point, I see some behaviour which seems erratic to me.
I have set up a Thermostat accessory (group + all the individual characteristics), which works as it should.
I have set
maximumTemperature in the
I also see these being set to 0 respectively 30 when going through PaperUI / Homekit Integration / Configure / Expert mode.
For testing purposes, I have bound a Number item with no channel behind it to one
When I change the value of that item, no matter to how low or high I set it, I never get a message in the log, that the value may be above or below the defined min/max.
But: when I restart the homekit bundle (through OH console) or if OH restarts, I get errors, depending on what the value was set to, prior to the restart. I get an error “over max”, when the item is set to >38.0:
2020-05-20 10:32:25.488 [WARN ] [istics.impl.base.FloatCharacteristic] - Detected value out of range 38.1. Returning max value instead. Characteristic io.github.hapjava.characteristics.impl.thermostat.TargetTemperatureCharacteristic@4350a17a
I get an error “below min”, when the item is set to <10.0:
2020-05-20 10:35:22.947 [WARN ] [istics.impl.base.FloatCharacteristic] - Detected value out of range 9.9. Returning min value instead. Characteristic io.github.hapjava.characteristics.impl.thermostat.TargetTemperatureCharacteristic@15c85b6e
When I crank up the
maximumTermperature in PaperUI, this has no effect on the max-bound that is checked - it’s still 38.
- is this the expected behaviour, that min/max bounds are checked when Homekit starts (reloads), but not when the item to which the value is bound changes?
- how come, that in my setup min/max which are used for checking seem to be 10/38, instead of the configured 0/30?