Notification missing and NTP doesn't work

[interrupteur]

Firmware
Build: 20111 - Mega
System Libraries: ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support
Build Time: Nov 30 2020 00:29:45
Binary Filename: ESP_Easy_mega_20201130_hard_SONOFF_POW_4M1M

Sonoff : Pow R1

---------------------------------------

Hi,

I have 2 problems...

1) NOTIFICATIONS

the Notifications page is missing, as you can see in the picture... Is there a way to add it without to update a new firmware please ?

pow1.png (9.46 KiB) Viewed 7289 times

2) NTP

The NTP doesn't not work (see the second picture) ====> Local Time: 1970-01-02 01:34:41
I put my local NTP server and the time is always the same (1970)...

pow2.png (5.94 KiB) Viewed 7289 times

I have others Sonoff (TH1) and i have no problem: the local time is OK...

pow3.png (7.33 KiB) Viewed 7289 times

What's the problem ?


Thanks a lot for your help

Inter-Rupteur

[TD-er]

Regarding NTP.
If you enable NTP without adding any hostname or IP, the NTP lookup is taking one from the random pool.ntp.org.
However your device does need 2 things for this to work:
- Access to the internet (thus the gateway must be known and working)
- Access to a DNS server (to resolve pool.ntp.org, which returns always a different IP)

If you setup your own router to reply on NTP requests, then your router must of course be set to do so.
And you must make sure only to enter an IP address (not something including something like http://<ip>/)


Regarding the notifications.
Of they don't show up in your web interface, the notifications are not included and I will look into why not as there is no reason why they should not be there on the 4M POW build.
Sadly that means you need to update to a newer build when it is included, but the good part is that the 4M POW can be upgraded via the web interface, so you don't need to dismantle it for an update.

[interrupteur]

Hi TD-er,

thanks for your reply.

1) For the NTP
I have setup a NTP server (router) and i have no problem with others sonoff (10 Sonoff th10 and 5 Sonoff Basic) : As you see in the third picture. I applied the same configuration to the 2 Sonoff Pow but they doesn't work. I just put the IP like you said (and not the http:....). The 2 give me 1970....

2) For Notifications
hum... I must wait so.. OK

Thanks
Inter-Rupteur

[TD-er]

Nr 2 has already been implemented in the mega branch, so for the next build the notifiers will be included in the POW 4M builds

[interrupteur]

Perfect !!

and for N°1, what can i do now ?

[TD-er]

Can you show the network config from the sysinfo page?
And what IP is your router/gateway at?
What do you use as NTP configured host? (you can leave it empty to use the pool.ntp.org)

[interrupteur]

Hi TD-er,

this is the config of the module :

network.png (50.67 KiB) Viewed 7164 times

this is the config of the NTP Host (esp) :

NTP.png (4.15 KiB) Viewed 7164 times

this is the config of the local DNS server :

DNS.png (9.78 KiB) Viewed 7164 times

The configuration of the router :

The router is NTP client and server. NTP Client with pool.ntp.org. Enable the NTP server role for all my local lan and create a rule to pass the NTP trafic for lan.

[TD-er]

Your DNS is not in the same subnet as the rest of your network.
Not saying it is impossible like this, but to me it looks highly unlikely this is correct.

The IP configuration appears to be delivered via DHCP, but it all looks a bit strange.
Just like you have at least 3 subnets in your network:

- 192.168.5.x for DNS
- 192.168.100.x for your ESP device, with its own gateway (layer 3 switch maybe?)
- 192.168.110.x for your PC you're working with.

Also you do use a .local hostname for your NTP server.
Please don't use .local mDNS like hostnames when testing these kind of DNS resolve issues.
And make sure your routing in your network allows you to reach 192.168.5.x from 192.168.100.x and of course the return path.
The subnets look like they are a /24 network, so to reach other subnets you really must have some kind of layer-3 routing switch or use your main router for the traffic between subnets.
So I guess in there is probably your problem.

Steps:
- First try without setting a hostname for NTP, to make sure the ESP can resolve the pool.ntp.org hosts (and reach the DNS server)
- Use IP address for the NTP server you try to reach, also to make sure traffic can be exchanged between the subnets and it isn't a DNS issue as mDNS is not using the main DNS but broadcasts among other hosts in your network.

[interrupteur]

Hi TD-er,

it's not a problem that the DNS server is not in the same subnet. All my network are made in vlan mode. The router is a Layer-3, the routing is enable and certains networks can reach other network (in function of needs => rules created to passe certains flows). My DHCP server deliver IPs (differents vlans) only to certains networks (those who have a lot of devices...).

After a lot of testing (with / without ntp.pool.org, local DNS name, IP only..) i found the problem : The configuration was not the problem and was OK. It was at the level of "Timezone Offset" with 5 more min ... And i didn't see it because i was looking of the problem of NTP it self....

Thanks a lot for your help and availability.
Now i wait for the notification...


Inter-Rupteur

[TD-er]

Thanks for the update