#bme680 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #bme680, aggregated by home.social.
-
LED Matrix mit MAX7219 und ESP32 ansteuern
Aus der Krabbelkiste zur fertigen Smart-Clock: Wie ein kleines Winterprojekt mit einer Handvoll AliExpress-Modulen und einem ESP32 zur ultimativen LED-Matrix-Uhr “Dottie” heranwuchs.
#1088AS #74HCT245 #BME680 #DIYUhr #DS3231 #ESP32 #IoT #kicad #LEDMatrix #MAX7219 #ntp #OpenSource #Pegelwandler #PlatformIO #RTC #SmartClock #SmartHome #VEML7700
https://dirkwouters.de/led-matrix-mit-max7219-und-esp32-ansteuern/
-
LED Matrix mit MAX7219 und ESP32 ansteuern
Aus der Krabbelkiste zur fertigen Smart-Clock: Wie ein kleines Winterprojekt mit einer Handvoll AliExpress-Modulen und einem ESP32 zur ultimativen LED-Matrix-Uhr “Dottie” heranwuchs.
#1088AS #74HCT245 #BME680 #DIYUhr #DS3231 #ESP32 #IoT #kicad #LEDMatrix #MAX7219 #ntp #OpenSource #Pegelwandler #PlatformIO #RTC #SmartClock #SmartHome #VEML7700
https://dirkwouters.de/led-matrix-mit-max7219-und-esp32-ansteuern/
-
After all this time fiddling with my DIY air quality sensor, I’m still not sure how to read the sensor readings
Here a little bit about today’s adventure
today’s context
I am sitting on the train and the car is mostly full (about 30 adults). We’ve been at full speed for a good twenty minutes, so anything that needed to settle surely has by now. The train itself was put in service last year or whereabouts, so it’s neither brand new nor crumbling old.
The BME680 sensor I’m using has a three minute self calibration sequence that simply won’t give any readings. Anything I get is after 300s.
sensor readings and doubts
My issue is that at 14 minutes into the ride, the readings were still unsettled. Is that due to the train moving? The sensor not having enough air flow during its startup sequence to calibrate correctly?
At 24 minutes into the ride, the values look suspiciously like default values. Temperature at a steady 25, VOC reading near 25.0 and eCO2 at 500 (give or take a few units).
pressure readings make me more confident
I noticed the pressure sensor reads somewhat different values, sometimes 80 Pa difference in a few seconds even though we are at a steady pace, apparently on even ground, and the weather doesn’t appear to change. But it is very cloudy outside so who knows, maybe our speed causes us to go through more local weather differences than I realize.
However, when the train slows to a crawl, the pressure readings stabilize a lot. They start fluctuating again after we picked up some speed.
the end
I don’t quite understand the sensor’s fondness for eCO2 values so close to the 500 mark. This is a train car full of people, possibly with a working ventilation and filtering system, but I didn’t expect near-perfect or steady readings (for half an hour now).
-
After all this time fiddling with my DIY air quality sensor, I’m still not sure how to read the sensor readings
Here a little bit about today’s adventure
today’s context
I am sitting on the train and the car is mostly full (about 30 adults). We’ve been at full speed for a good twenty minutes, so anything that needed to settle surely has by now. The train itself was put in service last year or whereabouts, so it’s neither brand new nor crumbling old.
The BME680 sensor I’m using has a three minute self calibration sequence that simply won’t give any readings. Anything I get is after 300s.
sensor readings and doubts
My issue is that at 14 minutes into the ride, the readings were still unsettled. Is that due to the train moving? The sensor not having enough air flow during its startup sequence to calibrate correctly?
At 24 minutes into the ride, the values look suspiciously like default values. Temperature at a steady 25, VOC reading near 25.0 and eCO2 at 500 (give or take a few units).
pressure readings make me more confident
I noticed the pressure sensor reads somewhat different values, sometimes 80 Pa difference in a few seconds even though we are at a steady pace, apparently on even ground, and the weather doesn’t appear to change. But it is very cloudy outside so who knows, maybe our speed causes us to go through more local weather differences than I realize.
However, when the train slows to a crawl, the pressure readings stabilize a lot. They start fluctuating again after we picked up some speed.
the end
I don’t quite understand the sensor’s fondness for eCO2 values so close to the 500 mark. This is a train car full of people, possibly with a working ventilation and filtering system, but I didn’t expect near-perfect or steady readings (for half an hour now).
-
After all this time fiddling with my DIY air quality sensor, I’m still not sure how to read the sensor readings
Here a little bit about today’s adventure
today’s context
I am sitting on the train and the car is mostly full (about 30 adults). We’ve been at full speed for a good twenty minutes, so anything that needed to settle surely has by now. The train itself was put in service last year or whereabouts, so it’s neither brand new nor crumbling old.
The BME680 sensor I’m using has a three minute self calibration sequence that simply won’t give any readings. Anything I get is after 300s.
sensor readings and doubts
My issue is that at 14 minutes into the ride, the readings were still unsettled. Is that due to the train moving? The sensor not having enough air flow during its startup sequence to calibrate correctly?
At 24 minutes into the ride, the values look suspiciously like default values. Temperature at a steady 25, VOC reading near 25.0 and eCO2 at 500 (give or take a few units).
pressure readings make me more confident
I noticed the pressure sensor reads somewhat different values, sometimes 80 Pa difference in a few seconds even though we are at a steady pace, apparently on even ground, and the weather doesn’t appear to change. But it is very cloudy outside so who knows, maybe our speed causes us to go through more local weather differences than I realize.
However, when the train slows to a crawl, the pressure readings stabilize a lot. They start fluctuating again after we picked up some speed.
the end
I don’t quite understand the sensor’s fondness for eCO2 values so close to the 500 mark. This is a train car full of people, possibly with a working ventilation and filtering system, but I didn’t expect near-perfect or steady readings (for half an hour now).
-
After all this time fiddling with my DIY air quality sensor, I’m still not sure how to read the sensor readings
Here a little bit about today’s adventure
today’s context
I am sitting on the train and the car is mostly full (about 30 adults). We’ve been at full speed for a good twenty minutes, so anything that needed to settle surely has by now. The train itself was put in service last year or whereabouts, so it’s neither brand new nor crumbling old.
The BME680 sensor I’m using has a three minute self calibration sequence that simply won’t give any readings. Anything I get is after 300s.
sensor readings and doubts
My issue is that at 14 minutes into the ride, the readings were still unsettled. Is that due to the train moving? The sensor not having enough air flow during its startup sequence to calibrate correctly?
At 24 minutes into the ride, the values look suspiciously like default values. Temperature at a steady 25, VOC reading near 25.0 and eCO2 at 500 (give or take a few units).
pressure readings make me more confident
I noticed the pressure sensor reads somewhat different values, sometimes 80 Pa difference in a few seconds even though we are at a steady pace, apparently on even ground, and the weather doesn’t appear to change. But it is very cloudy outside so who knows, maybe our speed causes us to go through more local weather differences than I realize.
However, when the train slows to a crawl, the pressure readings stabilize a lot. They start fluctuating again after we picked up some speed.
the end
I don’t quite understand the sensor’s fondness for eCO2 values so close to the 500 mark. This is a train car full of people, possibly with a working ventilation and filtering system, but I didn’t expect near-perfect or steady readings (for half an hour now).
-
After all this time fiddling with my DIY air quality sensor, I’m still not sure how to read the sensor readings
Here a little bit about today’s adventure
today’s context
I am sitting on the train and the car is mostly full (about 30 adults). We’ve been at full speed for a good twenty minutes, so anything that needed to settle surely has by now. The train itself was put in service last year or whereabouts, so it’s neither brand new nor crumbling old.
The BME680 sensor I’m using has a three minute self calibration sequence that simply won’t give any readings. Anything I get is after 300s.
sensor readings and doubts
My issue is that at 14 minutes into the ride, the readings were still unsettled. Is that due to the train moving? The sensor not having enough air flow during its startup sequence to calibrate correctly?
At 24 minutes into the ride, the values look suspiciously like default values. Temperature at a steady 25, VOC reading near 25.0 and eCO2 at 500 (give or take a few units).
pressure readings make me more confident
I noticed the pressure sensor reads somewhat different values, sometimes 80 Pa difference in a few seconds even though we are at a steady pace, apparently on even ground, and the weather doesn’t appear to change. But it is very cloudy outside so who knows, maybe our speed causes us to go through more local weather differences than I realize.
However, when the train slows to a crawl, the pressure readings stabilize a lot. They start fluctuating again after we picked up some speed.
the end
I don’t quite understand the sensor’s fondness for eCO2 values so close to the 500 mark. This is a train car full of people, possibly with a working ventilation and filtering system, but I didn’t expect near-perfect or steady readings (for half an hour now).
-
Artikel-Update:
I2C-#Sensoren am #Elecrow #LoRaWAN #LR1262 Dev.-Board mit #Raspi-Pico 2040
ergänzt: Sensoren #BME280 und #BME680
--> https://cool-web.de/raspberry/elecrow-rp2040-sx1262-lorawan-development-board-i2c-sensors-bmp280.htm
#LoRa #Bosch #Sensortec #BMP280 #RaspberryPi #Raspi #PiPico #RP2040 #Elektronik #Maker #DIY #Microcontroller #Elecrow
-
Artikel-Update:
I2C-#Sensoren am #Elecrow #LoRaWAN #LR1262 Dev.-Board mit #Raspi-Pico 2040
ergänzt: Sensoren #BME280 und #BME680
--> https://cool-web.de/raspberry/elecrow-rp2040-sx1262-lorawan-development-board-i2c-sensors-bmp280.htm
#LoRa #Bosch #Sensortec #BMP280 #RaspberryPi #Raspi #PiPico #RP2040 #Elektronik #Maker #DIY #Microcontroller #Elecrow
-
Artikel-Update:
I2C-#Sensoren am #Elecrow #LoRaWAN #LR1262 Dev.-Board mit #Raspi-Pico 2040
ergänzt: Sensoren #BME280 und #BME680
--> https://cool-web.de/raspberry/elecrow-rp2040-sx1262-lorawan-development-board-i2c-sensors-bmp280.htm
#LoRa #Bosch #Sensortec #BMP280 #RaspberryPi #Raspi #PiPico #RP2040 #Elektronik #Maker #DIY #Microcontroller #Elecrow
-
Artikel-Update:
I2C-#Sensoren am #Elecrow #LoRaWAN #LR1262 Dev.-Board mit #Raspi-Pico 2040
ergänzt: Sensoren #BME280 und #BME680
--> https://cool-web.de/raspberry/elecrow-rp2040-sx1262-lorawan-development-board-i2c-sensors-bmp280.htm
#LoRa #Bosch #Sensortec #BMP280 #RaspberryPi #Raspi #PiPico #RP2040 #Elektronik #Maker #DIY #Microcontroller #Elecrow
-
Artikel-Update:
I2C-#Sensoren am #Elecrow #LoRaWAN #LR1262 Dev.-Board mit #Raspi-Pico 2040
ergänzt: Sensoren #BME280 und #BME680
--> https://cool-web.de/raspberry/elecrow-rp2040-sx1262-lorawan-development-board-i2c-sensors-bmp280.htm
#LoRa #Bosch #Sensortec #BMP280 #RaspberryPi #Raspi #PiPico #RP2040 #Elektronik #Maker #DIY #Microcontroller #Elecrow
-
T-Echo Plus #Meshtastic Gerät mit Umwelt-#Telemetrie-#Sensor erweitern
--> https://cool-web.de/nrf/lilygo-t-echo-plus-lora-meshtastic-bme280-bme680-i2c-sensor-anschliessen.htm
#nRF #nRF52840 #LILYGO #TEchoPlus #I2C #BMP280 #BME280 #BME680 #Maker #DIY #Mikrocontroller #LoRa #Funknetzwerk #868MHz #Jedermannfunk #Hardware #Analyse #Oszilloskop
-
T-Echo Plus #Meshtastic Gerät mit Umwelt-#Telemetrie-#Sensor erweitern
--> https://cool-web.de/nrf/lilygo-t-echo-plus-lora-meshtastic-bme280-bme680-i2c-sensor-anschliessen.htm
#nRF #nRF52840 #LILYGO #TEchoPlus #I2C #BMP280 #BME280 #BME680 #Maker #DIY #Mikrocontroller #LoRa #Funknetzwerk #868MHz #Jedermannfunk #Hardware #Analyse #Oszilloskop
-
T-Echo Plus #Meshtastic Gerät mit Umwelt-#Telemetrie-#Sensor erweitern
--> https://cool-web.de/nrf/lilygo-t-echo-plus-lora-meshtastic-bme280-bme680-i2c-sensor-anschliessen.htm
#nRF #nRF52840 #LILYGO #TEchoPlus #I2C #BMP280 #BME280 #BME680 #Maker #DIY #Mikrocontroller #LoRa #Funknetzwerk #868MHz #Jedermannfunk #Hardware #Analyse #Oszilloskop
-
T-Echo Plus #Meshtastic Gerät mit Umwelt-#Telemetrie-#Sensor erweitern
--> https://cool-web.de/nrf/lilygo-t-echo-plus-lora-meshtastic-bme280-bme680-i2c-sensor-anschliessen.htm
#nRF #nRF52840 #LILYGO #TEchoPlus #I2C #BMP280 #BME280 #BME680 #Maker #DIY #Mikrocontroller #LoRa #Funknetzwerk #868MHz #Jedermannfunk #Hardware #Analyse #Oszilloskop
-
T-Echo Plus #Meshtastic Gerät mit Umwelt-#Telemetrie-#Sensor erweitern
--> https://cool-web.de/nrf/lilygo-t-echo-plus-lora-meshtastic-bme280-bme680-i2c-sensor-anschliessen.htm
#nRF #nRF52840 #LILYGO #TEchoPlus #I2C #BMP280 #BME280 #BME680 #Maker #DIY #Mikrocontroller #LoRa #Funknetzwerk #868MHz #Jedermannfunk #Hardware #Analyse #Oszilloskop
-
#Sensor #Bosch #BME680 als #Thermometer, #Barometer, #Hygrometer und VOC-Meter nutzen
#RaspberryPi #Raspi #Pico #RP2040 #Maker #DIY #Mikrocontroller #Elecrow #LoRa #BMP280 #BME280 #AHT20 #VOC #Gase #I2C #Luftqualität #Luftdruck #Temperatur
-
#Sensor #Bosch #BME680 als #Thermometer, #Barometer, #Hygrometer und VOC-Meter nutzen
#RaspberryPi #Raspi #Pico #RP2040 #Maker #DIY #Mikrocontroller #Elecrow #LoRa #BMP280 #BME280 #AHT20 #VOC #Gase #I2C #Luftqualität #Luftdruck #Temperatur
-
#Sensor #Bosch #BME680 als #Thermometer, #Barometer, #Hygrometer und VOC-Meter nutzen
#RaspberryPi #Raspi #Pico #RP2040 #Maker #DIY #Mikrocontroller #Elecrow #LoRa #BMP280 #BME280 #AHT20 #VOC #Gase #I2C #Luftqualität #Luftdruck #Temperatur
-
#Sensor #Bosch #BME680 als #Thermometer, #Barometer, #Hygrometer und VOC-Meter nutzen
#RaspberryPi #Raspi #Pico #RP2040 #Maker #DIY #Mikrocontroller #Elecrow #LoRa #BMP280 #BME280 #AHT20 #VOC #Gase #I2C #Luftqualität #Luftdruck #Temperatur
-
#Sensor #Bosch #BME680 als #Thermometer, #Barometer, #Hygrometer und VOC-Meter nutzen
#RaspberryPi #Raspi #Pico #RP2040 #Maker #DIY #Mikrocontroller #Elecrow #LoRa #BMP280 #BME280 #AHT20 #VOC #Gase #I2C #Luftqualität #Luftdruck #Temperatur
-
Trying to set up an ESP32 to send weather data via MQTT to my PC.
I have not managed.
-
Trying to set up an ESP32 to send weather data via MQTT to my PC.
I have not managed.
-
Trying to set up an ESP32 to send weather data via MQTT to my PC.
I have not managed.
-
Trying to set up an ESP32 to send weather data via MQTT to my PC.
I have not managed.
-
Nachdem ich heute entdeckt habe das man sich schon für ca. 7€ inkl. Porto Platinen professionell erstellen lassen kann habe ich mal KiCad ausprobiert für ein Flipper Zero Board mit meinen Sensoren.
KiCad zeigt mir noch zwei Fehler an für die 2 GND Verbindungen, die laut KiCad zu Pin 8 und 18 gehen sollen.
Die 2 Leiterbahnen sind aber korrekt mit Pin 11 verbunden.#FlipperZero #Flipper #hardware #sensors #diy #SCD40 #BME680 #BME280 #KiCad
-
Nachdem ich heute entdeckt habe das man sich schon für ca. 7€ inkl. Porto Platinen professionell erstellen lassen kann habe ich mal KiCad ausprobiert für ein Flipper Zero Board mit meinen Sensoren.
KiCad zeigt mir noch zwei Fehler an für die 2 GND Verbindungen, die laut KiCad zu Pin 8 und 18 gehen sollen.
Die 2 Leiterbahnen sind aber korrekt mit Pin 11 verbunden.#FlipperZero #Flipper #hardware #sensors #diy #SCD40 #BME680 #BME280 #KiCad
-
Nachdem ich heute entdeckt habe das man sich schon für ca. 7€ inkl. Porto Platinen professionell erstellen lassen kann habe ich mal KiCad ausprobiert für ein Flipper Zero Board mit meinen Sensoren.
KiCad zeigt mir noch zwei Fehler an für die 2 GND Verbindungen, die laut KiCad zu Pin 8 und 18 gehen sollen.
Die 2 Leiterbahnen sind aber korrekt mit Pin 11 verbunden.#FlipperZero #Flipper #hardware #sensors #diy #SCD40 #BME680 #BME280 #KiCad
-
"Stoßlüften" (Shock ventilation) works.
-
"Stoßlüften" (Shock ventilation) works.
-
"Stoßlüften" (Shock ventilation) works.
-
"Stoßlüften" (Shock ventilation) works.
-
"Stoßlüften" (Shock ventilation) works.
-
The #BME680 component seems awfully unreliable after all
Its VOC is wild, and the temperature measurements are consistently 2°C too high (compared with commercially available sensors)
-
The #BME680 component seems awfully unreliable after all
Its VOC is wild, and the temperature measurements are consistently 2°C too high (compared with commercially available sensors)
-
The #BME680 component seems awfully unreliable after all
Its VOC is wild, and the temperature measurements are consistently 2°C too high (compared with commercially available sensors)
-
The #BME680 component seems awfully unreliable after all
Its VOC is wild, and the temperature measurements are consistently 2°C too high (compared with commercially available sensors)
-
Today I soldered a few more of my custom air quality thingies, flashed them with the exact same program as the other ones, gave them a USB adapter and plugged them in their own spot in the house
They automatically found their path in the mesh, then they started sharing and recording their readings, which automatically appeared in my dashboard, and all I had to do was rename them there
In the picture, the number in the parentheses is the number of readings for the day (more or less one per minute) and all bars and lines represent average readings for the day; I have one graph per room to get the timelines
Humidity and temperature are on the left axis, all the other are on the right axis
(Looks like the one in the bedroom crashed again)
The one in the attic is missing however long it took me to solder the new things, since that’s the one I unplugged to use as a template
-
Today I soldered a few more of my custom air quality thingies, flashed them with the exact same program as the other ones, gave them a USB adapter and plugged them in their own spot in the house
They automatically found their path in the mesh, then they started sharing and recording their readings, which automatically appeared in my dashboard, and all I had to do was rename them there
In the picture, the number in the parentheses is the number of readings for the day (more or less one per minute) and all bars and lines represent average readings for the day; I have one graph per room to get the timelines
Humidity and temperature are on the left axis, all the other are on the right axis
(Looks like the one in the bedroom crashed again)
The one in the attic is missing however long it took me to solder the new things, since that’s the one I unplugged to use as a template
-
Today I soldered a few more of my custom air quality thingies, flashed them with the exact same program as the other ones, gave them a USB adapter and plugged them in their own spot in the house
They automatically found their path in the mesh, then they started sharing and recording their readings, which automatically appeared in my dashboard, and all I had to do was rename them there
In the picture, the number in the parentheses is the number of readings for the day (more or less one per minute) and all bars and lines represent average readings for the day; I have one graph per room to get the timelines
Humidity and temperature are on the left axis, all the other are on the right axis
(Looks like the one in the bedroom crashed again)
The one in the attic is missing however long it took me to solder the new things, since that’s the one I unplugged to use as a template
-
Today I soldered a few more of my custom air quality thingies, flashed them with the exact same program as the other ones, gave them a USB adapter and plugged them in their own spot in the house
They automatically found their path in the mesh, then they started sharing and recording their readings, which automatically appeared in my dashboard, and all I had to do was rename them there
In the picture, the number in the parentheses is the number of readings for the day (more or less one per minute) and all bars and lines represent average readings for the day; I have one graph per room to get the timelines
Humidity and temperature are on the left axis, all the other are on the right axis
(Looks like the one in the bedroom crashed again)
The one in the attic is missing however long it took me to solder the new things, since that’s the one I unplugged to use as a template
-
Today I soldered a few more of my custom air quality thingies, flashed them with the exact same program as the other ones, gave them a USB adapter and plugged them in their own spot in the house
They automatically found their path in the mesh, then they started sharing and recording their readings, which automatically appeared in my dashboard, and all I had to do was rename them there
In the picture, the number in the parentheses is the number of readings for the day (more or less one per minute) and all bars and lines represent average readings for the day; I have one graph per room to get the timelines
Humidity and temperature are on the left axis, all the other are on the right axis
(Looks like the one in the bedroom crashed again)
The one in the attic is missing however long it took me to solder the new things, since that’s the one I unplugged to use as a template
-
This morning my ISP had an outage and I restarted their router, which happens to power my rpi0 with the web server for this project
And I forgot to restart that web server, so I lost all data from today
But before that, it was performing beautifully. There were 844 records for each node since last night, like clockwork. I happen to have cleared my previous data last night, so all the nodes were running and already on a stable mesh at the time.
Each sensor has been broadcasting its readings every three seconds, at which point my server decides to ignore most readings until the 1 minute mark (per sensor) and I’m happy that not one minute was lost for half a day of recording
I am less happy that after the web server was restarted, none of the microcontrollers found it by themselves. It looks like the entire mesh collapsed because the root node couldn’t bridge both networks again.
I understand that the root node didn’t restart the bridge between both WiFi (I didn’t set it up that way), but I would have thought that the iot mesh should have continued independently? Perhaps because it is declared as the root node? I’ll have to test this more.
I reset the ESP32 root node and it picked up the home WiFi fine, but none of the probes connected to it again (this mesh should have self healed within minutes, at most)
I went around the house to reset each ESP8266 node and yes, that is when the mesh self organized again and I started seeing the web server collecting readings again, as their BME680 sensor finished its self calibration routine
#meshnetwork #AirQuality #esp32 #esp8266 #bme680 #raspberrypi
-
This morning my ISP had an outage and I restarted their router, which happens to power my rpi0 with the web server for this project
And I forgot to restart that web server, so I lost all data from today
But before that, it was performing beautifully. There were 844 records for each node since last night, like clockwork. I happen to have cleared my previous data last night, so all the nodes were running and already on a stable mesh at the time.
Each sensor has been broadcasting its readings every three seconds, at which point my server decides to ignore most readings until the 1 minute mark (per sensor) and I’m happy that not one minute was lost for half a day of recording
I am less happy that after the web server was restarted, none of the microcontrollers found it by themselves. It looks like the entire mesh collapsed because the root node couldn’t bridge both networks again.
I understand that the root node didn’t restart the bridge between both WiFi (I didn’t set it up that way), but I would have thought that the iot mesh should have continued independently? Perhaps because it is declared as the root node? I’ll have to test this more.
I reset the ESP32 root node and it picked up the home WiFi fine, but none of the probes connected to it again (this mesh should have self healed within minutes, at most)
I went around the house to reset each ESP8266 node and yes, that is when the mesh self organized again and I started seeing the web server collecting readings again, as their BME680 sensor finished its self calibration routine
#meshnetwork #AirQuality #esp32 #esp8266 #bme680 #raspberrypi
-
This morning my ISP had an outage and I restarted their router, which happens to power my rpi0 with the web server for this project
And I forgot to restart that web server, so I lost all data from today
But before that, it was performing beautifully. There were 844 records for each node since last night, like clockwork. I happen to have cleared my previous data last night, so all the nodes were running and already on a stable mesh at the time.
Each sensor has been broadcasting its readings every three seconds, at which point my server decides to ignore most readings until the 1 minute mark (per sensor) and I’m happy that not one minute was lost for half a day of recording
I am less happy that after the web server was restarted, none of the microcontrollers found it by themselves. It looks like the entire mesh collapsed because the root node couldn’t bridge both networks again.
I understand that the root node didn’t restart the bridge between both WiFi (I didn’t set it up that way), but I would have thought that the iot mesh should have continued independently? Perhaps because it is declared as the root node? I’ll have to test this more.
I reset the ESP32 root node and it picked up the home WiFi fine, but none of the probes connected to it again (this mesh should have self healed within minutes, at most)
I went around the house to reset each ESP8266 node and yes, that is when the mesh self organized again and I started seeing the web server collecting readings again, as their BME680 sensor finished its self calibration routine
#meshnetwork #AirQuality #esp32 #esp8266 #bme680 #raspberrypi
-
This morning my ISP had an outage and I restarted their router, which happens to power my rpi0 with the web server for this project
And I forgot to restart that web server, so I lost all data from today
But before that, it was performing beautifully. There were 844 records for each node since last night, like clockwork. I happen to have cleared my previous data last night, so all the nodes were running and already on a stable mesh at the time.
Each sensor has been broadcasting its readings every three seconds, at which point my server decides to ignore most readings until the 1 minute mark (per sensor) and I’m happy that not one minute was lost for half a day of recording
I am less happy that after the web server was restarted, none of the microcontrollers found it by themselves. It looks like the entire mesh collapsed because the root node couldn’t bridge both networks again.
I understand that the root node didn’t restart the bridge between both WiFi (I didn’t set it up that way), but I would have thought that the iot mesh should have continued independently? Perhaps because it is declared as the root node? I’ll have to test this more.
I reset the ESP32 root node and it picked up the home WiFi fine, but none of the probes connected to it again (this mesh should have self healed within minutes, at most)
I went around the house to reset each ESP8266 node and yes, that is when the mesh self organized again and I started seeing the web server collecting readings again, as their BME680 sensor finished its self calibration routine
#meshnetwork #AirQuality #esp32 #esp8266 #bme680 #raspberrypi
-
This morning my ISP had an outage and I restarted their router, which happens to power my rpi0 with the web server for this project
And I forgot to restart that web server, so I lost all data from today
But before that, it was performing beautifully. There were 844 records for each node since last night, like clockwork. I happen to have cleared my previous data last night, so all the nodes were running and already on a stable mesh at the time.
Each sensor has been broadcasting its readings every three seconds, at which point my server decides to ignore most readings until the 1 minute mark (per sensor) and I’m happy that not one minute was lost for half a day of recording
I am less happy that after the web server was restarted, none of the microcontrollers found it by themselves. It looks like the entire mesh collapsed because the root node couldn’t bridge both networks again.
I understand that the root node didn’t restart the bridge between both WiFi (I didn’t set it up that way), but I would have thought that the iot mesh should have continued independently? Perhaps because it is declared as the root node? I’ll have to test this more.
I reset the ESP32 root node and it picked up the home WiFi fine, but none of the probes connected to it again (this mesh should have self healed within minutes, at most)
I went around the house to reset each ESP8266 node and yes, that is when the mesh self organized again and I started seeing the web server collecting readings again, as their BME680 sensor finished its self calibration routine
#meshnetwork #AirQuality #esp32 #esp8266 #bme680 #raspberrypi
-
DIY устройство в подрозетник с датчиками окружающей среды в комнате
Я не являюсь экспертом в схемотехнике и разработке печатных плат, это был мой первый опыт в этой области, и, конечно, я ожидал, что мой путь будет долгим и тернистым. Но я был решительно настроен, так как конечный результат должен быть использован в моем доме как полноценно работающее устройство.
https://habr.com/ru/articles/841532/
#diy_умный_дом #homeassistant #esp32 #esphome #sensors #scd40 #ld2410c #bme680 #подрозетник
-
DIY устройство в подрозетник с датчиками окружающей среды в комнате
Я не являюсь экспертом в схемотехнике и разработке печатных плат, это был мой первый опыт в этой области, и, конечно, я ожидал, что мой путь будет долгим и тернистым. Но я был решительно настроен, так как конечный результат должен быть использован в моем доме как полноценно работающее устройство.
https://habr.com/ru/articles/841532/
#diy_умный_дом #homeassistant #esp32 #esphome #sensors #scd40 #ld2410c #bme680 #подрозетник
-
DIY устройство в подрозетник с датчиками окружающей среды в комнате
Я не являюсь экспертом в схемотехнике и разработке печатных плат, это был мой первый опыт в этой области, и, конечно, я ожидал, что мой путь будет долгим и тернистым. Но я был решительно настроен, так как конечный результат должен быть использован в моем доме как полноценно работающее устройство.
https://habr.com/ru/articles/841532/
#diy_умный_дом #homeassistant #esp32 #esphome #sensors #scd40 #ld2410c #bme680 #подрозетник
