updated to the latest version and somehow I cannot acces my KNX config anymore..
When I want to open de KNX settings from the main settings screen, when I click on it, it jumps to my main screen/dashboard.
can’t seem to find any reference of KNX in the logs..
Even when booted in safe mode knx isn’t working
Hi 
!
Make sure the integration is actually loaded. If it loads, it should write at least some log that it was…
Also try to clear your browser cache and see if there are any logs in your browser console.
so I went into the YAML config check and when clicking on KNX it throws me a ’ KNX integration not loaded’ ..
now should this be ‘not loaded’ due to the fact that I am in safe mode or should this load in safe mode?
im going to check the logs now.
Logs don’t really give a more clear information:
Logger: homeassistant.components.websocket_api.http.connection
Bron: components/websocket_api/commands.py:336
Integratie: Home Assistant WebSocket API (documentatie, problemen)
Eerst voorgekomen: 10:36:31 (5 gebeurtenissen)
Laatst gelogd: 11:01:17
[545935792400] Error during service call to knx.reload: KNX integration is not loaded
[545937694224] Error during service call to knx.reload: KNX integration is not loaded
as I am not home at the moment I cannot check whether my ip interface is actually still online.
when running a terminal from HA and sending a ping to the ip interface I don’t get a response… weird thing is that it just stopped working last Friday night at 21:00.. while nobody was home..
so I think there is a other problem… running a ping from a different network device and gives me this result. I guess it has to wait until I get home.. 
PING 192.168.188.15 (192.168.188.15) 56(84) bytes of data.
From 192.168.188.21 icmp_seq=1 Destination Host Unreachable
From 192.168.188.21 icmp_seq=2 Destination Host Unreachable
From 192.168.188.21 icmp_seq=3 Destination Host Unreachable
From 192.168.188.21 icmp_seq=4 Destination Host Unreachable
— 192.168.188.15 ping statistics —
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3ms
pipe 4
Safe mode doesn’t affect the Knx integration since it isn’t a custom component but a core integration.
So should be loaded in safe mode.