Static Port for Browser app (Issue #2144)

[cagnulein]

Static Port for Browser app (Issue #2144)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[evan-kolberg]

I developed a workaround if someone would want to connect to the localhost websocket - Works on macOS, possibly Linux, and not Windows. Thanks to @cagnulein for helping me via email.

How I did this:

1. Launched QZ
2. Went to General UI Options in Settings
3. Scrolled down and clicked on OPEN FLOATING ON A BROWSER - whatever the heck that means
4. Inspected the page and went to Sources
5. Found the main_ws_manager.js and global.js files
6. Noticed that the localhost port changed each time the QZ app restarted
7. Since on macOS, ran lsof -iTCP -sTCP:LISTEN in Terminal.app
8. Saw that there were 4 options for ports and 1 of them was the socket port.
9. Translated the JavaScript code into Python
10. Implemented a function to find the websocket port from the parent process named qdomyoszw
11. Was able to successfully read data from the open websocket

How to run the code (if on macOS, maybe Linux):

1. Launch QZ
2. Git pull the repo (or add it as a submodule) and pip install the websocket library
3. Run main_macOS.py

Your output should look like this:

This doesn't directly give a static port for the browser app, but it offers a solution to those who want to connect to the localhost websocket.

I still don't know what the Server Port: 36866 option does under Experimental Features does. Is this for emitting Bluetooth signals with Mqtt or OSC? I don't know.

--
Evan

[cagnulein]

The server port is, if I remember correctly, for the templates done by @p3g4asus

[p3g4asus]

I had to review the code because I completely forgot it. However it is pretty simple. When a template is found, the settings are searched for the key "template_[templateId]_port". If it is found and it is not >0 and < 65535, that port number is used. If it is found and it is 0, the first time the template is started, the port is set randomly and saved in settings so that it will remain fixed for every next start. If it is not found, it is set to a default value that is 6666. So I think that if you delete that line of code for windows build, you will have QZ windows inner web server on port 6666.