UDP is a connectionless protocol, this ist the reason why you don’t see LISTEN state.
BTW: use “ss” command instead of netstat from net-tools. netstat is deprecated.
“ss” shows for UDP UCONN or ESTAB.
See my (working CoIoT) setup output:
You can also trace the network traffic with tcpdump on OH host if there are incoming Coap packets: tcpdump host <Shelly Device IP> and port 5683 -n -vv -X
Thanks for your explanations @igi and @atetzner .
tcpdump confirms receipt of UDP packages from the Shelly1 appx. every 15 seconds. When ringing the bell connected to my Shelly1 I even see more UDP packets flowing. So its not network or service.
Thanks for your help on this.
I can’t use matching binding (the one installed through Paper UI) because in that case I can’t switch between color and white modes.
I haven’t mention my use case earlier, so it might explain why I need it. When Plex is playing movie/TV show, mode is switched to color and color of the bulb matches dominant color of the Plex poster. When Plex is paused or stopped it switches to white light and predefined intensity.
It was mentioned that Shelly introduced a counter which is not reset with a powercycle but can be reset via API. Apparently this happened at some point because the API documentation has a reset_totals parameter. https://shelly-api-docs.shelly.cloud/gen1/#shelly-3em-emeter-index
But in my binding documentation for 3.4.1 I don’t find any trace of support for the reset action.
Is it just missing from the binding?
Anybody would be able to extend the binding for that action?
How does the Shelly manager decide whether to show devices or not?
I have 6 Shellys that were set up via text files and also work. When the manager is opened it says there are 6 devices but only shows 3.
Openhab 3.4.1 is currently running, but the error has been there for a long time, I think since 3.2.
The device filter is set to all. I have 2 Shelly EM with the same configuration. One is displayed (is the first entry without a name) and the other is not.
So the name displayed in the Shelly Manager is not the Shelly label but its network address and when I display the menu, the name is empty. But it shows up in the GUI.
I had never given my Shellys a name in the device. Now I’ve done it and the Shelly manager is working again. Interesting that it worked without it until now.
Thank you
Quite useful: if you add new devices the binding uses the device name for the thing’s name.
Especially if you are using the dev binding from time to time you need to delete and re-add all things. By setting the device name in the device this task is done within a couple of seconds
This is not the reason. I have three shelly-plug-s which don’t even have the option to set a device name, but showing up with their network name in shelly manager. Might be that setting the device name just triggered a network announcement on the shelly devices which was then cought by the binding and shelly manager, finally resulting in showing up.