Core: Future of Z-Wave

[balloob]

There has been a lot of awesome work been done lately on Z-Wave by @armills, @andrey-git and @turbokongen to ensure stability and reliability.

Based on #6813 and the recent addition of Z-Wave nodes, I think that we should talk about creating a shared vision on how our ultimate Z-Wave integration looks like. We can then start taking steps towards making that a reality.

Here are just some of my thoughts

• Full test coverage #6437 (almost there!)
• A dedicated Z-Wave panel in the frontend:
  
  
  
  • Call services to add/remove node or heal network (v1). We already have the services, just need buttons.
  
  
  • Show Open Z-Wave log (v1). We already have the log, just need an API call.
  
  
  • Explore current nodes and all their info (v2)
  
  
  • Configure nodes? (v3)
  
  
• What else?

[andrey-git]

• Nodes neighbour connectivity map

[tflack]

+1 on configuring nodes, especially performing associations between nodes. There are a lot of Z-wave switch controls (like the Aeotec 4 button) coming on the market and having to shut down home assistant to go launch and mess with ozwcp (and it's less than intuitive interface for associations) is a pain.

[ViperRNMC]

Hi Paulus, looks nice (goed werk!), like to see also a connectivity map with possibility to adjust neighbours.

[andrey-git]

@ViperRNMC I don't think neighbours are settable.

[turbokongen]

No, Neighbours are not settable. They are handled in the controller. Heal node or network is the best that can be done to fix neighbours. If it does not help, look at range, interferrence or faulty devices.

[turbokongen]

I would love to do the panel, but I have big issues with understanding the polymer coding part.

[raccettura]

I'd personally love to not have to shut HA and fire up ozwcp to edit parameters on devices or check their values. Integrating that into HA would make things much more usable "out of the box".

Also firmware updates for ZW+?

[turbokongen]

@raccettura OZW does not support OTA, so as long it doesn't, we can't either.

[andrey-git]

@raccettura Also note that there is already a {print,set}_config_parameter services.

[scadagenius]

1. Love to see configuration of Node/Device so don't have to shutdown HA.
2. Also real time activity when I am in that Zwave panel not sure that above mentioned item "Show Open Z-Wave log (v1). We already have the log, just need an API call." will cover this.
3. Some kind of trigger (state machine?) when any of the node is dead or come alive.
   Nice work guys!
   Thanks a lot.

[balloob]

@turbokongen I can help with a foundation of a panel. I also know that @andrey-git is getting pretty solid in Polymer so should be able to help.

[timcv]

I would love the possibility to set my names on the z-wave devices. I had to re include all my zwave devices the other day and it was a pain in the butt to search and replace all entity names.

The possibility to override the name from OZW from kitchen_lamp_3_4 to just kitchen lamp would help a lot.

[andrey-git]

Made a PR to address the last comment.

[riemers]

With the new hass release, you can click in the z-wave panel and say "stop z-wave network" then i made a custom toggle, that runs below script, which turns on ozwcp panel. Run the toggle again and it turns off and you can turn back hass zwave again. Might not be the end result but since i was configurating a bunch of settings this made my life a little easier. (works on the hassbian image)

#!/bin/bash

BIN_FOLDER=/srv/homeassistant/src/open-zwave-control-panel/
if [ -z $2 ]; then
        PORT=8888
else
        PORT=$2
fi

test -f ${BIN_FOLDER}ozwcp || exit 0
case "$1" in
    start)
            echo -n "Starting ozwcp"
            cd ${BIN_FOLDER}
            nohup ./ozwcp -p${PORT} > /dev/null 2>&1 &
            echo $! > ${BIN_FOLDER}ozwcp.pid
            echo ""
            ;;
     stop)
            echo -n "Stopping ozwcp"
            rm -f ${BIN_FOLDER}ozwcp.pid
            pkill ozwcp
            echo ""
            ;;
     toggle)
            if [ -f "${BIN_FOLDER}ozwcp.pid" ];then
                    rm -f ${BIN_FOLDER}ozwcp.pid
                    pkill ozwcp
                    echo "Stopped ozwcp (was running)"
                    echo ""
            else
                    cd ${BIN_FOLDER}
                    nohup ./ozwcp -p${PORT} > /dev/null 2>&1 &
                    echo $! > ${BIN_FOLDER}ozwcp.pid
                    echo "Started ozwcp (was stopped)"
                    echo ""
            fi
            ;;
        *)
            echo "Usage: ./ozwcp_toggle.sh start|stop|toggle <portnumber>"
            exit 1
            ;;
esac

[ziadsawalha]

Has there been any work or desire expressed for supporting multiple controllers? I have two zwave.me sticks and would like to have them both available in homeassistant.

[emlove]

@ziadsawalha I think the only big hurdle with multiple controllers would be the zwave services/API. We'd need a new parameter to the services that specify which network you want to control.

[andrey-git]

@ziadsawalha Any advantage to using 2 sticks at the same time (at the same place)? Why not use just one?

[ziadsawalha]

@andrey-git I'm using them to support devices on different frequencies (US and European devices).

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[balloobbot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍