-
-
Notifications
You must be signed in to change notification settings - Fork 260
Fix deCONZ websocket port prompt and default #2104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Markus Schraufstetter <[email protected]>
31813e8 to
393505b
Compare
|
I don't get it. The existing lines right before your new ones do exactly the same, don't they. Except for the port number. It's even documented in there. |
|
With the current setup, the deCONZ/Phoscon WebSocket interface does not work. The HTTP service is currently bound to the same port as the WebSocket interface. The WebSocket interface must run on an unused port. Therefore, two ports and two corresponding queries are required, not a single query with both services on the same port. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add unattended installation, too?
Add a parameter to build-image/openhabian.conf for the wsport and add calling deconz_setup from openhabian-setup.sh if that's set.
Add that param to the docs, too.
Signed-off-by: Markus Schraufstetter <[email protected]>
Signed-off-by: Markus Schraufstetter <[email protected]>
5f39f8d to
6c90f1c
Compare
…raspbee2/install#raspbian) Signed-off-by: Markus Schraufstetter <[email protected]>
Signed-off-by: Markus Schraufstetter <[email protected]>
Signed-off-by: Markus Schraufstetter <[email protected]>
Adds a dedicated websocket port prompt (default 8088) instead of reusing the HTTP port, keeping the HTTP behavior unchanged and avoiding double‑binding the same port which can cause issues.