-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Knx crash issues of IP interface #24492
Comments
Hey there @Julius2342, mind taking a look at this issue as its been labeled with a integration ( This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people. |
Is your knx component working for a while and then loosing its connection or does this occur immediately at start of HA? Does this happen at fixed intervals? How do you connect to your knx interface? What device are you using? Wlan or cable? Are the ip addresses fixed (local and interface)? 🤔 the last change to the knx component was in 0.90 so I don't know what causes the homekit sensors behaving diffrently on 0.94 and 0.93 . Maybe have a look at this issue: XKNX/xknx#194 |
@farmio thanks for your reply. The KNX IP/interface working for about 8hours or 20 hours when I set the rate_limit to 6. and then I tried the 2 but it still crash within 24 hours. But I found a phenomenon that when I restart the KNX ip/interface (WEINZIERL Interface 731), it showed me a lot of error (the flash and red indicator), about 1 minute later, it working normally. if I reboot the Hass.io, there is the same.
So, I think the KNX/IP router will be working well with Hass.io and I bought a Gira IP router Gira 216700 and it is on its way. Before I replace the IP interface, I add the fire_event to the config file as bellowing
The first time, the ip interface worked about 24 hours and then crash. I reboot the interface again and set the rate_limit from 2 to 5. and now, it works about 4 days without crash till now. As you can seen, there is not the fixed interval whereas I always can see the error indicator when 731 power on. I connected the devices all by "NETGEAR SOHO GS324 24-Port Gigabit Unmanaged Switch" with wired cables and fixed ip address by router (Ubiquiti EdgeRouter ER-X Advanced Gigabit Router ) or by ETS setting such as Knx/ip interface IP address setting. but all the Mac addresses are managing by router and I check them again without conflict. All the others networking devices are working well, I tried to plug-off the RJ45 from the KNX/IP interface and Plug-in again but the problem cannot be solved. the only way that I re-power on the KNX/IP interface. (at the same time, I do not need to touch Hass.io @ Raspberry 3, it can restore working well after the KNX/IP interface reboot) about the humidity sensor, I will try it later with your advice because I want to have a look that how long the ip/interface can work for before next Monday(1-July) |
I use Gira 216700 myself and it works flawlessly. I have not set a rate limit (default is 20) and I don't think values as low as 2 (2 telegrams per second) will work properly. (If you really have to lower it, I'd try something like 15 but I doubt it's necessary.) Does the Weinzierl provide any logs? Maybe they run a webserver like the Gira devices. Try navigating to http://192.168.1.234 and see if you find something. fire_event only affects how received telegrams are forwarded internally. It should not affect the connection. The humidity sensor device_class will work with the next version of the knx component (it was released yesterday and will come to HA in a couple of weeks I think). |
Are you apply the filter when you use Gira 216700? I bought it just want to setup the filter for both sides. the reason why I set the rate limit so law is that I once to control a Siri voice command to turn on and 5 seconds later turn off all the lights (about 40 lights) and the KNX/IP interface crashed immediately. I also test the normal KNX switches after that, they were working well. after I rebooted the KNX/IP interface, everything came back in HA and HomeKit. Regarding to the Weinzierl 731, I only can test it on next Monday. So, I also will remove the fire_event configuration on that day. And I can confirm there are only HA and ETS connect to the KNX/IP interface. Thanks for your help! |
Do you mean Group Address filter tables for different KNX lines/areas? Then yes I do use it but it works just as well without. You could use a scene instead of triggering 40 lights successively - this would lower your bus load. |
Yes, I just mean Group Address filter. And I will continue to optimize the configuration next week. BTW, could you add a KNX heartbeat function in the KNX component in the future, and then, create a heartbeat sensor in HA can easily to identify the communication situation between HA and KNX system. |
You won't need this once you have a stable interface 😉 |
Hi, today I replace the IP interface to Gira 216700 router. But it cannot run with routing or tunneling, can you do me a favours to give me your config? I already removed the secure setting for this router and the ETS function is working well. Thanks! |
My config won't be of any help as my ip-addresses will be different. Are there any errors in the home-assistant log? |
after setting only with "knx:", the log as following for your reference
|
Something seems very odd here. If this is no option you could try to add
to your configuration and post the logs again. |
I only can do the operation remotely at midnight.:-)
|
Please do, the logs don't reveal any more information except that both interfaces are found. If you want to strictly connect to one of them you can add
(You could omit the This could be related to XKNX/xknx#76 |
my original setting was above and it wasn't working with Gira216700 but 731 is working. The logs are following after I change the setting what you recommended.
|
Well, that's essentially the same as above. |
Yes. and I will try to capture the network package next Monday. Thanks! |
Hi, I got the packet capture file and the log files of Gira 216700 for your reference, thanks for your help. |
I couldn't find any packets from '192.168.1.229' to '192.168.1.238' or vice versa in your capture. |
I retry it twice in this morning and capture the packets during the Hass reboot. I hope it can be help. thanks again! |
I never used a device with knx-secure so I can't say anything about it. |
so, I need to disable all the secure setting in this case. And I just run the wireshark in a 3rd laptop. do you mean that I need to run it in Raspberry which running Hassio? |
Yes this would be one option. You could also mirror the port the Raspberry is plugged in. You can use this to run a simple test. Just adapt the |
Hi Farmio, And I try to install webSSH in HassIO first and run the code reference from "https://community.home-assistant.io/t/is-there-a-tcpdump-addon-for-hassio/44847" as following: Step1: install the tcpdump at webssh Step 3: Restart the Home assistant services Step 4: after the service restarted, use "Ctrl+C" to stop capture Step 5: copy/download the file from Hassio If my above steps were wrong, I only can do it tomorrow again, and I hope this time can provide the useful information, thanks. |
For solving the |
does the capture file helpful? |
So your status code is: E_CONNECTION_TYPE - The KNXnet/IP server device does not support the requested connection type (0x22) Request:
Response:
I would never have guessed that. It should provide 4 concurrent tunneling connections. Mine does, but I have an earlier revision (without knx secure support). |
I updated the firmware by GPA software from Gira and I can downgrade the firmware tomorrow to 3.x version.(Now is 4.0.x version). So, I will like to have your Gira IP router firmware version and I try to set to same for testing; and second, I will recommend you can add a password function in KNX component for the secure connection. nowadays, ABB Knx IP router also need to set a secure connection. |
Mine has 4.0.435 |
After you helped me to analysed the packets, I guess the problem is on Gira 216700 itself. So I took a lot testing which focus on it. I used the same version with ETS 5.7 and it can be working well after I reset the Gira 216700. the detail operating records as following. And I found out that I must dis-activated all the secure setting of Gira 216700 in ETS first and reset the Gira 216700 by GPA SW, and then, I download the data via USB-Knx dongel. secondly, only set the after reboot the Hassio, it is working. At this moment, I did not use the filter table in the Knx ip router and it looks working well with huge control command such as all lights turn on or turn off by Hassio.group. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Home Assistant release with the issue:
Last working Home Assistant release (if known):
Hass.io V0.94.2
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.ioComponent/platform:
https://www.home-assistant.io/components/knx/
Description of problem:
There are 3 issues about the KNX component:
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: