ESP_Easy_mega-20200310_normal_ESP8266_4M1M
ESP_Easy_mega-20200426_normal_ESP8266_4M1M
BACKGROUND:
I have a set of rules that are working fine with the 20200310 release. On System#boot it disables controller 1 and 2 then checks to see if a dummy device variable (control#coldboot) is a zero. (on a cold boot it will be 0 but if it is set to something, on a wake from deepsleep it will still hold the value it was set to). If it is a coldboot, it sets some values (including setting a value in control#coldboot so it won't do it when waking from sleep).
When WiFi#connect occurs, it grabs the first two octal's of the IP and compares them to '192.168' and compares %ip4% to the %unit% to decide which controller to activate. I have my router assign IP address based of the MAC address so %ip4% will be the same as the unit number I assign to the divide. This is done to run on my local network or at my daughter's using BeeBotte.
When MQTT#Connected occurs, if the email indicator is set, it turns it off and sends a mqtt msg to Node-RED which will send me an eMail with the IP address. It then published another message saying 'awake' and sets a timer for 10 seconds t allow devices to publish their readings.
Then I have some rules for turning on and off a gpio pin which causes a circuit - by dynamicdave - to turn off/on power to the I2C line for some sensors).
This all works great on 20200310.
THE PROBLEM
When I flash to ESP_Easy_mega-20200426_normal_ESP8266_4M1M and boot, it runs the first cycle and goes to sleep but when it wakes it just hangs.
I've narrowed it down (after beating my head against the wall for several days) to having a device for a BMx280 defined but not having it connected or not having power to the I2C line. It looks like it loops looking for the device. the log gets flooded with
Code: Select all
May 1 11:27:45 node28 EspEasy: BMx280 : Unable to detect chip ID
May 1 11:27:46 node28 EspEasy: BMx280 : Unable to detect chip ID
May 1 11:27:46 node28 EspEasy: BMx280 : Unable to detect chip ID
May 1 11:27:47 node28 EspEasy: BMx280 : Unable to detect chip ID
May 1 11:27:47 node28 EspEasy: BMx280 : Unable to detect chip ID
May 1 11:27:48 node28 EspEasy: BMx280 : Unable to detect chip ID
May 1 11:27:48 node28 EspEasy: BMx280 : Unable to detect chip ID
As I said, this was not an issue with 20200310 (which I have dropped my other devices back to)
If there is any other information I can provide, please let me know.