Michael Bisbjerg
Michael Bisbjerg
If I recall correctly, `last_measurement` is the actual timestamp from the measurement, be it a device/sigfox or a device/bluetooth measurement.. So to ensure you react when you have data, I...
If you enable debug logging we could see what the actual values are. If it's pushing the _same_ value twice, it's a bug that I need to fix.
Checking twice within 10 minutes is unfortunate, but the issue I might see is if I publish the same _actual value_ twice. I'm thinking that you should only see the...
Ah, but `last_contact` should f.ex. only trigger, if the value is updated (by HASS). And HASS doesn't update the value, unless it receives something from MQTT - HASS doesn't care...
Could you be in a location with bad sigfox reception? If that's the case, it could be that your BR device is missing its own checkins, meaning this updater will...
There's no way on the HASSIO container unfortunately.. :/
There is a risk that some of the logic conflicts. F.ex. I do a lot of comparisons to ensure I don't resend identical values (what this setting negates). I can...
Ah, I see. Nice to know also, that their serverside thingy is likely javascript :P When that exception occurs, the entire update loop will be disrupted (and run again later)....
I've made some code that splits out the weather updates from the regular pool updates. Turns out this is a seperate API call for BR, so it can fail independently...
I find it very odd that the description of placement of the guids should have an effect. I've tried out the following: * Create a structure with data (the ids...