So today I perform my monthly W2k16 windows update which naturally created the need to reboot my system. I have not rebooted since adding the deConz….
When the Fire Daemon services started both deConz and HS3, upon going to the HS3 webpage, I noticed that deConz stole the port number - as I had configured HS3 with a delayed start. This presents a problem naturally. Saying that, I'd like to start the deConz on an alternate port within my service. From what I see, I can invoke deConz with as:
deCONZ --auto-connect=1 --dbg-error=1 --http-port=8090 --ws-port=20877 --upnp=0
When I start the deconz after HS3 starts it appears the webserver port is 8090 - perhaps it decides on the next available port. In the example above that I found on the web, I can only assume you can also specify the web server port - which in my case I wouldn't need if the port of 8090 is both the application/web server port. Assuming I don't need --ws if I specify 8090, do I need the other flags?
Robert
When the Fire Daemon services started both deConz and HS3, upon going to the HS3 webpage, I noticed that deConz stole the port number - as I had configured HS3 with a delayed start. This presents a problem naturally. Saying that, I'd like to start the deConz on an alternate port within my service. From what I see, I can invoke deConz with as:
deCONZ --auto-connect=1 --dbg-error=1 --http-port=8090 --ws-port=20877 --upnp=0
When I start the deconz after HS3 starts it appears the webserver port is 8090 - perhaps it decides on the next available port. In the example above that I found on the web, I can only assume you can also specify the web server port - which in my case I wouldn't need if the port of 8090 is both the application/web server port. Assuming I don't need --ws if I specify 8090, do I need the other flags?
Robert
Comment