Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Randomly stop broadcasting (vESPrino v1.16 build20170228)
I recently updated the firmware of the CO2 Monitor through USB and I started noticing that the device stops broadcasting information to my Domoticz app. I checked the device and It appears as if it was powered down.

Here is the log when the device boots up:

This is what it looks like in the domoticz app:
[Image: XYEUAwx0xx2Lh4-L3yFBjI6CtPmu9nsWIEGmO5fh...ize_mode=3]
i will check
there is some logic, where each time the device wakes up it tries to reuse it's last IP. And currently - if this fails - the device wouldn't seach for a new IP

i will prepare a fix in the evening for this
and let's hope this is indeed the root cause
can you try to upgrade again to the latest firmware

now it will take an ip on each iteration
I've updated the Firmware a minute ago and I am waiting to see what happens.
I've set-up my router to distribute a fixed IP-address to the MAC of the Vair Monitor so I don't quite understand how the described problem is occurring. I will report back in a few days if I have more information.
well i am also not quite sure
it may be that due to some missing fallback logic, if for some reason the device fails to connect, then i store the IP that i get and then just reuse it.. up to now i didn;t check this i think

but it may well be another problem
sadly it only happens randomly in some people's setups
It is still happening, so the issue is not resolved.
in this case, can you enable debug mode, the device will start to blink, depending on whether it succeeds to send or connect to WiFi, and this way - once it stops (if it stops in debug mode) you can tell me how it blinks
and in fact - you didn;t have this issue before, right ?
I rebooted in in Debug mode and it booted up flashing green twice and then back to blue or purple (sorry colorblind).
Anyhow, here is the output of the monitor:

It didn't happen before I updated the firmware.
I guess I had an older version from before you could manually input the ip address in the config tool.
( Back then I had other issues but the devices kept running.
FYI, the RF module is still disconnected so I just have the board with the esp8266 and the CO2 sensor.

** There seem to be no set interval as to when the device stops broadcasting.
(can be 2 hours or 20 hours)
i just created a post describing the different ways to debug it. I always wanted to do it but for some reason i didn't manage

There are also several other approaches to debugging

Now that you've enabled debug. Just let the device run, as it usually does. You do not need to keep it connected via USB.
Have a look on the post above, and tell me whether you are able to recognize the colors as described.
If not - tell me which are the ones that you can recognize, and i will add other blinking colors, so that people can choose. The current version is just the first shot.

It would be a great help for me, if in this mode the device stops sending data. As the problem may be that for some reason the I2C Bus failing and in this case the device will not send data. This can be also checked if you add some HTTP Destination for logging, (see the post) or adding an additional line in the Custom HTTP Config

(and appropriate idx), which will dump how long the device worked.. and will be sent even if the CO2 value is unavailable

Forum Jump:

Users browsing this thread: 1 Guest(s)