[Confirmed not fully functional]Network binding 2.4 does not work

Thanks, I learned something. I had a bunch of orphaned config files and files with old information in it that caused a lot of startup errors. For the first time in 2 years my startup is perfectly clean with no errors!

I’ll retry configuring network things via file to see if that is fixed later.

Same for me: clean new OH2.4 install on a brand new Windows 10 PC, ICMP ports open in firewall, created network.cfg and deleted network.config but nothing is discovered by the binding whereas it works like a charm in OH2.3.

Adding things manually works: they are pinged and channel are updated properly.

Network discovery is not working in OH 2.4. It might come back in a later OH 2.5 snapshot though.

2 Likes

ah ok, nice to know. :slight_smile:

I switched my router for a simple hub and could not understand why devices were not discovered anymore. Glad to see it is by design. I hope the feature comes back, just have to add the devices manually until then.

1 Like
Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "arping" (in directory "."): error=2, No such file or directory)

Arping installed. Binding stopped working after updating to 2.4.

You need to set the full path to your arping install.

If somebody willing to test, have a look here:

Network binding

Thank you, I do have full path specified. I’ll do debug.