Closed jnssnmrcs closed 1 year ago
No it wouldn't. The websocket port is actually reported by the deCONZ API - no need to configure it manually.
hm my bad, I missed the env vars to control which port deconz uses for websocket, having some issues getting it to work though, but that's outside the scope of this plugin. Thanks, closing.
Would be great if you could add support for setting a web socket port other than the default 443. I'm running deconz in a docker image and is binding it to a different port.