With OH3.1.0RC1 the shelly binding detects the shelly devices.
All properties are correct shown but none of the devices is coming online.
Firmware version shellyplug-s: 20210429-101611/v1.10.4-g3f94cd7
I assume below is the issue but don’t know how to fix it.
shellyplug-s-b50ad5: CoAP Exception
java.net.UnknownHostException: : Name or service not known
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:929) ~[?:?]
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1519) ~[?:?]
at java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:848) ~[?:?]
at java.net.InetAddress.getAllByName0(InetAddress.java:1509) ~[?:?]
at java.net.InetAddress.getAllByName(InetAddress.java:1368) ~[?:?]
at java.net.InetAddress.getAllByName(InetAddress.java:1302) ~[?:?]
at java.net.InetAddress.getByName(InetAddress.java:1252) ~[?:?]
at org.openhab.binding.shelly.internal.coap.ShellyCoapServer.start(ShellyCoapServer.java:86) ~[?:?]
at org.openhab.binding.shelly.internal.coap.ShellyCoapHandler.start(ShellyCoapHandler.java:131) ~[?:?]
at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.initializeThing(ShellyBaseHandler.java:296) ~[?:?]
at org.openhab.binding.shelly.internal.handler.ShellyBaseHandler.refreshStatus(ShellyBaseHandler.java:397) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:829) [?:?]
event.log file
2021-07-03 20:57:06.651 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘ShellyplugSB50Ad519216810013DeviceUptime’ changed from 1097 s to 1157 s
2021-07-03 20:58:06.734 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘ShellyplugSB50Ad519216810013DeviceUptime’ changed from 1157 s to 1217 s
2021-07-03 20:59:06.893 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘ShellyplugSB50Ad519216810013DeviceUptime’ changed from 1217 s to 1277 s
As far as I understand the error / exception message you shelly cannot be reached by it’s name:
Can you ping it in your network by using that name ( the name that is reported in the error message ) or do you use another name when you ping it ?
My initial answer was more referring to a setup by using a .thing file and configuring the thing by using the ip address which might have changed because of the DHCP lease time might have expired.
I would suspect a DNS problem here. It would match with the error message.
But your other screenshot shows the IP address that is being used in the UI.
What are the parameters that are used to start docker esp. with regard to network ?
Thanks. I did. Default port is 5683. If that is correct than this doesn’t solve the issue. I believe the issue more the from Openhab to the shelly device. I will Friday try to make a sniffer capture. Maybe that will give some details.
In case the problem is the file’s extension - rename it to e.g. .txt before uploading. Describe that in your message. In case the problem is the file size I would suggest to use a third party file hoster and just provide the link here.
only shelly.pcap.txt (4.5 KB)
I uploaded a capture file (remove .txt) from communication between OH 3.1.0 docker installation running on the Synology nas (ip .51) and a shelly device (ip .13). I see communication between the 2 points but also a message destination unreachable.
Also on the nas I’m running OH 2.5 as a native install (has the same ip address as the docker install; using same network) and tried to adopt the same shelly device. That is working fine.
Any idea how to get this docker install working?