this will mostly be a networking problem on the virtual switch of the VM host … also don’t understand some configuration here why people still use devices topology address is like working with channels instead of items … also my config is
Do not out set Network address of the local host ip address.
I just made a test on a debian running openhabian script with ooenhab 3.3 with the config trough UI listed above and the VM is running on xcp-ng and no disconnect.
I believe there was an update to hyper-v that broke some stuff try reverting to a previous update of the windows server to check
Well, i ment that the NICs should NOT be allowed to go to sleep Unfortunately, sometimes the drivers of te NICs do set this to allow, despite the fact that it is a server.
The HW is fine. Your problem might be related to the teaming though…I came across weird connection problems on windows server a couple of times, which had been related to NIC teaming. Never really figured out what the root cause was, but getting rid of the teaming solved the connection problems in all cases. Maybe you wanna give this a try, too.
Some update to Windows / Hyper-V definitely broke something.
I ran Home Assistant (yes, HA, not OpenHAB) with a KNX integration flawlessly for 2 years, on a Hyper-V VM running in Windows Server, with I350 NIC.
Then, about 2 months ago, without me changing anything in the systems, I started getting those “Connection Closed” notices and all KNX switches became unresponsive.
If I do a clean install of HA+KNX to a new Hyper-V virtual machine, it still doesn’t work (Connection Closed).
If I restore my existing HA+KNX configuration to a VMWare VM, or RPI… it works.
So, here we have 2 cases where HyperV + KNX stopped working all of the sudden. One running in OpenHAB, the other in Home Assistant.
I tried changing all settings in the Network Adapter, but didn’t get it to work.
Think I’ll try a different NIC.
Did you manage to get your KNX integration to work again?