-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
opening configuration window before starting a local or remote connection crashes ozw-admin #42
Comments
I found the core dump. Attached. Should it help:
|
Firstly - When connecting to the VNC interface, you should do a "Network" connection to localhost rather than trying to open the serial port. (Will look at removing/hiding the serial port option on the allinone in the future). ozwdaemon is also running, and it will be using the serial port - So nothing ever good will happen if ozw-admin is also trying to open the serial port. As for the config window crash - I'm working on that (opening it before opening a serial port or remote connection) - but for ozwdaemon - Any changes you want to make to how its running, should be via the Options.xml file in the User directory, or ozwdaemon.ini (for things as yet undocumented!) |
Ah, thanks. I guess I didn't understand the different parts of the system and that ozw-admin needs to connect to ozwdaemon. Sorry for that. |
Opening the Config window shouldn't crash now |
I'm trying to migrate away from Z-Wave integrated in HASS to qt-openzwave. I started container with these parameters:
docker run -it --restart always --name ozwdaemon --security-opt seccomp=unconfined --device=/dev/ttyAMAzwave -v /opt/ozw/config:/opt/ozw -e MQTT_SERVER="192.168.178.250" -e USB_PATH=/dev/ttyAMAzwave -p1983:1983 -p 5901:5901 -p7800:7800 openzwave/ozwdaemon:allinone-latest
The container starts and I can connect to port 7800 and start VNC.
Then as soon as I click on 'Configuration' from the File menu, the VNC connection is closed and I see that ozw-admin was terminated:
I can reproduce this over and over.
The same issue occurs when I click on 'Open', enter /dev/ttyAMAzwave as device and click on 'Start'. As soon as I click on Start, the VNC connection is closed and ozw-admin is terminated by SIGSEGV.
I created /opt/ozw/crashes and /opt/ozw/config/crashes but I see no core-dumps.
The same occurs when I manually start ozwadmin from within the container and specify a device:
Any ideas?
The text was updated successfully, but these errors were encountered: