HomeKit stopped working with new FritzBox 7530AX

Hello everyone,

I already spend a couple of days searching the community and google but could not really find a solution. I observe a really strange behavior of my HomeKit Add-on after I changed my router to a FritzBox 7530AX.

One of the most important features I used to use was the Push-Notification when a motion sensor was triggered. This is used to unlock the iPad which is quite cool.

After upgrading the FritzBox, I couldn’t even choose “Notification” at HomeKit for the motion sensor.
I did a lot around ClearPairings, delete Home, reboot all devices, clear cache on the iPhone and the iPad.

The bridge was found by HomeKit and could be installed, the Motion Sensor can be installed.
If I trigger the Motion Sensor manually (it’s just a Switch with HomeKit Metadata “Motion Sensor”) the App shows “Motion Detected”. But this works only for about a couple of seconds. Then, everything I do on the openhab end is well ignored. I can trigger a switch on the iPhone, this goes well into openhab and the connection is open again for a couple of seconds (for the motion sensor too).
Sometimes the changes from openhab are pushed to HomeKit after a minute or more (which doesn’t make sense for a motion sensor).

First I found an “Unknown User” Problem during pairing which I solved by changing the User at the HomeKit.json file manually.
I set the Log Level to TRACE and the logs seems quite free of errors:

I updated to Openhab 4.0.2 which didn’t solve the problem.

Next step was checking if openhab publishes it correctly, it seems to be ok:

(can be embedded in one of the next posts as I’m a new user)

Apart from the hostname which I guess the new FritzBox just added something to the hostname which annoys me (that “-fritz-box.local”) but doesn’t seem to be the problem.

Does anybody of you have experienced a similar problem?
I really think it is more the FritzBox causing trouble instead of openhab, but any idea?
This is really driving me crazy as all the logs tell me, that it is working but it is not :grinning:

THX
Jan

Hi!
I experienced also some issues when switching to my new FritzBox 7530AX. The issues I have are related to DNS resolution.
Openhab (4.0.3.-1) running on a raspberry pi was not reachable via the hostname even if the IP was still available. The connection via IP worked fine.
I haven’t worked this out finally but I thinks it’s somehow DNS related.
When trying to re-install I found the message in the logs that another mDNS stack is running.

Hello Friends,

No I’ve faced exactly the same issue.
Did you found any rootcause that is causing this issue?

/Franz

frsc@raspi:~ $ docker exec -it openhab3-openhab-1 bash
root@raspi:/openhab# ping raspi
PING raspi (127.0.1.1) 56(84) bytes of data.
64 bytes from raspi (127.0.1.1): icmp_seq=1 ttl=64 time=0.156 ms
64 bytes from raspi (127.0.1.1): icmp_seq=2 ttl=64 time=0.107 ms
^C
--- raspi ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1019ms
rtt min/avg/max/mdev = 0.107/0.131/0.156/0.024 ms
root@raspi:/openhab# ping raspi.fritz.box
PING raspi.fritz.box(raspi.fritz.box (2a00:1e:d300:4e01:dffa:ae93:5848:cc10)) 56 data bytes
64 bytes from raspi.fritz.box (2a00:1e:d300:4e01:dffa:ae93:5848:cc10): icmp_seq=1 ttl=64 time=0.112 ms
64 bytes from raspi.fritz.box (2a00:1e:d300:4e01:dffa:ae93:5848:cc10): icmp_seq=2 ttl=64 time=0.153 ms
64 bytes from raspi.fritz.box (2a00:1e:d300:4e01:dffa:ae93:5848:cc10): icmp_seq=3 ttl=64 time=0.145 ms
64 bytes from raspi.fritz.box (2a00:1e:d300:4e01:dffa:ae93:5848:cc10): icmp_seq=4 ttl=64 time=0.081 ms
^C
--- raspi.fritz.box ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 0.081/0.122/0.153/0.028 ms
root@raspi:/openhab# ping raspi.fritz.box
PING raspi.fritz.box (192.168.3.42) 56(84) bytes of data.
64 bytes from raspi-fritz-box.fritz.box (192.168.3.42): icmp_seq=1 ttl=64 time=0.127 ms
64 bytes from raspi-fritz-box.fritz.box (192.168.3.42): icmp_seq=2 ttl=64 time=0.102 ms
64 bytes from raspi-fritz-box.fritz.box (192.168.3.42): icmp_seq=3 ttl=64 time=0.089 ms
64 bytes from raspi-fritz-box.fritz.box (192.168.3.42): icmp_seq=4 ttl=64 time=0.086 ms
64 bytes from raspi-fritz-box.fritz.box (192.168.3.42): icmp_seq=5 ttl=64 time=0.088 ms

Hi Franz,

I was following the mDNS-route to solve the issue in the past but couldn’t fix it. Apart from that, it was bothering me, that Apple is updating too frequently and for me HomeKit was more down, than working. I was using the HomeKit Binding to unlock my screen via motion sensor only.
This can easily be fixed by using the openhab-app and a rule which sends a notification each time the motion sensor is triggered.
This did the trick to me :slight_smile:

Jan

Hi Jan,

Thanks for the research and for your Short Message here.
I was ableto fix It I’ve seen the Result today morning.
I‘m Running Open Hub in Docker I have a lot of Inter Faces. I had configured the Interface with with IP Specified In the Settings of the HomeKit Binding.

Now with the new Router, this exchanged the IP address that was assigned. As I set the old op on the routers Dhcp and waited one night its fine again.

ThX
/ Franz

1 Like