firmware changes

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
dr.zorg82
Normal user
Posts: 81
Joined: 02 Feb 2023, 07:32
Location: russia

firmware changes

#1 Post by dr.zorg82 » 02 Jun 2023, 15:22

Good afternoon. used normal Build20230409_20230531075113 there was a sensor ds18b20, but there was a problem with wifi. after two or three days of work, wi-fi was disconnected and the module had to be rebooted. I thought it was the firmware and decided to change . because on another module I use Build: ESP_Easy_mega_20230409_neopixel_ESP32_4M316k Apr 9 2023, then I decided to put a neopixel. but in firmware ESP_Easy_mega_20230508_neopixel_ESP32_4M316k.factory no sensor ds18b20 :( Can I add this sensor myself? or is it better to set the climate and not fool my head?
by the way in Build: ESP_Easy_mega_20230508_climate_ESP32_4M316k May 8 2023 also no sensor ds18b20 :shock: Why?
2023-06-02_16h35_49.png
2023-06-02_16h35_49.png (26.2 KiB) Viewed 959 times

User avatar
Ath
Normal user
Posts: 3386
Joined: 10 Jun 2018, 12:06
Location: NL

Re: firmware changes

#2 Post by Ath » 02 Jun 2023, 16:27

The DS18B20 plugin has been renamed to '1-Wire Temperature', as it supports more types of the 1-wire sensor than just the DS18B20.
/Ton (PayPal.me)

TD-er
Core team member
Posts: 8607
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: firmware changes

#3 Post by TD-er » 02 Jun 2023, 19:46

About the "lost connection"....
What is happening? Does ESPEasy have issues resolving some DNS name?
If so.... please have a look at the latest test build: https://td-er.nl/ESPEasy/latest/
As I did fix this issue last night, where one of the DNS server records may get corrupted.

What happened is that some IPv6 routing advertisement packet is picked up by LWIP in the ESP32 core libraries and the first 32 bits of this is then set as DNS server.
So when you need to resolve some DNS entry (e.g. to connect to a host by the controller) the ESP may timeout and all kinds of strange things may happen.

dr.zorg82
Normal user
Posts: 81
Joined: 02 Feb 2023, 07:32
Location: russia

Re: firmware changes

#4 Post by dr.zorg82 » 03 Jun 2023, 09:25

TD-er wrote: 02 Jun 2023, 19:46 What is happening? Does ESPEasy have issues resolving some DNS name?
I do not quite understand what you said, but my settings are as follows
2023-06-03_10h21_11.png
2023-06-03_10h21_11.png (33.14 KiB) Viewed 913 times
Ath wrote: 02 Jun 2023, 16:27 has been renamed to '1-Wire Temperature',
thank you

TD-er
Core team member
Posts: 8607
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: firmware changes

#5 Post by TD-er » 03 Jun 2023, 12:27

Based on your settings, you should see only 1 DNS entry on the sysinfo page (the other one being 0.0.0.0 or "::")
What may happen sometimes is that the 2nd DNS server entry on the sysinfo page shows some seemingly random IP.

These DNS settings are needed to convert a "hostname" to an IP so you can reach a server.

for example "espeasy.com" would resolve to 194.50.163.231
However if this setting gets corrupted, the ESP may take forever to convert such a hostname to an IP.

So if you happen to use a hostname somewhere and this setting gets corrupted, ESPEasy may appear unreachable.
For example NTP (to get the time synced) is by default using a hostname.
But you may also use a hostname in controllers or when calling SendToHTTP in rules.

dr.zorg82
Normal user
Posts: 81
Joined: 02 Feb 2023, 07:32
Location: russia

Re: firmware changes

#6 Post by dr.zorg82 » 03 Jun 2023, 13:03

TD-er wrote: 03 Jun 2023, 12:27 you should see only 1 DNS entry on the sysinfo page (the
now I have
2023-06-03_13h57_33.png
2023-06-03_13h57_33.png (13.41 KiB) Viewed 905 times
. and at the moment everything is working (Build: ESP_Easy_mega_20230409_neopixel_ESP32_4M316k Apr 9 2023)
but on the other firmware the settings were the same, but after a couple of days the module losted connecting to Wi-Fi and only rebooting the module helped
but now it works and I'm happy with it. Thank you

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 2 guests