NielsPiersma

I would like to report that I have got the same issues. Our policy doesn't allow using public NTP servers for time resolving, so our DHCP scope assigns internal NTP...

Well, removing the ntp settings from the DHCP pool did not work as expected. Running backlog ntpserver1 0; ntpserver2 0; ntpserver3 0 did not result in a "default" list of...

> `backlog ntpserver1 0; ntpserver2 0; ntpserver3 0backlog ntpserver1 0; ntpserver2 0; ntpserver3 0` will not work. Tasmota do not accept NTP settings from DHCP While this feature had been...

For testing purposes, I am going to do the following. -- assign fixed IP -- assign static NTP servers See if that does something. --> Yes, on the failing Tasmos...

Sorry Clarification Problem is gone (for all tasmos) when using fixed up addresses Problems surfaces on 'some ' tasmos when set to DHCP . Have not figured out the root...

I've updated the Tamos (NOUS A1 devices) to 12.0.2.4 (sensors) and assigned DHCP addresses by issuing backlog ipaddress1 0.0.0.0; restart 1 I will let you know if there is any...

I would also opt for adding the AQC113C driver. Now running awsome Z690 AORUS XTREME (rev. 1.0) https://www.gigabyte.com/Motherboard/Z690-AORUS-XTREME-rev-10#kf which include both a 2.5GB Intel nic (commit supported driver) and a...

> Hello, do you have PowerSave 1 (enabled low power mode)? No, I've not enabled PowerSave 1, tried explicitly with "PowerSave 0", but to no avail. It instantly reboots when...