Add-on problem

[cgarwood]

Add-on problem

[isabellaalstrom]

Maybe I should try to reset everything. I am in a good place for testing since there's nothing running in production on this yet. I'm only just starting out with Home Assistant at my workplace :)

[Fishwaldo]

I just pushed a fix for OpenZWave that was causing crashes. Docker Images are rebuilding and should be available in a few hours. Try again then.

[marcelveldt]

Have you spotted the add-on settings and in particular the path to the Z-wave device.
It's not (yet) auto detected so you will have to fill in the path to the serial device.

BTW: It looks like OZWAdmin is causing the error. I will remove that from the image for the time being as that component is really in early stage. It's a management console to directly manage advanced properties of your Z-Wave mesh and controllers.

We can set-up an additional add-on just for testing the OZWAdmin once it's more usable.

[isabellaalstrom]

I will try it tomorrow as soon as I get to work (it's on our office hass) and get back to you.

[Fishwaldo]

Yes. Hopefully

[marcelveldt]

I just pushed a fix for OpenZWave that was causing crashes. Docker Images are rebuilding and should be available in a few hours. Try again then.

Will the Hassio daemon add-on be updated with this new image?

Yes, a new version of the daemon add-on is now published (1.0.10)

[daanvb]

Exact same thing happening to me

[marcelveldt]

@isabellaalstrom and @daanvb the new version is up on the repo. Can you give it another try ?

[daanvb]

Have you spotted the add-on settings and in particular the path to the Z-wave device.
It's not (yet) auto detected so you will have to fill in the path to the serial device.

@isabellaalstrom and @daanvb the new version is up on the repo. Can you give it another try ?

Yeah I spotted that. My Zwave is at \dev\ttyACM1

I too will give it another go tomorrow. Bit zwave'd out for today! Do i just reinstall v0.0.3 via HACS?

[marcelveldt]

Have you spotted the add-on settings and in particular the path to the Z-wave device.
It's not (yet) auto detected so you will have to fill in the path to the serial device.
@isabellaalstrom and @daanvb the new version is up on the repo. Can you give it another try ?

Yeah I spotted that. My Zwave is at \dev\ttyACM1

I too will give it another go tomorrow. Bit zwave'd out for today! Do i just reinstall v0.0.3 via HACS?

I've updated the add-on (hassio/supervisor)

[balloob]

Reminder: Go to Supervisor UI -> System and click on Hardware info to see the path of your Z-Wave stick. (is this in the docs yet?)

[isabellaalstrom]

Add-on now starting up fine! I'm not really sure how to proceed with testing though, is everything done by calling services?

[daanvb]

Working here too, thanks. All devices and most entities discovered. Missing the motion sensor on one of my sensors for some reason.

Guessing there is no control panel yet?

[marcelveldt]

Control panel is not yet there. You can do the commands manually by using the services or even directly on the MQTT bus. What commands/configuration do you need most ?

[marcelveldt]

Working here too, thanks. All devices and most entities discovered. Missing the motion sensor on one of my sensors for some reason.

The initial scan takes a very long time because all battery nodes need to be awake once to discover their info. This is just only the first time only. In my own situation I got tired of waiting and woke up each pir sensor myself by pressing the button.

[daanvb]

I don't think it is anything to do with this addon why it is missing. All my devices are connected to mains power. My zwave has always been a bit flakey. I have been using zwave2mqtt addon and then trying to use ozwcp to configure but i have been finding that some settings such as offsets, reporting and motion detection time weren't being stored....I think the whole system needs a full factory reset and to start again....

Ah yeah I have found the services, just seen the set_parameter_config....

if i wanted to try and set a temperature offset on my Aoetec MultiSensor 6
would i call the service like this

node_id: 21
parameter: 201 #201 being the temperature calibration parameter from specs
value: -15

[isabellaalstrom]

Managed to add a node now and something showed up in home assistant, but the add-on keeps giving me this:

2020-02-06 11:22:18,368 INFO exited: ozwdaemon (exit status 255; not expected)
2020-02-06 11:22:19,378 INFO spawned: 'ozwdaemon' with pid 104
2020-02-06 11:22:20,895 INFO success: ozwdaemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-06 11:22:41,316 INFO exited: ozwdaemon (exit status 255; not expected)
2020-02-06 11:22:41,322 INFO spawned: 'ozwdaemon' with pid 109
2020-02-06 11:22:42,820 INFO success: ozwdaemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-02-06 11:23:03,254 INFO exited: ozwdaemon (exit status 255; not expected)
2020-02-06 11:23:03,260 INFO spawned: 'ozwdaemon' with pid 114
2020-02-06 11:23:04,757 INFO success: ozwdaemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

[marcelveldt]

I just pushed a fix for OpenZWave that was causing crashes. Docker Images are rebuilding and should be available in a few hours. Try again then.

Great news! Will this also fix the crash with the set value on a newly added dimmer ?

[daanvb]

I just pushed a fix for OpenZWave that was causing crashes. Docker Images are rebuilding and should be available in a few hours. Try again then.

Will the Hassio daemon add-on be updated with this new image?

[balloob]

Alright, closing this issue. Please open a new one if you see more problems 👍