Nanoleaf binding may fail when upgrading to the latest Nanoleaf firmware because of IPV6

I noticed lately that after upgrading some of my panels to firmware 8.5.2 the started to go offline and online. After some investigation I was able to track down the issue as the devices are discovered as IPV6 devices which then cannot be used correctly within the binding to run the API requests to the devices.

For the time being I therefore recommend, if this is an option for you, to disable IPV6 on the openhab server. For example this can be achieved on openhabian with the following

Issue the command

sudo nano /etc/sysctl.conf

Add the following at the bottom of the file:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

then reboot.

If there is any binding developer out there who discovered a similar problem at

MyService implements MDNSDiscoveryParticipant

public @Nullable DiscoveryResult createResult(ServiceInfo service) {
        final ThingUID uid = getThingUID(service);
        if (uid == null) {
            return null;
        final Map<String, Object> properties = new HashMap<>(2);
        String host = service.getHostAddresses()[0];

which receives an IPV6 address and how I can avoid the registering an IPV6 device or call a request based on an IPV6 address which fails with org.eclipse.jetty.client.newRequest when using a URI like “http://[fe80:0:0:0:255:daff:fe5d:99c]:16021/api/v1/G0NHMoU7vTvcVCMe6H3bvZzKikv74dAz/”

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.