I have a question about the battery values. I have a new WS-2000 and am using the local server now. It has the indoor sensor and 4 additional in/outdoor sensors. All new batteries.
When I enable child devices, they show up with "battery: 0". This is how all the additional sensors look:
As far as I can tell, Ambient's reporting only gives a 1 ('good') or 0 ('dead'?) for the battery value. I suspect that's the "batt: 1" in the state variable.
What's off is my indoor sensor shows no "batt" value:
On the station device itself, I see these. "battin" would in the indoor sensor, but it shows 0. I do not know what the batt_co2 is - I don't have any additional sensors.
Looking at the code, I see this comment in the batt processing:
// Normal sensors only report 0 = Good or 1 = Bad. I am putting 0 = 75% because they will never be full for long
I think that's backwards for the values: 0=bad and 1=good, at least for the data direct from the device (e.g., maybe it the other way for data from the API).
When I turned on full logging, I see this coming from my device, and it certainly has "battin: 1" in there.
So somehow the "battin: 1" is getting changed to "battin: 0" when going into the states. The other battN values are getting through. Ah, I see "battout: 0" also, so it's being treated like battin.
(and I do see it reporting batt_co2, but I don't know what that is!)
