Aeotec + Pi3B+ POE Hat and hassio (hassos) not working

Configuration Z-Wave
1

Just a heads up for everybody. I spent a lot of time trying to get Zwave running when I move from a 3B to a 3B+, I knew my aeotec stick was working on my old setup. The problem is the new POE Hat, as soon as I remove it everything works on my new setup.

Some more info:
On the new setup with POE Hat I keep getting the following error:

WARNING (Dummy-6) [openzwave] Z-Wave Notification DriverFailed : {‘notificationType’: ‘DriverFailed’, ‘homeId’: 0, ‘nodeId’: 255}

And if I look at Zwave management i got:

2018-09-04 08:22:36.803 Always, OpenZwave Version 1.4.3142 Starting Up
2018-09-04 08:24:04.681 Info, Setting Up Provided Network Key for Secure Communications
2018-09-04 08:24:04.681 Warning, Failed - Network Key Not Set
2018-09-04 08:24:04.686 Info, mgr, Added driver for controller /dev/ttyAMA0
2018-09-04 08:24:04.686 Info, Opening controller /dev/ttyAMA0
2018-09-04 08:24:04.687 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2018-09-04 08:24:04.687 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2018-09-04 08:24:04.698 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-09-04 08:24:04.699 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-09-04 08:24:04.699 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-09-04 08:24:04.699 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-09-04 08:24:04.699 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-09-04 08:24:04.699 Detail,
2018-09-04 08:24:04.699 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-09-04 08:24:04.700 Detail, contrlr, Notification: DriverFailed

2

All this is saying is that the device isn’t on /dev/ttyAMA0, it might be on /dev/ttyAMA1

3

If you have the ssh add-on, connect in and run hassio hw info to see how the devices are assigned. If you want to use the web interface, go to hassio > system > hardware.

Example from my non-plus pi3b.

core-ssh:~# hassio hw info
    {
        "result": "ok",
        "data": {
            "serial": [
                "/dev/ttyACM0",
                "/dev/ttyAMA0"
            ],
            "input": [],
            "disk": [],
            "gpio": [
                "gpiochip128",
                "gpiochip100",
                "gpiochip0"
            ],
            "audio": {
                "0": {
                    "name": "bcm2835_alsa - bcm2835 ALSA",
                    "type": "ALSA",
                    "devices": {
                        "0": "digital audio playback",
                        "1": "digital audio playback"
                    }
                }
            }
        }
    }
4

I tried that already many times, unfortunately it does not make a difference.

5

So with both the POE hat and your zwave stick installed, you don’t see any difference in how the devices are reported?

6

yes, they both show;
“serial”: [
“/dev/ttyACM0”,
“/dev/ttyAMA0”

7

I think that is just the zwave stick since it matches my report from above.
Try changing your configuration.yaml file to point to /dev/ttyACM0 and restart.

zwave:
  usb_path: /dev/ttyACM0
8

I don’t want to be rude but did you read my first post ? As soon as I remove the Hat everything works, nothing wrong with the stick.

9

Doesn’t mean that the POE Hat isn’t being found as a serial device knocking the stick to ttyACM0 tho.
Does the stick lights still light up when the POE Hat is plugged in?

10

I did read through the first post. I have always seen the Aeotec zwave stick configured and working as ttyACM0, not AMA0. Hence my suggestion to try ttyACM0. It could be as @firstof9 points out that adding the POE hat is impacting the addressing. Definitely odd behavior.

11

Looks like you might have a challenge here … :==> https://www.theregister.co.uk/2018/09/11/raspberry_pi_poe_hat_issue/

12

That explains a lot. I got it to work but it is not stable (Mostly I have to a Pi reboot, when I reboot HA it loses the zwave stick)