ZWave network visualization card (for OpenZWave beta and ZWave2MQTT)

[abmantis]

EDIT (26 Dec 2020): Now also works for ZWave2MQTT!

Hey!

Since I was using the great ZHA Network Visualization Card for Zigbee, and I’m helping a friend setting up his new ZWave network, I decided to adapt it for the new OpenZWave and ZWave2MQTT integrations. You can find it here:

abmantis/ozw-network-visualization-card

Screenshots:

[sender]

Hi, cool! Will I t be possible to make this an addon or hacs ?

[filipedias (eduardo dias)]

Awesome! Great Work!

[abmantis]

Yeah, I plan to add this to HACS soon.

[sender]

Hi, followed the steps but upon adding the card I get:

Custom element doesn't exist: ozw-network-visualization-card.

type: 'custom:ozw-network-visualization-card'

[abmantis]

Have you restarted HA?

[arkoko (Arthur Kono)]

I had too. Ctrl-F5 (reload page) helped me.
But I have very strange map:

[sender]

Yes, no difference

[sender]

Reload (ctrl f5) does not take away the error for me…

[arkoko (Arthur Kono)]

My conf (yaml mode).

configuration.yaml
lovelace:
  mode: yaml
  resources:
    - url: /local/ozw-network-visualization-card.js
      type: module

ui-lovelace.yaml
title: Z-Wave Network
icon: mdi:z-wave
panel: true
cards:
  - type: custom:ozw-network-visualization-card

And file in the path:
config/www/ozw-network-visualization-card.js

Hope this helps

[rccoleman (Rob Coleman)]

This is great! Pretty much everything can see everything else in my house. Really easy to set up.

[arkoko (Arthur Kono)]

Wow! Pretty nice. I do not understand why my graph is so weird (above in my post)

[sender]

Yes, this helps! And Ah! Now I see why it didn’t work.

See below:

It clearly says

Put the ozw-network-visualization-card.js lovelace card into the [config]/www/ozw-network-vizualization-card directory

And thats what I did, I placed the file in the directory!

But reading your config above, and placing it in the www folder solved my issue.

Working now.

Thank you.

Edit: I don’t trust the diagram though… battery powered devices which do routing … thant can’t be true.
But I think this is cause OZW is reporting it as routing thus the error is not from your work.

Thanks again! Very nice.

[rccoleman (Rob Coleman)]

The neighbor list has always been a little confusing in the OZW Beta. If I use MQTT Explorer to search for “neighbor”, it only shows the battery-operated devices with neighbor lists. And in the graph, it shows all of my devices, including the battery-operated ones, as “Routing” and “Beaming”. So I don’t know where it’s getting the neighbor info for the wall-powered devices or why it’s confused about the battery-devices.

Since MQTT is the only means of communication between ozwdaemon and HA, you can see everything available in MQTT. For instance, it could be misinterpreting “Routing Slave” (which my battery devices say) as a device that can be used for routing (as I would interpret “Routing”). If the neighbor info isn’t available in MQTT, I wouldn’t believe what HA has to say about it. Garbage-in, Garbage-out, as they say. But I expect the data will improve as ozwdaemon matures.

[arkoko (Arthur Kono)]

In instruction vizualization and visualization are mixed as well.

[abmantis]

Oh, that’s an error on the docs! Thanks for pointing it out!
You could put it in the directory, but then you also have to specify it when adding the card to the lovelace resources.

[sender]

I always learnt that “there is 1 letter difference between networking and not working”

[abmantis]

In ozwadmin, do he sensors show Routing and Beaming as false?

@rccoleman The neighbors info is available on MQTT.

[rccoleman (Rob Coleman)]

I only see it for battery-operated devices. These are all battery-powered devices except for the Z-Stick:

If I open any of the other nodes, I don’t see that element. It looks like it may be part of an event:

    "Event": "nodeQueriesComplete",
    "TimeStamp": 1597494491,
    "NodeManufacturerName": "Elexa Consumer Products Inc. (Dome)",
    "NodeProductName": "Motion Detector",
    "NodeBasicString": "Routing Slave",
    "NodeBasic": 4,
    "NodeGenericString": "Notification Sensor",
    "NodeGeneric": 7,
    "NodeSpecificString": "Notification Sensor",
    "NodeSpecific": 1,
    "NodeManufacturerID": "0x021f",
    "NodeProductType": "0x0003",
    "NodeProductID": "0x0083",
    "NodeBaudRate": 100000,
    "NodeVersion": 4,
    "NodeGroups": 4,
    "NodeName": "DNH Motion Sensor",
    "NodeLocation": "",
    "NodeDeviceTypeString": "Home Security Sensor",
    "NodeDeviceType": 3079,
    "NodeRole": 6,
    "NodeRoleString": "Reporting Sleeping Slave",
    "NodePlusType": 0,
    "NodePlusTypeString": "Z-Wave+ node",
    "Neighbors": [
        1,
        4,
        5,
        6,
        8,
        16,
        37
    ],
    "Neighbors": [
        1,
        4,
        5,
        6,
        8,
        16,
        37
    ]
}

[firstof9]

This is an mqtt-explorer limitation/bug (the base64 image hits some kind of char limit). The neighbors exist for all nodes.

EDIT: Note you can add the repo to HACS as a custom repo.