ESPEasy does not transfer part of the data
Moderators: grovkillen, Stuntteam, TD-er
ESPEasy does not transfer part of the data
Hello,
I run several NodeMCU which I have flashed with ESPEasy. I integrated this into the home automation using FHEM. There are currently 4 NodeMCU in 4 different rooms, mainly used for shutter control.
Each NodeMCU have 2 buttons, 1 LED and a DHT11, then there are "special functions" that only individual NodeMCU have, such as a BMP280 on the east side of the house for recording the outside temperature or a BH1750 and a TSL2561 for recording the brightness on the south-east side of the house.
Now to the problem that I have: The measured values of the sensors are temporarily not transmitted to FHEM. These are displayed in the ESPEasy web front end, but "absent" is displayed in the FHEM. The settings in ESPEasy are to transmit a measured value every 60 seconds. If this state has occurred, it does not help to reboot the ESPEasy / to press the reset button on the NodeMCU, you have to interrupt the power supply of the NodeMCu and plug it in again, then it works again immediately. Or wait, at sometimes "self-healing" appear and suddenly it works again. The buttons, the LED and the data from the DHT11 work without interruption. Also showed ist the WLAN connection (RSSI), this always works.
Does anyone have any advice on what I can do / where to look to get the transmission of the sensors stable?
Thanks and best regards
Ralf
I run several NodeMCU which I have flashed with ESPEasy. I integrated this into the home automation using FHEM. There are currently 4 NodeMCU in 4 different rooms, mainly used for shutter control.
Each NodeMCU have 2 buttons, 1 LED and a DHT11, then there are "special functions" that only individual NodeMCU have, such as a BMP280 on the east side of the house for recording the outside temperature or a BH1750 and a TSL2561 for recording the brightness on the south-east side of the house.
Now to the problem that I have: The measured values of the sensors are temporarily not transmitted to FHEM. These are displayed in the ESPEasy web front end, but "absent" is displayed in the FHEM. The settings in ESPEasy are to transmit a measured value every 60 seconds. If this state has occurred, it does not help to reboot the ESPEasy / to press the reset button on the NodeMCU, you have to interrupt the power supply of the NodeMCu and plug it in again, then it works again immediately. Or wait, at sometimes "self-healing" appear and suddenly it works again. The buttons, the LED and the data from the DHT11 work without interruption. Also showed ist the WLAN connection (RSSI), this always works.
Does anyone have any advice on what I can do / where to look to get the transmission of the sensors stable?
Thanks and best regards
Ralf
Re: ESPEasy does not transfer part of the data
If this got stuck, can you still perform an I2C scan?
The mentioned sensors that cause issues look to be all I2C.
What other I2C devices are connected? For example an OLED display?
The mentioned sensors that cause issues look to be all I2C.
What other I2C devices are connected? For example an OLED display?
Re: ESPEasy does not transfer part of the data
Hi, thanks for your answer.
How can I do an I2C scan?
In the ESPEasy log file, I see entries for one NodeMCU from the BH1750 but no entries from the TSL2561. If I unplug the TSL, I see error messages in the log that it cannot be reached. No other I2C participants are connected.
At the other NodeMCU, only the BMP280 is on the I2C.
How can I do an I2C scan?
In the ESPEasy log file, I see entries for one NodeMCU from the BH1750 but no entries from the TSL2561. If I unplug the TSL, I see error messages in the log that it cannot be reached. No other I2C participants are connected.
At the other NodeMCU, only the BMP280 is on the I2C.
Re: ESPEasy does not transfer part of the data
It is relevant to know what version of ESPEasy is on the NodeMCU's, the name of the uploaded .bin file is usually the most informative.
/Ton (PayPal.me)
Re: ESPEasy does not transfer part of the data
Via the web interface: Tools -> I2C Scan.
I've seen it happen only a few times myself and some others have reported it also that the I2C bus may get stuck.
What you described that you need to power cycle it, sounds like what may also happen with a stuck I2C bus.
So whenever this occurs again, can you try to perform an I2C scan to see if it reports an error for every I2C address?
If so, then it is almost certain this issue: https://github.com/letscontrolit/ESPEasy/issues/3664
And this PR should hopefully be a fix for it: https://github.com/letscontrolit/ESPEasy/pull/3678
I've seen it happen only a few times myself and some others have reported it also that the I2C bus may get stuck.
What you described that you need to power cycle it, sounds like what may also happen with a stuck I2C bus.
So whenever this occurs again, can you try to perform an I2C scan to see if it reports an error for every I2C address?
If so, then it is almost certain this issue: https://github.com/letscontrolit/ESPEasy/issues/3664
And this PR should hopefully be a fix for it: https://github.com/letscontrolit/ESPEasy/pull/3678
Re: ESPEasy does not transfer part of the data
I found the I2C scan option - i'll look at that if i have the problem the next time.
Firmware
Build:⋄ 20111 - Mega
System Libraries:⋄ ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support
Git Build:⋄
Plugin Count:⋄ 47 [Normal]
Build Origin: Travis
Build Time:⋄ Jan 14 2021 23:29:36
Binary Filename:⋄ ESP_Easy_mega_20210114_normal_ESP8266_4M1M
Build Platform:⋄ Linux-4.19.104-microsoft-standard-x86_64-with-glibc2.29
Git HEAD:⋄ mega-20210114_cdc8a1a
Firmware
Build:⋄ 20111 - Mega
System Libraries:⋄ ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support
Git Build:⋄
Plugin Count:⋄ 47 [Normal]
Build Origin: Travis
Build Time:⋄ Jan 14 2021 23:29:36
Binary Filename:⋄ ESP_Easy_mega_20210114_normal_ESP8266_4M1M
Build Platform:⋄ Linux-4.19.104-microsoft-standard-x86_64-with-glibc2.29
Git HEAD:⋄ mega-20210114_cdc8a1a
Re: ESPEasy does not transfer part of the data
Hello,
now i hane more information:
- the sensor values do not reach the fhem
- the sensor values are displayed in the web front end of the ESPEasy and also change there
-the I2C scan shows the address of the attached module but no error
now i hane more information:
- the sensor values do not reach the fhem
- the sensor values are displayed in the web front end of the ESPEasy and also change there
-the I2C scan shows the address of the attached module but no error
Re: ESPEasy does not transfer part of the data
Maybe have a look at the controller settings then.
For example maybe set the timeout to some higher value like 1000 msec?
For example maybe set the timeout to some higher value like 1000 msec?
Re: ESPEasy does not transfer part of the data
The timeout was / is set to 1000 mS
Re: ESPEasy does not transfer part of the data
Just now i saw at one of the Controllers, that the values of the BMP 280 where freezed. If i start a refresh of the Devices-Site i got the same Values. If i do a I2C scan the controller returns "No I2C devices found".
Now i tun the power off, wait 5 seconds and turn it on - an i got the actual values and the I2C returns the adress of the BMP 280 (0x76).
It seems, the I2C communication don't works.
How can i do?
Now i tun the power off, wait 5 seconds and turn it on - an i got the actual values and the I2C returns the adress of the BMP 280 (0x76).
It seems, the I2C communication don't works.
How can i do?
Last edited by Ralf on 28 Jun 2021, 13:41, edited 1 time in total.
Re: ESPEasy does not transfer part of the data
Yep, that's the issue of an I2C bus that hangs.
Right now I don't have a working automatic fix yet.
I will try to finish this PR soon: https://github.com/letscontrolit/ESPEasy/pull/3678
Right now I don't have a working automatic fix yet.
I will try to finish this PR soon: https://github.com/letscontrolit/ESPEasy/pull/3678
Who is online
Users browsing this forum: No registered users and 140 guests