01-13-2017, 03:06 PM
aahhh, now i saw it.. in fact it is a bug that a fellow already reported, but i was fixing other stuff and still havent got to it.
basically after the firmware replaces the mqtt value string %CO2% with the actual value
then another part checks if there are unreplaced stuff.. but it searches for CO2 and not for %CO2%
so if you have CO2 in the topic value (e.g. your topic) then this check fails.
i will fix it in the current firmware, but i need a couple days more to finalize testing.
maybe you got the last automatic update that caused this troubles
it is also interesting why your other is still working... in general firmware update happens after restart, so if for some reason one of the sensors rebooted - it got the firmware update, which is 20161217
and if you updated then using OTAH, this is how you got the latest.. but both of them have this bug
basically after the firmware replaces the mqtt value string %CO2% with the actual value
then another part checks if there are unreplaced stuff.. but it searches for CO2 and not for %CO2%
so if you have CO2 in the topic value (e.g. your topic) then this check fails.
i will fix it in the current firmware, but i need a couple days more to finalize testing.
maybe you got the last automatic update that caused this troubles
it is also interesting why your other is still working... in general firmware update happens after restart, so if for some reason one of the sensors rebooted - it got the firmware update, which is 20161217
and if you updated then using OTAH, this is how you got the latest.. but both of them have this bug