Sensor data sometimes not showing in 2nd browser

[davebuk]

Device

Wemos D1 mini

Version

1.22.0-git46719eec

Question

I have setup two wemos d1 mini devices running the same firmware using the below definitions.

The first device was just for BME280 data and doesn't have anything else connected. This works as expected.

The second device was originally just a relay control with schedule and sun times running. The schedules didn't work reliably so I deleted them and use openHAB to control the relay. I re-flashed the second device adding BME280 support to read outdoor data. For some reason this second device doesn't show the BME280 data on the webUI but shows the mqtt data for temp/px/hum fine. I removed the sch keys in case that was causing the issue but doesn't effect SENSORS in the webUI menu list or data being shown on the status page.

I have got a longer wire on the the BME280 sensor on the device not showing data but I would have thought that if there is mqtt data, sensor data should be shown on the webUI.

What makes the firmware show the sensor link on the left of the webUI?

i2c.scan shows:

i2c.scan
0x76
found 1 device(s)
+OK

sensors
 0 * temperature @ BME280 @ I2C (0x76) => .013.118.001.001
 1 * humidity @ BME280 @ I2C (0x76) => .013.118.002.002
 2 * pressure @ BME280 @ I2C (0x76) => .013.118.003.003
+OK

   #define MANUFACTURER        "WEMOS"
   #define DEVICE              "WEMOS_BMX280"

   //My config

   #define DEBUG_SERIAL_SUPPORT    0
   #define ALEXA_SUPPORT           0
   #define DOMOTICZ_SUPPORT        0
   #define HOMEASSISTANT_SUPPORT   0
   #define THINGSPEAK_SUPPORT      0
   #define RPN_RULES_SUPPORT       0
   #define NTP_TIMEZONE            TZ_Europe_London
   
   
   // Buttons
   #define BUTTON_MQTT_SEND_ALL_EVENTS     1
   #define BUTTON1_PIN         14    // D5
   #define BUTTON1_CONFIG      BUTTON_PUSHBUTTON | BUTTON_DEFAULT_HIGH | BUTTON_SET_PULLUP
   #define BUTTON1_RELAY       1


   // Relays
   #define RELAY1_PIN          5    // D1
   #define RELAY1_TYPE         RELAY_TYPE_NORMAL


   // LEDs
   #define LED1_PIN            2    // D4
   #define LED1_PIN_INVERSE    1
   
  // Extras    
   #define BMX280_SUPPORT 1
   #define I2C_SDA_PIN 12    // D6
   #define I2C_SCL_PIN 13    // D7

[mcspr]

See info output and look for WEB_something? WebUI has different packages, only WEB_SENSOR and WEB_FULL contain sensor config & output. Sensor loading is also sometimes delayed, page reload might help if the previous one was during the sensor search / setup. Assuming sensor is discovered and working, i.e. logs also show MQTT publishes (as broker payloads might've been cached)

The second device was originally just a relay control with schedule and sun times running. The schedules didn't work reliably so I deleted them and use openHAB to control the relay.

Would you mind sharing the specific rules that were not working in a separate issue?

[davebuk]

device: WEMOS_WEMOS_1RY_SWITCH
mcu: esp8266 chipid: C8C9A31471CB freq: 80mhz
sdk: 2.2.2-dev(38a443e) core: 3.1.2
md5: 70748305b9fe7e422f3c005a3f16502b
support: API BUTTON DEBUG_TELNET DEBUG_WEB I2C LED MDNS MQTT NTP ARDUINO_OTA OTA_WEB OTA_CLIENT METRICS RELAY SCHEDULER SENSOR TELNET TERMINAL UART WEB_SENSOR 
sensors: BMX280 
system: OK boot counter: 1
last reset reason: Reboot from web interface
+OK

Multiple restarts of the device doesn't fix it. MQTT is sending variable data to the broker so it seems the data is being read and output. I'll try another sensor on a short wire and see if that brings up the webUI SENSOR section.

I can't remember the exact string I was using for the schedule but there were two. One turned ON the relay 15mins AFTER SUNRISE every day and the other turned relay OFF 15 mins BEFORE SUNSET. It is to control the illumination inside my bird box live stream.

The relay would always work at the correct time. I tried deleting the entries from the webUI but they would not delete. I could only get rid of the entries by deleting the keys for each entry. #2660

[davebuk]

I've tried a different sensor on a short standard wire (this is a third sensor, first one is working fine on another wemos d1 mini) but there isn't any difference to the second sensor. Neither of them show data on the webUI but do show data in the debug screen and output via MQTT.

I'll try a factory re-set and see what that does.

[davebuk]

Factory reset has brought back the webUI for the sensor and menu entry on the left. I did change the device DNS name and description fields which broke it again. After power cycling the device it seems to be working again.

I'll close the issue.

[mcspr]

from #2660

I use chrome on windows and android. Oddly I'd been viewing the webUI on my phone then went to my windows pc to grab some of the debug data. The sensor stuff wouldn't show on windows chrome but is fine on android. Before factory reset it wouldn't show sensors on either but only for that one device.

and from here

I did change the device DNS name and description fields which broke it again. After power cycling the device it seems to be working again.

so the issue seems to be multiple clients. usually it is silently failing because of out-of-memory conditions; currently the code just tries to work around general timing issue, but 2nd device may simply receive the initial parts of the config and then silently fail for the rest

while the data from sensors does eventually flow to the ui, it is not anticipating or parsing it. client never received config that told it so. there are several issues on top of each other here...

[davebuk]

Initial test seems to be working correctly with the fix.

[davebuk]

Did you want this issue closed?