11-16-2016, 04:01 PM
Set up the colour LEDs last night. Brightness level 93 seems to be a good compromise.
It only connects to the router for a second or so: I had a ping -a running which usually beeped once, sometimes twice, occasionally not at all. Just as an experiment I tried the command “prop_jset "event.wifiDisconnected"##ledbrg 93##ledcolor red##” just to see if that would give more status information but it didn't.
I then left it running overnight with a nominal 30 second sample interval. This was off the Staples powered hub which gave problems before but with the “uplink” USB port plugged into my laptop and also my mouse, a USB to serial adapter for a Current Cost meter and a 1-wire adapter with a few temperature sensors plugged in. Power to the hub was from mains. This combination has been running well for a few days and continued to operate nominally overnight.
The LED was off for a few seconds, on orange for a few seconds then turned to cyan. A second or so later MQTT data was logged which seemed reasonable. The LED remained on cyan for about 30 seconds then the cycle repeated.
The only untoward event noted overnight was a single “%CO2%” reading.
This morning I disconnected the other devices connected to the hub and also disconnected the hub's upstream USB connection from the laptop leaving just the mains supply and the CO₂ monitor plugged in to it. This was one of the combinations which caused problems before.
For about half the cycles the LED operated as before. For the remainder it didn't come on at all. I.e., it either stays off completely or goes through the whole off/orange/cyan sequence as above. I didn't notice any where it just stayed orange or cyan or anything like that.
It's been running for quite a few hours now but has not stopped as it did before.
The data for temperature, pressure and humidity seem sensible. There was a short run of CO₂ readings of 2147483649 (i.e., a 32-bit signed -1 interpreted as unsigned, I assume). Since then there have been quite a lot of %CO2% readings. I've not watched it all the time (of course) but I have seen valid-looking CO₂ readings in cycles with the LED on and with it off. I've also seen %CO2% with the light on. I haven't noticed any %CO2% readings with the LED off.
When the LED is on I think the %CO2% readings are much more common; I've only seen a few valid looking readings with the LED on.
In addition, the CO₂ reading is not updating much. For example it was stuck on 795 for quite a long time then suddenly jumped to 1383 and stuck on that. Log file attached.
It only connects to the router for a second or so: I had a ping -a running which usually beeped once, sometimes twice, occasionally not at all. Just as an experiment I tried the command “prop_jset "event.wifiDisconnected"##ledbrg 93##ledcolor red##” just to see if that would give more status information but it didn't.
I then left it running overnight with a nominal 30 second sample interval. This was off the Staples powered hub which gave problems before but with the “uplink” USB port plugged into my laptop and also my mouse, a USB to serial adapter for a Current Cost meter and a 1-wire adapter with a few temperature sensors plugged in. Power to the hub was from mains. This combination has been running well for a few days and continued to operate nominally overnight.
The LED was off for a few seconds, on orange for a few seconds then turned to cyan. A second or so later MQTT data was logged which seemed reasonable. The LED remained on cyan for about 30 seconds then the cycle repeated.
The only untoward event noted overnight was a single “%CO2%” reading.
This morning I disconnected the other devices connected to the hub and also disconnected the hub's upstream USB connection from the laptop leaving just the mains supply and the CO₂ monitor plugged in to it. This was one of the combinations which caused problems before.
For about half the cycles the LED operated as before. For the remainder it didn't come on at all. I.e., it either stays off completely or goes through the whole off/orange/cyan sequence as above. I didn't notice any where it just stayed orange or cyan or anything like that.
It's been running for quite a few hours now but has not stopped as it did before.
The data for temperature, pressure and humidity seem sensible. There was a short run of CO₂ readings of 2147483649 (i.e., a 32-bit signed -1 interpreted as unsigned, I assume). Since then there have been quite a lot of %CO2% readings. I've not watched it all the time (of course) but I have seen valid-looking CO₂ readings in cycles with the LED on and with it off. I've also seen %CO2% with the light on. I haven't noticed any %CO2% readings with the LED off.
When the LED is on I think the %CO2% readings are much more common; I've only seen a few valid looking readings with the LED on.
In addition, the CO₂ reading is not updating much. For example it was stuck on 795 for quite a long time then suddenly jumped to 1383 and stuck on that. Log file attached.