The binding uses the value returned by the device to set the min/max values. Maybe something changed in your configuration and this got screwed up - you could try changing it in the XML file for the device, which should be what the binding uses to set the value (make sure the binding isn’t running before changing the XML though).
Ah, yes, now I see it in the node.xml file. I should’ve thought to look there. Maybe I should leave it alone if the device thinks that’s the max.
I also saw some other weirdness with the polling interval. After an openHAB restart, all my devices initialized to poll every 1800 seconds (which I believe is the default). When I looked in the UI, it showed the polling interval was 86400. But when I looked in the jsondb, there wasn’t a “binding_pollperiod” config parameter. So I tweaked all the devices (incremented by 1 to 86401 seconds) and there’s now an entry in the jsondb for all the devices, and after a restart they now are initializing with the expected polling interval.
I wonder if this is a side-effect of the recent changes to config validation? Otherwise, I have no plausible explanation for the behavior.
I had it set to whatever the default is when you accept the thing from the inbox. I assume that’s 86400, but I don’t recall for sure. I’m not really sure how long the parameter has been missing from the jsondb. I only noticed it today when I was looking at the logs and saw all the polling activity.
I’ll be adding some more nodes to this network, but it won’t be for at least a few more weeks (it’s at another house). Now that I know what to look for, I can check whether the poll period is being set when a new node is added.
Yeah, I’m not sure either. But it’s definitely confusing. After adding the thing from the inbox, when you look at it in the UI it shows a polling period of 86400. But since there’s no parameter in the jsondb, the binding defaults to 1800.
The same might be true for the command repoll period, but I haven’t looked at what the UI shows versus what the binding defaults to.
Yes, but it doesn’t systematically go through and set all configuration. It sets a few things like the node ID - everything else is just in the config description, and unless it’s written to jsondb, it won’t be there.