[HELP!]Trouble staring z-way-server and finding attached device

Discussions about RaZberry - Z-Wave board for Raspberry computer
Post Reply
CrashOverrideCS
Posts: 4
Joined: 19 Apr 2020 09:18

[HELP!]Trouble staring z-way-server and finding attached device

Post by CrashOverrideCS »

I have the RaZberry attached to my Raspberry Pi 4. I went through the process of setting up home-assistant.io today. Once that was said and done, I moved onto setting up the z-way controller which I thought was already installed. I tried following these instructions to get the path of my controller: https://www.home-assistant.io/docs/z-wa ... oller-path

Code: Select all

ls -ltr /dev/tty*|tail -n 1
crw-rw-rw- 1 root tty       5,  0 Apr 19 07:22 /dev/tty
but I can't find it. All attempts to install z-way-server seem to work, but I can't tell that it did since I don't have any services listed or web traffic out of https://find.z-wave.me/zboxweb/r// (10.0.0.215)

Here is my config.txt:

Code: Select all

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
# dtoverlay=vc4-fkms-v3d
start_x=1
gpu_mem=256
dtoverlay=pi3-miniuart-bt
enable_uart=1
dtoverlay=w1-gpio
CrashOverrideCS
Posts: 4
Joined: 19 Apr 2020 09:18

Re: [HELP!]Trouble staring z-way-server and finding attached device

Post by CrashOverrideCS »

The result of trying to install (again)

Code: Select all

 xenos@Atlantus  ~  wget -q -O - https://razberry.z-wave.me/install/v3.0.0 | sudo bash
[sudo] password for xenos: 
Hit:1 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:2 https://download.docker.com/linux/raspbian buster InRelease                             
Hit:3 http://apt.puppetlabs.com stretch InRelease                                             
Hit:4 https://dl.yarnpkg.com/debian stable InRelease                                          
Hit:7 http://archive.raspberrypi.org/debian buster InRelease                                  
Hit:8 http://raspbian.raspberrypi.org/raspbian buster InRelease                               
Ign:5 https://dl.bintray.com/etcher/debian stable InRelease                                   
Get:9 https://dl.bintray.com/etcher/debian stable Release [3,674 B]                           
Hit:6 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease                  
Ign:10 http://deb.theforeman.org precise InRelease                                            
Ign:11 http://deb.theforeman.org wheezy InRelease      
Ign:12 http://deb.theforeman.org plugins InRelease
Hit:13 http://deb.theforeman.org precise Release                       
Hit:14 http://deb.theforeman.org wheezy Release                        
Hit:15 http://deb.theforeman.org plugins Release 
Hit:16 https://repo.z-wave.me/z-way/raspbian buster InRelease
Err:6 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
Fetched 3,674 B in 4s (842 B/s)
Reading package lists... Done
N: Skipping acquire of configured file 'etcher/binary-armhf/Packages' as repository 'https://deb.etcher.io stable InRelease' doesn't support architecture 'armhf'
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
W: Failed to fetch https://packagecloud.io/headmelted/codebuilds/debian/dists/stretch/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
apt-transport-https is already the newest version (1.8.2).
dirmngr is already the newest version (2.2.12-1+rpi1+deb10u1).
The following packages were automatically installed and are no longer required:
  libmbim-glib4 libmbim-proxy libqmi-glib5 libqmi-proxy
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Executing: /tmp/apt-key-gpghome.QAvf6VhCdF/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0x7E148E3C
gpg: key 2222290F7E148E3C: "Z-Wave.Me <info@z-wave.me>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
Hit:1 http://apt.puppetlabs.com stretch InRelease
Hit:2 https://dl.yarnpkg.com/debian stable InRelease                                          
Hit:4 https://brave-browser-apt-release.s3.brave.com stable InRelease                         
Hit:5 https://download.docker.com/linux/raspbian buster InRelease                             
Hit:7 http://archive.raspberrypi.org/debian buster InRelease                                  
Ign:3 https://dl.bintray.com/etcher/debian stable InRelease                                   
Get:8 https://dl.bintray.com/etcher/debian stable Release [3,674 B]                           
Hit:6 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease                  
Ign:9 http://deb.theforeman.org precise InRelease                                             
Hit:10 http://raspbian.raspberrypi.org/raspbian buster InRelease                              
Ign:11 http://deb.theforeman.org wheezy InRelease                                             
Ign:12 http://deb.theforeman.org plugins InRelease                      
Hit:13 http://deb.theforeman.org precise Release  
Hit:14 http://deb.theforeman.org wheezy Release                        
Hit:15 http://deb.theforeman.org plugins Release                       
Hit:16 https://repo.z-wave.me/z-way/raspbian buster InRelease          
Err:6 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
Fetched 3,674 B in 4s (901 B/s)
Reading package lists... Done
N: Skipping acquire of configured file 'etcher/binary-armhf/Packages' as repository 'https://deb.etcher.io stable InRelease' doesn't support architecture 'armhf'
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
W: Failed to fetch https://packagecloud.io/headmelted/codebuilds/debian/dists/stretch/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libmbim-glib4 libmbim-proxy libqmi-glib5 libqmi-proxy
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/822 B of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 180408 files and directories currently installed.)
Preparing to unpack .../z-way-full_1.0-latest-version_all.deb ...
Unpacking z-way-full (1.0-latest-version) over (1.0-latest-version) ...
Setting up z-way-full (1.0-latest-version) ...
CrashOverrideCS
Posts: 4
Joined: 19 Apr 2020 09:18

Re: [HELP!]Trouble staring z-way-server and finding attached device

Post by CrashOverrideCS »

Am I missing a z-wave-server here?

Code: Select all

ls -A etc/init.d              
alsa-utils        .depend.stop       lightdm          pppd-dns      sudo
apparmor          dhcpcd             mongoose         procps        sysstat
avahi-daemon      docker             networking       raspi-config  triggerhappy
bluetooth         dphys-swapfile     network-manager  rng-tools     udev
console-setup.sh  etc-setserial      nfs-common       rpcbind       unattended-upgrades
cron              fake-hwclock       paxctld          rsync         x11-common
dbus              hwclock.sh         plymouth         rsyslog       zbw_connect
.depend.boot      keyboard-setup.sh  plymouth-log     setserial
.depend.start     kmod               postgresql       ssh
CrashOverrideCS
Posts: 4
Joined: 19 Apr 2020 09:18

Re: [HELP!]Trouble staring z-way-server and finding attached device

Post by CrashOverrideCS »

It is possible I am at the point now where the server is working and Home Assistant is the issue here, but I want to confirm. There is a "OZW" log in Home Assistant, and when I attempt to add a "node", this is the log:

Code: Select all

2020-04-19 13:04:44.181 Detail, Queuing (Controller) Add Device
2020-04-19 13:04:44.182 Info, Add Device
2020-04-19 13:04:44.182 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0e, 0x7f
2020-04-19 13:04:44.182 Detail, Notification: ControllerCommand - Starting
2020-04-19 13:04:44.183 Detail,
2020-04-19 13:04:44.183 Info, contrlr, Sending (Command) message (Callback ID=0x0e, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0e, 0x7f
2020-04-19 13:04:44.186 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0e, 0x01, 0x00, 0x00, 0xbd
2020-04-19 13:04:44.186 Detail,
2020-04-19 13:04:44.186 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-19 13:04:44.186 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2020-04-19 13:04:44.186 Detail, Node001,   Expected callbackId was received
2020-04-19 13:04:44.186 Detail, Node001,   Expected reply was received
2020-04-19 13:04:44.186 Detail, Node001,   Message transaction complete
2020-04-19 13:04:44.186 Detail,
2020-04-19 13:04:44.186 Detail, contrlr, Removing current message
2020-04-19 13:04:44.186 Detail, Notification: ControllerCommand - Waiting
2020-04-19 13:04:44.186 Info, WriteNextMsg Controller nothing to do
And when I try to add "Secure Nodes"

Code: Select all

2020-04-19 13:07:17.954 Detail,
2020-04-19 13:07:23.117 Detail, Queuing (Controller) Add Device
2020-04-19 13:07:23.118 Info, Add Device
2020-04-19 13:07:23.118 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0f, 0x7e
2020-04-19 13:07:23.118 Detail, Notification: ControllerCommand - Starting
2020-04-19 13:07:23.120 Detail,
2020-04-19 13:07:23.120 Info, contrlr, Sending (Command) message (Callback ID=0x0f, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0f, 0x7e
2020-04-19 13:07:23.123 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0f, 0x01, 0x00, 0x00, 0xbc
2020-04-19 13:07:23.123 Detail,
2020-04-19 13:07:23.123 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-19 13:07:23.123 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2020-04-19 13:07:23.123 Detail, Node001,   Expected callbackId was received
2020-04-19 13:07:23.123 Detail, Node001,   Expected reply was received
2020-04-19 13:07:23.123 Detail, Node001,   Message transaction complete
2020-04-19 13:07:23.123 Detail,
2020-04-19 13:07:23.123 Detail, contrlr, Removing current message
2020-04-19 13:07:23.123 Detail, Notification: ControllerCommand - Waiting
2020-04-19 13:07:23.124 Info, WriteNextMsg Controller nothing to do
I'm not seeing my light "node" I'm trying to sync up with my network showing up in HomeAssistant, but I'm not sure if it is at fault, or if there is another way to check and manually connect a bluetooth/wifi device outside of HomeAssistant?
equathza
Posts: 20
Joined: 10 Aug 2015 20:15

Re: [HELP!]Trouble staring z-way-server and finding attached device

Post by equathza »

Irony here is that you might not understand that hass.io has it's own "openZ-wave" implementation, which is different from Z-way server.
Both application (home assistant and z-way-server) can talk to the z-wave controller, however not at the same time!

Useful information about how hass.io has it's Z-wave implementation:
https://www.home-assistant.io/docs/z-wave/adding/
https://www.home-assistant.io/docs/z-wa ... -specific/

I've only briefly looked into hass.io for controlling my Z-wave network. Their implementation I've found to be a complicated mess..

I'm not seeing my light "node" I'm trying to sync up with my network showing up in HomeAssistant, but I'm not sure if it is at fault, or if there is another way to check and manually connect a bluetooth/wifi device outside of HomeAssistant?
Don't exactly understand your question here... Are you asking if there is an easy way to connect to a bluetooth/wifi device in Z-way server?

If so, I think if it's not supported in Z-way server, or a available plugin. You can either create some script, or have to write a module yourself.
-> A fellow Z-way user running a network of 50+ devices
luxus
Posts: 12
Joined: 20 Sep 2015 11:34

Re: [HELP!]Trouble staring z-way-server and finding attached device

Post by luxus »

CrashOverrideCS wrote:
19 Apr 2020 21:18
Am I missing a z-wave-server here?
hey chrash,
how did u got the server running? i have the same problem
Post Reply