RPi4 and Z-Wave.me RazBerry Board (version 1) - Cannot include nodes

[FreelancerJ]

Newbie here! First post and everything! Glad to join you wonderful folks!

The problem in a mouthful: I have the Z-Wave integration set up, but when I attempt to include a device, nothing happens. The one device that seems to have communicated with the RazBerry seems to have failed to provide any info in the interview.

Let’s go into more depth, so I can provide some more helpful info about what I’ve done so far

So where I’m at: I’ve set up a Raspberry Pi 4 with Home Assistant, using the alternate install method to get it up and running in Raspian, and HASSio is running happily in it’s docker. It even controls my Daikin without me needing to code, I’m impressed!

I’m up to trying to get my RazBerry Z-Wave Board running using the built in Integration.
I was previously using the RazBerry with the Z-Way software on a Raspberry Pi 3 with no issue, but the location left a bit to be desired (the Pi 3 is also my DNS host among other things and sits with the router at one end of the house) for coverage, and I wanted to have it more central, hence the Pi 4.
I excluded my Z-Wave devices and factory reset the RazBerry before moving it to the new Pi.

I’ve added dtoverlay=pi3-disable-bt to my /boot/config.txt, ran sudo systemctl disable hciuart and enabled the serial interface using the raspi-config tool. I’ve also purged modemmanager via apt-get

The Razberry shows up in HomeAssistant, and displays the following:

RazBerry Info

node id: 1
node name: Z-Wave.Me RaZberry Controller 2016 ZWave+
manufacturer name: Z-Wave.Me
product name: RaZberry Controller 2016 ZWave+
query stage: Complete
is awake: true
is ready: true
is failed: false
is info received: false
max baud rate: 40000
is zwave plus: false
capabilities: listening, staticUpdateController, beaming, primaryController, routing
neighbors: 2
sentCnt: 2
sentFailed: 0
retries: 0
receivedCnt: 0
receivedDups: 0
receivedUnsolicited: 0
sentTS: 2019-10-30 12:16:59:241
receivedTS: 2019-10-30 12:16:59:184
lastRequestRTT: 0
averageRequestRTT: 0
lastResponseRTT: 0
averageResponseRTT: 0

I’ve added the Z-Wave entry in my configuration.yaml, as well as linked to a network key I’ve stored in a secrets.yaml file.

I was able to get inclusion working for one device, sort of.
At first, when I hit include in the Z-Wave control panel in Home Assistant, nothing would seem to happen. The device I was trying to pair, a ZXT-120, is battery powered so I was timing pressing it’s button to include immediately after pressing include on HASS. I would press it, give the two a minute for interview, and then restart HASS.
After the third or forth time of this, a second Z-Wave entity pops up, as “Unknown Node 2” and nothing really useful

Unknown Node 2 info

node id: 2
node name: Unknown Node 2
manufacturer name: 
product name: 
query stage: Complete
is awake: true
is ready: true
is failed: false
is info received: false
max baud rate: 40000
is zwave plus: false
capabilities: beaming, frequent, routing
sentCnt: 12
sentFailed: 0
retries: 1
receivedCnt: 0
receivedDups: 0
receivedUnsolicited: 0
sentTS: 2019-10-30 12:17:27:240
receivedTS: 2019-10-30 12:16:59:184
lastRequestRTT: 0
averageRequestRTT: 0
lastResponseRTT: 0
averageResponseRTT: 0
application version: Unknown

Selecting “Refresh Node” doesn’t change the detail there, including if I refresh it, wait two minutes and then restart HASS, or Raspian. Here is the output in OZW Log when I try to refresh

OZW_Log when refreshing

2019-10-30 12:32:28.663 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=ProtocolInfo live=1
2019-10-30 12:32:28.663 Detail, Node002, QueryStage_Probe
2019-10-30 12:32:28.663 Info, Node002, NoOperation::Set - Routing=true
2019-10-30 12:32:28.664 Detail, Node002, Queuing (NoOp) NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x12, 0xd2
2019-10-30 12:32:28.664 Detail, Node002, Queuing (Query) Query Stage Complete (Probe)
2019-10-30 12:32:28.664 Detail,
2019-10-30 12:32:28.664 Info, Node002, Sending (NoOp) message (Callback ID=0x12, Expected Reply=0x13) - NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x12, 0xd2
2019-10-30 12:32:29.664 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:29.665 Detail, Node002, Removing current message
2019-10-30 12:32:29.665 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:29.666 Detail, Node002, Query Stage Complete (Probe)
2019-10-30 12:32:29.666 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=WakeUp live=1
2019-10-30 12:32:29.666 Detail, Node002, QueryStage_WakeUp
2019-10-30 12:32:29.667 Detail, Node002, QueryStage_ManufacturerSpecific1
2019-10-30 12:32:29.667 Detail, Node002, Checking for ManufacturerSpecific CC and Requesting values if present on this node
2019-10-30 12:32:29.667 Detail, Node002, Queuing (Query) ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x13, 0xa5
2019-10-30 12:32:29.667 Detail, Node002, Queuing (Query) Query Stage Complete (ManufacturerSpecific1)
2019-10-30 12:32:29.667 Detail,
2019-10-30 12:32:29.667 Info, Node002, Sending (Query) message (Callback ID=0x13, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x13, 0xa5
2019-10-30 12:32:30.667 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:30.667 Detail, Node002, Removing current message
2019-10-30 12:32:30.667 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:30.669 Detail, Node002, Query Stage Complete (ManufacturerSpecific1)
2019-10-30 12:32:30.669 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodeInfo live=1
2019-10-30 12:32:30.669 Detail, Node002, QueryStage_NodeInfo
2019-10-30 12:32:30.669 Detail, Node002, Queuing (Query) Request Node Info (Node=2): 0x01, 0x04, 0x00, 0x60, 0x02, 0x99
2019-10-30 12:32:30.669 Detail, Node002, Queuing (Query) Query Stage Complete (NodeInfo)
2019-10-30 12:32:30.670 Detail,
2019-10-30 12:32:30.670 Info, Node002, Sending (Query) message (Callback ID=0x00, Expected Reply=0x49) - Request Node Info (Node=2): 0x01, 0x04, 0x00, 0x60, 0x02, 0x99
2019-10-30 12:32:31.670 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:31.670 Detail, Node002, Removing current message
2019-10-30 12:32:31.670 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:31.672 Detail, Node002, Query Stage Complete (NodeInfo)
2019-10-30 12:32:31.672 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodePlusInfo live=1
2019-10-30 12:32:31.672 Detail, Node002, QueryStage_NodePlusInfo
2019-10-30 12:32:31.672 Detail, Node002, QueryStage_SecurityReport
2019-10-30 12:32:31.672 Detail, Node002, QueryStage_ManufacturerSpecific2
2019-10-30 12:32:31.672 Detail, Node002, Queuing (Query) ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x14, 0xa2
2019-10-30 12:32:31.672 Detail, Node002, Queuing (Query) Query Stage Complete (ManufacturerSpecific2)
2019-10-30 12:32:31.672 Detail,
2019-10-30 12:32:31.672 Info, Node002, Sending (Query) message (Callback ID=0x14, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x14, 0xa2
2019-10-30 12:32:32.673 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:32.673 Detail, Node002, Removing current message
2019-10-30 12:32:32.673 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:32.674 Detail, Node002, Query Stage Complete (ManufacturerSpecific2)
2019-10-30 12:32:32.674 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Versions live=1
2019-10-30 12:32:32.674 Detail, Node002, QueryStage_Versions
2019-10-30 12:32:32.674 Info, Node002, Requesting Versions
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_NO_OPERATION
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_BASIC
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_THERMOSTAT_MODE
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_THERMOSTAT_SETPOINT
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_MANUFACTURER_SPECIFIC
2019-10-30 12:32:32.675 Info, Node002, Requesting Versions for COMMAND_CLASS_VERSION
2019-10-30 12:32:32.675 Detail, Node002, QueryStage_Instances
2019-10-30 12:32:32.675 Info, Node002, Essential node queries are complete
2019-10-30 12:32:32.675 Detail, Node002, QueryStage_Static
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) ThermostatModeCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x04, 0x25, 0x15, 0x91
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) ThermostatSetpointCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x43, 0x04, 0x25, 0x16, 0x91
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x17, 0xa1
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) VersionCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x86, 0x11, 0x25, 0x18, 0x4f
2019-10-30 12:32:32.675 Detail, Node002, Queuing (Query) Query Stage Complete (Static)
2019-10-30 12:32:32.676 Detail, Node002, Notification: EssentialNodeQueriesComplete
2019-10-30 12:32:32.676 Detail,
2019-10-30 12:32:32.676 Info, Node002, Sending (Query) message (Callback ID=0x15, Expected Reply=0x04) - ThermostatModeCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x04, 0x25, 0x15, 0x91
2019-10-30 12:32:33.676 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:33.676 Detail, Node002, Removing current message
2019-10-30 12:32:33.676 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:33.678 Detail,
2019-10-30 12:32:33.678 Info, Node002, Sending (Query) message (Callback ID=0x16, Expected Reply=0x04) - ThermostatSetpointCmd_SupportedGet (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x43, 0x04, 0x25, 0x16, 0x91
2019-10-30 12:32:34.678 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:34.678 Detail, Node002, Removing current message
2019-10-30 12:32:34.679 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:34.680 Detail,
2019-10-30 12:32:34.680 Info, Node002, Sending (Query) message (Callback ID=0x17, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x72, 0x04, 0x25, 0x17, 0xa1
2019-10-30 12:32:35.680 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:35.681 Detail, Node002, Removing current message
2019-10-30 12:32:35.681 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:35.682 Detail,
2019-10-30 12:32:35.682 Info, Node002, Sending (Query) message (Callback ID=0x18, Expected Reply=0x04) - VersionCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x86, 0x11, 0x25, 0x18, 0x4f
2019-10-30 12:32:36.683 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:36.683 Detail, Node002, Removing current message
2019-10-30 12:32:36.683 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:36.684 Detail, Node002, Query Stage Complete (Static)
2019-10-30 12:32:36.684 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Associations live=1
2019-10-30 12:32:36.684 Detail, Node002, QueryStage_Associations
2019-10-30 12:32:36.684 Detail, Node002, QueryStage_Neighbors
2019-10-30 12:32:36.685 Detail, Requesting routing info (neighbor list) for Node 2
2019-10-30 12:32:36.685 Detail, Node002, Queuing (Command) Get Routing Info (Node=2): 0x01, 0x07, 0x00, 0x80, 0x02, 0x00, 0x00, 0x03, 0x79
2019-10-30 12:32:36.685 Detail, Node002, Queuing (Query) Query Stage Complete (Neighbors)
2019-10-30 12:32:36.685 Detail,
2019-10-30 12:32:36.685 Info, Node002, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=2): 0x01, 0x07, 0x00, 0x80, 0x02, 0x00, 0x00, 0x03, 0x79
2019-10-30 12:32:37.685 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:37.685 Detail, Node002, Removing current message
2019-10-30 12:32:37.685 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:37.687 Detail, Node002, Query Stage Complete (Neighbors)
2019-10-30 12:32:37.687 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2019-10-30 12:32:37.687 Detail, Node002, QueryStage_Session
2019-10-30 12:32:37.687 Detail, Node002, QueryStage_Dynamic
2019-10-30 12:32:37.687 Detail, Node002, Queuing (Send) ThermostatModeCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x02, 0x25, 0x19, 0x9b
2019-10-30 12:32:37.687 Detail, Node002, Queuing (Query) Query Stage Complete (Dynamic)
2019-10-30 12:32:37.687 Detail,
2019-10-30 12:32:37.687 Info, Node002, Sending (Send) message (Callback ID=0x19, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x40, 0x02, 0x25, 0x19, 0x9b
2019-10-30 12:32:38.688 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:32:38.688 Detail, Node002, Removing current message
2019-10-30 12:32:38.688 Detail, Node002, Notification: Notification - TimeOut
2019-10-30 12:32:38.689 Detail, Node002, Query Stage Complete (Dynamic)
2019-10-30 12:32:38.689 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2019-10-30 12:32:38.690 Detail, Node002, QueryStage_Configuration
2019-10-30 12:32:38.690 Detail, Node002, QueryStage_Complete
2019-10-30 12:32:38.690 Warning, CheckCompletedNodeQueries m_allNodesQueried=1 m_awakeNodesQueried=1
2019-10-30 12:32:38.690 Detail, Node002, Notification: NodeQueriesComplete

I’ve also tried to add a second device, a Aeotec Multisensor 6, to the Z-Wave network however I cannot get inclusion to work for it. The LED indicator pretty clearly shows the pattern for “Inclusion Failed”, according to its manual. The logging I’m getting is as follows.

OZW_Log when including Aeotec Multisensor

2019-10-30 12:40:52.878 Detail, Queuing (Controller) Add Device
2019-10-30 12:40:52.878 Info, Add Device
2019-10-30 12:40:52.878 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1a, 0x6b
2019-10-30 12:40:52.879 Detail, Notification: ControllerCommand - Starting
2019-10-30 12:40:52.880 Detail,
2019-10-30 12:40:52.880 Info, contrlr, Sending (Command) message (Callback ID=0x1a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x1a, 0x6b
2019-10-30 12:40:53.881 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-30 12:40:53.881 Detail, contrlr, Removing current message
2019-10-30 12:40:53.881 Detail, contrlr, Notification: Notification - TimeOut
2019-10-30 12:40:53.881 Detail, Notification: ControllerCommand - Error - Failed

I don’t know if any of that hints to anyone what I’m getting wrong in all this, or any anyone has a similar setup that can walk me through how to get working.

This is a brand new installation as well, so I am not really opposed to blowing it away and starting again if I have to, but I feel like this will be something really simple I’m missing

Research I’ve done so far
Looking around the forums I’ve only found a few 2-3 year old posts about running Razberrys.
Most are getting stuck making HomeAssistant communicate with the board, rather than trouble including devices, so other than a cursory glance at their solutions to see if they had any steps to set up that I didn’t do, they don’t seem to apply.

Others were having trouble getting HomeAssistant to discover devices that were already paired to the board from previous software, which also doesn’t really apply. most were solved by starting the Z-Wave network over from scratch…

One thing I’ve seen mentioned a few times is installing python-openzwave.
Since I’m running HASS via Docker and not in a Python virtual environment, I figured this doesn’t really apply to me (yeah I know HASS is in python inside the docker).
The OZW_log indicates at the start that it is running OpenZwave Version 1.4.3440 so hopefully that’s right, otherwise I’m not sure I know how to fix it inside the Docker…

Thanks in advance for any insight, ideas and advice you guys have!

[brendan]

Have you tried adding it using the Z-Wave integration instead of via YAML?

Unfortunately I havent tested an RPI4 as I don’t currently have one to try, but it should just be /dev/ttyAMA0 for the path for the hardware if I recall. I am not sure if the dtoverlay=pi3-disable-bt works on a Pi4 though.

ZXT-120 is tempramental. It has timing issues and it doesn’t work properly with any ZWave stick in Home Assistant. I could get maybe one or two commands to work then it would stop again. There are a few discussions on it.

If you have devices that were paired previously, I would strongly recommend excluding them before including them, even go as far as a factory reset for them. Also try deleting the zwave cache file, which should be located in your CONFIG folder. The file is the zwcfg_xxxxxxxx.xml file.

OZW 1.4x is correct with HA. HA uses a forked version of OZW1.4 .

Edit: Just noticed this was 4 months ago. Hopefully you actually have your issue sorted by now

[FreelancerJ]

Hey, thanks for replying!

I actually never did get it sorted. I’ve since popped my Razberry board back on the original Pi 3 and set that network back up. I’ve been on and off trying to get my head around MQTT to connect them, while occasionally peeking back here in hopes someone might jump in with “Tada, this is how I got it working!”

So in answer to each thing you’ve mentioned:

As far as I recall, the board wouldn’t show up in the Z-Wave Integration unless I entered in the details of where to find it in yaml. I’ll recheck this shortly.

The dtoverlay control does indeed work on a Pi 4. I did try installing the ZWay.me software on the Pi and it was working ok there.

Yeah, I get the feel of that with the ZXT in normal use, it always takes a couple of tries to get going when initially setting it up with ZWay. I also have a Aeotec Multisensor 6 (ZW100-B) which from memory I couldn’t get to include in any way shape or form. The light on the sensor would show it is in inclusion mode, and then flash the signal that it had given up waiting whenever trying to include through HomeAssistant.

Given we’ve been sent on leave from work due to the CoVid situation, I have time to tinker again, so I’ll reset all my Z-wave sensors and Razberry and pop the board into the Pi 4 again if you want to help me troubleshoot
All that’s connecting right now are devices acting as sensors for me, so it’s a pretty simple network to get going. I do want to get this going properly though, either directly or with MQTT before I replace a bunch of light switches with z-wave relays

[brendan]

I hope have some luck with it. Unfortunately I work in one of the “essential services” areas, so my work has actually increased rather than decreased and I don’t have time to tinker much now.
You could look at the new QT-OpenZwave that is being developed for HA as well. It looks very interesting for running Zwave Controllers on a device separate from HA. Just be aware it is very much pre-beta still

The Future of Z-Wave in HA - QT-OpenZWave

Hi all, In the state of the union 2019 presentation there was a brief update on the path to Open Z-Wave 1.6. Short mention of it can be found here. [Home Assistant - State of the Union 2019] This sounds like a great path forward. There will be a separation between Home Assistant and Z-Wave meaning that restarting HA will not result in a restart of the Z-Wave network. My initial guess is this will be in a separate docker container like a Hassio addon. It will then by connected t…

[FreelancerJ]

That looks super exciting, can’t wait for it.
I actually just rebooted my Pi as part of fixing an issue with it’s wifi, and now its spent the last hour or so listing filesystem issues, so at this point I might need to start it from scratch anyway, so I might opt in to bug test for this newness and see how it goes. I’ll let ya know!

Stay safe with work, hope you’re not in a customer facing gig. We shut down early cause we average 2-3000 people through our doors a day and it was just a disaster waiting the happen
We could probably argue that we are “essential” but the higher ups (thankfully) decided that chances of infection to staff, as well as number of members of the public, was too high to be worth it, even after working hard to reduce traffic and ramping up the sanitising.