Pi Hole with Sonoff wifi door sensor DW2-Wi-Fi – Wireless Door/Window Sensor not working with Pi-Hole

Help
1

Hello Team ,
Currently i installed the Pi-Hole on raspberry pi 4
i am using it for the DHCP - Mac address reservation for the AC controllers ,
but when the pi-hole is working the sonoff wifi door sensors goes to offline state
so i checked with the support the following

The initial setup works fine:

Sonoff DW2 → UniFi Access Point → Switch → ISP Router → Internet
However, after introducing a separate DHCP and DNS server via pi-hole (no ad blocker lists is used in this setup ), the issue arises. The updated flow is:

Sonoff DW2 → UniFi Access Point → Switch (DHCP & DNS Server - Pi-Hole) → ISP Router → Internet

In this configuration, the DW2 device goes offline. Upon investigation, it seems that the Pi-Hole DHCP and DNS server might be blocking communication, possibly due to missing or incorrect parameters.

i recently checked with this article

unfortunately it was not resolved so i checked with the sonoff support and got the following :slight_smile:

the DW2 WIFI, The device's wireless transmission is working IEEE 802.11b 2.4GHz,

so is there any way that this might be relevant with pi-hole
because i know for sure that the issue now in the pi-hole .

2

If you point one or more of them back to the pihole you could run the command below and see if the DHCP messages shed some light.

zgrep -n dnsmasq-dhcp /var/log/pihole.log*

Running 802.11b would be important for the access point but not your pihole.

You will likely want to runt a debug log ( tools > debug log ) and post the token for devs to look at as well.

3

i checked through the logs ,
230638:Oct 7 12:03:04 dnsmasq-dhcp[892103]: DHCPREQUEST(eth0) 192.168.1.204 d0:27:03:82:6e:50
230639:Oct 7 12:03:04 dnsmasq-dhcp[892103]: DHCPACK(eth0) 192.168.1.204 d0:27:03:82:6e:50

and it is registering , but till now it didn't connect ,
also when i checked the debug logs , i was not able to find an error indicating this mac address or any issues in it ,

if you have a way to increase the level of debugs or a way i can investigate more in it please let me know

4

So is the 192.168.1.204 your sonoff device your testing? Can you ping the IP address from another device?

If you can than perhaps this is an issue with mDNS? My network is quite small and I don't use it really but I am finding some posts on reddit talking about how some of the sonoff devices will not work with out mDNS. Moving DHCP from the router to the Pihole I would image impacts that? Perhaps someone with more knowledge of it could chime in on that.

5

Hello
the issue will be resolved if i moved the DHCP to the router
but the issue is that the router has a limited slots for dhcp mac reservation , this is why i created the pi-hole to fix that

so i was checking even in the Home assistant for option to enable the connection locally , but it seems that it is not working also ,
i found in the logs

"errors": [
{
"name": "custom_components.sonoff.core.ewelink.cloud",
"message": [
"Cloud ERROR: {'error': 504, 'reason': 'Request Timeout', 'deviceid':

so i am now sure that there is something missing or additional config that needs to be added to the pi-hole to make this device work

so do you have any suggestions that might help , log , or anything :smiley:

6

As I mentioned. What info I find on the internet suggests that this could be an mDNS issue. mDNS runs parallel to DNS and perhaps moving DHCP from the Router to the Pihole impacts that in someway. Avahi is the mDNS server for linux. Does the machine your running pihole on have avahi installed?