HA Yellow and Zooz 800LR Module

Hardware
1

Hi all!
I just snagged the Zooz 800LR (ZAC93 LR) GPIO Zwave module for my Home Assistant Yellow. I cannot for the life of me get it to be recognized. This is a brand new product so support from Zooz (so far) is generic and I can’t find anything about GPIO device activation for the Yellow.
I know it will most likely show as a serial device (maybe like ttyAMA3 or something), but I don’t see anything. I’m also thinking I need to change a jumper to activate the GPIO pins?

Thanks in advance for any input.

2

I found this and it seems like no jumpers are used in order to make use of the GPIO pins.
https://yellow.home-assistant.io/yellow-v1.2-standard/

3

I’ll be following this thread for sure. I’ve not yet received my Home Assistant Yellow (ordered in November). I did also just order this GPIO module. Hopefully a solution is found soon.

4

You might need to register (free) with Zooz support, but I found this article related to the ZAC93 GPIO module here:

https://www.support.getzooz.com/kb/article/1215-zac93-800-gpio-module-installation-guide/

Has details on installing and configuring with a Yellow! Hope this helps!

5

Definitely a good find as Zooz did point me to this last night.
I have open support cases with Zooz and Home Assistant, both.

Zooz is stating the contact they have with Home Assistant is on leave. Home Assistant so far seems to think that since my CM4 was not purcahsed with the kit that may have something to do with it.

My current working theory is that the CM4 is using ttyAMA0, which is what the GPIO pins use. So, I am trying to find out how to disable Bluetooth on the CM4.

I won’t be able to work on this again for a couple days, but will provide an update as soon as I have one.

6

Found an article that may help. It’s for a competitor’s GPIO board, but the disabling of Bluetooth and enabling the UART will be the same.

7

I’m following your progress. I just got the Zooz zac93 module and was not successful getting my rpi4 debian homeassistant container installl to recognize it in zwave js ui.

8

Ok. So I was able to get this working.
In the end, I did not do anything special.
But, the final step of selection ttyAMA0 within ZWave JS is all that I needed to do. Today, I selected ttyAMA0 3 times and saved it. The first 2 times it errored but on the 3rd time it recognized the device and everything is working great.

I have done this countless times before, and ZWave JS was able to initialize the device. I have performed some updates over the week, but I don’t see anything that would have helped me here.

Side note:
I learned from Home Assistant that the CM4 with WiFi has Bluetooth. If your CM4 does not have WiFi, then it does not have Bluetooth since they are on the same chip. However, if you have Bluetooth Home Assistant takes care of making sure ttyAMA0 is available on the GPIO pins on the board, so using ttyAMA0 should work no matter the CM4 version.

Overall, support from Zooz and Home Assistant was amazing. They have great support teams.

1 Like
9

@relic217 @NormandyHA Thanks for sharing!
Here’s a few notes to record how I got it working using the Zooz zac93 controller on my rpi4 running homeassistant and zwave js ui as containers. I am not sure if all of these steps are necessary, but it’s working:)

Edited the following file:
sudo nano /boot/config.txt

to add at the end:
dtoverlay=disable-bt

Edited the following file:
sudo nano /boot/cmdline.txt

to remove at the beginning:
console=serial0,115200

Opened raspi-config:
sudo raspi-config
Select Interfacing Options
Select Serial
“Would you like a login shell to be accessible over serial?” Select No
“Would you like the serial port hardware to be enabled?” Select Yes
reboot the rpi

Run the following command:
sudo systemctl disable hciuart
reboot again

I then setup zwavejsui as docker, I map the serial port to “/dev/zwave” for convenience, and I enter this as the device in the zwave js ui settings. Here’s my docker-compose:

version: '2.0'
services:
  zwavejsui:
    container_name: zwavejsui
    image: zwavejs/zwave-js-ui:latest
    restart: always
    devices:
      - '/dev/ttyAMA0:/dev/zwave'
    volumes:
      - /home/pi/share/zwavejsui:/usr/src/app/store
    ports:
      - '8091:8091'
      - '3000:3000'
1 Like
10

I just received my HA Yellow and installed the Zooz 800LR GPIO module. I’ve selected /dev/ttyAMA0 as the Serial Port and it seems to be finding the module, but is detecting it as “Unknown product 0x0611” with a Manufacturer of “Zooz”. I’ve tried each of iteration of the Jumper setting with no change. I’m using the CM4008000, with no onboard WiFi/BT or storage.

Has anyone else seen anything similar in their setup?

11

Hi,
Yes, I see the exact same thing. When working with Zooz, they mentioned that it would show as this and it would not effect any functionality.

1 Like
12

Excellent news, thanks for the response!

1 Like
13

Any thoughts on settings for “Normal Power Level” and “Measured Output Power at 0dBm”?
They both were 0 by default. I entered 3.3 in the “Measured Output Power at 0dBm” setting based on 700 series recommendation.

15

Do you have specifics on how and where you set this? I can take a look and test as I have all my ZWave stuff moved over to my Yellow now.

16

image
image1943×945 114 KB

Please let us know what settings you have there by default. Thank you!

17

Gotcha.

This is what I have now and it works just fine. I did, however, reach out Zooz by continuting of existing support thread to see if they have any suggestions for modification to increase performance. I will add their response here.

Screen Shot 2023-01-21 at 9.24.11 PM
Screen Shot 2023-01-21 at 9.24.11 PM2156×1180 224 KB

18

Thanks for sharing your default settings and reaching out to Zooz. :+1:

19

Their response:

“We would recommend leaving the values as is, unless your network is well backed up and you feel comfortable experimenting with different values. Otherwise, we don’t recommend changing the values.”

Pretty generic and no specific details.

I’ll be leaving mine as defaults. If you end up tinkering around with it and testing out different settings please report back!

1 Like
20

Curious if anyone using this setup has issues with devices immediately being flagged as “dead”? A ping fixes it. I see this happened with 700 series controllers too but had hoped 800 would fix it. I’m definitely running into that on my 800LR GPIO. On the pro, unlike my older Aeotec stick, it doesn’t just disappear and require rebooting my Pi (I don’t have a yellow yet - it was shipped yesterday though woohoo!). Overall I’ve mostly just traded one inconvenience for another.

21

I haven’t seen this issue at all on this GPIO 800 device. Also, I have never seen on my past 2 USB sticks either, but I’ve never run HA on a Pi.