My Docker Stack

To be honest, I hadn’t tried that due to this from Control startup order in Compose.

However, Compose does not wait until a container is “ready” (whatever that means for your particular application) - only until it’s running. There’s a good reason for this.

The problem of waiting for a database (for example) to be ready is really just a subset of a much larger problem of distributed systems. In production, your database could become unavailable or move hosts at any time. Your application needs to be resilient to these types of failures.

It goes on to suggest Dockerize. I’ll give depends_on a try. I’m guessing it will still fail for Zoneminder since the slight head-start still won’t be enough for Zoneminder to initialize the mysql database, apache and zm.

Ultimately it would be better for Home Assistant to retry services at a specified interval.

Well, with all the buzz going around with Docker, I decided to try my hand at it. With a few Google searches and thanks to @flamingm0e I think that I was able to get Docker installed along with Docker-Compose and spun off Portainer for my docker-compose.yml file. So Thank YOU!!

Now my question is … when I reboot my Raspberry Pi, nothing comes up. I know that Docker is set to restart automatically, but Docker-Compose does not. I’ve seen articles on people adding an “@reboot” in their crontab file, but not sure if this is the best method.

Lastly, currently I am using Caddy as a reverse proxy and automatic SSL renewal, I don’t mind switching to NGINX, but haven’t seen anyone’s compose file for an example. I am also dependent on RPI RF, I haven’t seen a home assistant package for that, maybe I missed it.
I still need to figure out how to rollout Samba, but haven’t had a chance to look at how it’s configured.

Thanks to the OP for sharing and replies throughout this thread. Very valuable.

1 Like

Since Raspbian uses SystemD, you could place a file inside /etc/systemd/system/ (e.g. docker-compose.service) and the following content:

[Unit]
Description=Docker stack for Home Assistant
After=network.target docker.service
[Service]
Type=simple
WorkingDirectory=/srv/hass-stack
ExecStart=/usr/local/bin/docker-compose -f /srv/hass-stack/docker-compose.yml up
ExecStop=/usr/local/bin/docker-compose -f /srv/hass-stack/docker-compose.yml down
[Install]
WantedBy=multi-user.target

As you can see, /srv/hass-stack is the location of my docker-compose.yml, adjust this to your needs.

Then, do:

sudo systemctl daemon-reload
sudo systemctl enable docker-compose
sudo systemctl restart docker-compose

once and you’re good to go.

2 Likes

That seems like a great solution @m0wlheld I can surly try that.

Now I notice that you are not starting your docker-compose with option “-d” I’ve tried to research what this option does and really can’t find an answer on the web. Is there an advantage of using “-d”? such as “docker-compose.yml up -d”

-d makes docker-compose detach from the starting process. So it’s useful to call this option from command line, but is is not required for systemd.

That’s the best explanation that I have found !! Thank you very much

One last question, with this setup, can we use hass.io images? I think that there is one for RPi_RF. Or are they a separate beast all together?

If you set your containers to ‘restart always’ in your compose, you don’t have to auto-start docker-compose

I don’t use a compose for that. just point your config to a bind mount and edit your configs as you desire.

And you are still using a docker container for NGINX right?
this may be a premature questions and I should try it first, but do you have to get in the container to add the config? or is that external.

I’m running reverse proxy on a digital ocean droplet. Not in docker, but the concept is the same.

You do a bind mount for the location of your configs and just drop your configs in.

I am trying to use Docker to get Home-Assistant started, but if I follow the installation guide (https://home-assistant.io/docs/installation/docker/) Home-Assistant won’t start. Portainer, Watchttower, etc. are already running in their own containers though.

Do I need a different HA-image for my RPi?

Here are the error messages I have in Portainer-Logs:
standard_init_linux.go:195: exec user process caused "exec format error"

My docker-compose.yml

version: "3"
    services:
      hass:
        container_name: home-assistant
        image: homeassistant/home-assistant
        volumes:
          - ../configuration/home-assistant:/config
          - /etc/localtime:/etc/localtime:ro
        devices:
          - "/dev/ttyAMA0:/dev/ttyAMA0"
        restart: always
        network_mode: host

Yes, you need one built for a pi. What you are trying to run is built for x86

I believe what you want is: homeassistant/raspberrypi3-homeassistant

2 Likes

Ok, got it. Thank you. I used homeassistant/raspberryp2-homeassistant though ;).

Only thing which isn’t working is my Razberry Z-Wave Hub. I copied my old configuration folder over to my new docker install. Everything is working except for Z-Wave. Sometimes the devices are showing up, but don’t get their specific device names, sometimes they don’t even appear in Home-Assistant, because of Warning, WARNING: Out of frame flow! (0x00). Sending NAK.

Should I install the Open ZWave-Panel using another docker? Do I have to wait a while for Open ZWave to be installed? Should I open another topic for this?

Here is my OCW Log:

2018-03-10 12:44:50.145 Always, OpenZwave Version 1.4.2926 Starting Up
2018-03-10 12:45:18.596 Info, Setting Up Provided Network Key for Secure Communications
2018-03-10 12:45:18.597 Warning, Failed - Network Key Not Set
2018-03-10 12:45:18.597 Info,   Opening controller /dev/ttyAMA0
2018-03-10 12:45:18.597 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2018-03-10 12:45:18.598 Info, mgr,     Added driver for controller /dev/ttyAMA0
2018-03-10 12:45:18.598 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2018-03-10 12:45:18.602 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-03-10 12:45:18.602 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-03-10 12:45:18.602 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-03-10 12:45:18.603 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-03-10 12:45:18.603 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-03-10 12:45:18.603 Detail,
2018-03-10 12:45:18.603 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-03-10 12:45:18.606 Detail, contrlr,   Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x34, 0x2e, 0x30, 0x35, 0x00, 0x01, 0x97
2018-03-10 12:45:18.606 Detail,
2018-03-10 12:45:18.606 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
2018-03-10 12:45:18.606 Info, contrlr,     Static Controller library, version Z-Wave 4.05
2018-03-10 12:45:18.606 Detail, Node045,   Expected reply was received
2018-03-10 12:45:18.607 Detail, Node045,   Message transaction complete
2018-03-10 12:45:18.607 Detail,
2018-03-10 12:45:18.607 Detail, contrlr, Removing current message
2018-03-10 12:45:18.607 Detail,
2018-03-10 12:45:18.607 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-03-10 12:45:18.609 Warning, WARNING: Out of frame flow! (0x08).  Sending NAK.
2018-03-10 12:45:18.610 Warning, WARNING: Out of frame flow! (0x08).  Sending NAK.
2018-03-10 12:45:18.612 Warning, WARNING: Out of frame flow! (0x08).  Sending NAK.
2018-03-10 12:45:18.613 Warning, WARNING: Out of frame flow! (0x08).  Sending NAK.
2018-03-10 12:45:28.607 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:28.608 Detail, contrlr, Removing current message
2018-03-10 12:45:28.608 Detail, contrlr, Notification: Notification - TimeOut
2018-03-10 12:45:28.609 Detail,
2018-03-10 12:45:28.609 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-03-10 12:45:28.611 Detail, Unsolicited message received while waiting for ACK.
2018-03-10 12:45:28.611 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x05, 0x1c, 0xe3
2018-03-10 12:45:28.611 Detail,
2018-03-10 12:45:28.611 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
2018-03-10 12:45:28.611 Info, contrlr,     There is a SUC ID Server (SIS) in this network.
2018-03-10 12:45:28.611 Info, contrlr,     The PC controller is an inclusion static update controller (SUC) and was the original primary before the SIS was added.
2018-03-10 12:45:28.611 Detail, Node227,   Expected reply was received
2018-03-10 12:45:28.611 Detail, Node227,   Message transaction complete
2018-03-10 12:45:28.612 Detail,
2018-03-10 12:45:28.612 Detail, contrlr, Removing current message
2018-03-10 12:45:28.612 Detail,
2018-03-10 12:45:28.612 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-03-10 12:45:28.613 Detail, Unsolicited message received while waiting for ACK.
2018-03-10 12:45:28.614 Detail, Node004,   Received: 0x01, 0x07, 0x05, 0x04, 0x01, 0x04, 0x00, 0x00, 0x02
2018-03-10 12:45:28.614 Warning, Node004, WARNING: Checksum incorrect - sending NAK
2018-03-10 12:45:28.615 Warning, WARNING: Out of frame flow! (0xcf).  Sending NAK.
2018-03-10 12:45:28.616 Warning, WARNING: Out of frame flow! (0x67).  Sending NAK.
2018-03-10 12:45:28.616 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2018-03-10 12:45:28.617 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2018-03-10 12:45:28.618 Detail, Unsolicited message received while waiting for ACK.
2018-03-10 12:45:28.619 Detail, Node071,   Received: 0x01, 0x07, 0x05, 0x04, 0x01, 0x47, 0x04, 0x00, 0x00
2018-03-10 12:45:28.619 Warning, Node071, WARNING: Checksum incorrect - sending NAK
2018-03-10 12:45:28.619 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2018-03-10 12:45:28.620 Warning, WARNING: Out of frame flow! (0x80).  Sending NAK.
2018-03-10 12:45:28.621 Warning, WARNING: Out of frame flow! (0xe8).  Sending NAK.
2018-03-10 12:45:28.621 Warning, WARNING: Out of frame flow! (0x1a).  Sending NAK.
2018-03-10 12:45:28.622 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2018-03-10 12:45:28.623 Warning, WARNING: Out of frame flow! (0x83).  Sending NAK.
2018-03-10 12:45:28.624 Warning, WARNING: Out of frame flow! (0x9f).  Sending NAK.
2018-03-10 12:45:28.624 Warning, WARNING: Out of frame flow! (0x80).  Sending NAK.
2018-03-10 12:45:28.625 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2018-03-10 12:45:28.626 Detail, Unsolicited message received while waiting for ACK.
2018-03-10 12:45:28.630 Detail, contrlr,   Received: 0x01, 0x2b, 0x01, 0x07, 0x05, 0x04, 0x01, 0x47, 0x04, 0x00, 0x00, 0x02, 0xfe, 0x83, 0xff, 0x88, 0xcf, 0x1f, 0x00, 0x00, 0xfb, 0x9f, 0x7d, 0xa0, 0x67, 0x00, 0x80, 0x80, 0x00, 0x80, 0x86, 0x00, 0x00, 0x00, 0xe8, 0x73, 0x00, 0x00, 0x0e, 0x00, 0x00, 0x40, 0x1a, 0x00, 0x5e
2018-03-10 12:45:28.630 Detail,
2018-03-10 12:45:28.630 Info, contrlr,  Received reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES
2018-03-10 12:45:28.630 Info, contrlr,     Serial API Version:   5.4
2018-03-10 12:45:28.630 Info, contrlr,     Manufacturer ID:      0x0147
2018-03-10 12:45:28.630 Info, contrlr,     Product Type:         0x0400
2018-03-10 12:45:28.630 Info, contrlr,     Product ID:           0x0002
2018-03-10 12:45:28.630 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2018-03-10 12:45:28.630 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2018-03-10 12:45:28.630 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2018-03-10 12:45:28.631 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2018-03-10 12:45:28.631 Detail, Node004,   Expected reply was received
2018-03-10 12:45:28.631 Detail, Node004,   Message transaction complete
2018-03-10 12:45:28.631 Detail,
2018-03-10 12:45:28.631 Detail, contrlr, Removing current message
2018-03-10 12:45:28.631 Detail,
2018-03-10 12:45:28.631 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-03-10 12:45:28.633 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x56, 0x01, 0xad
2018-03-10 12:45:28.633 Detail,
2018-03-10 12:45:28.633 Info, contrlr, Received reply to GET_SUC_NODE_ID.  Node ID = 1
2018-03-10 12:45:28.634 Detail, Node173,   Expected reply was received
2018-03-10 12:45:28.634 Detail, Node173,   Message transaction complete
2018-03-10 12:45:28.634 Detail,
2018-03-10 12:45:28.634 Detail, contrlr, Removing current message
2018-03-10 12:45:28.634 Detail,
2018-03-10 12:45:28.634 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x1c) - FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2018-03-10 12:45:28.688 Detail, contrlr,   Received: 0x01, 0x25, 0x01, 0x1c, 0x01, 0x20, 0x2c, 0x8b, 0x73, 0x86, 0x69, 0xd6, 0x3e, 0x66, 0xc4, 0x0d, 0x26, 0xdf, 0x0c, 0xa1, 0x28, 0xc5, 0x8f, 0x26, 0x92, 0xff, 0xd7, 0x7a, 0x4e, 0x06, 0x74, 0x3e, 0x06, 0x97, 0xf9, 0x7d, 0xeb, 0x8a, 0x3c
2018-03-10 12:45:28.689 Detail,
2018-03-10 12:45:28.689 Info, contrlr, Received reply to FUNC_ID_ZW_GET_RANDOM: true
2018-03-10 12:45:28.689 Detail, Node032,   Expected reply was received
2018-03-10 12:45:28.689 Detail, Node032,   Message transaction complete
2018-03-10 12:45:28.689 Detail,
2018-03-10 12:45:28.689 Detail, contrlr, Removing current message
2018-03-10 12:45:28.690 Detail,
2018-03-10 12:45:28.690 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x02) - FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2018-03-10 12:45:28.749 Detail, contrlr,   Received: 0x01, 0x25, 0x01, 0x02, 0x05, 0x08, 0x1d, 0x11, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x00, 0xdd
2018-03-10 12:45:28.749 Detail,
2018-03-10 12:45:28.749 Info, mgr,     Driver with Home ID of 0x00000000 is now ready.
2018-03-10 12:45:28.749 Info,
2018-03-10 12:45:28.750 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_INIT_DATA:
2018-03-10 12:45:28.750 Info, contrlr,     Node 001 - New
2018-03-10 12:45:28.750 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2018-03-10 12:45:28.750 Detail, Node001, QueryStage_ProtocolInfo
2018-03-10 12:45:28.750 Detail, Node001, Queuing (Query) Get Node Protocol Info (Node=1): 0x01, 0x04, 0x00, 0x41, 0x01, 0xbb
2018-03-10 12:45:28.750 Detail, Node001, Queuing (Query) Query Stage Complete (ProtocolInfo)
2018-03-10 12:45:28.750 Info, Node001, Initializing Node. New Node: false (false)
2018-03-10 12:45:28.750 Info, contrlr,     Node 005 - New
2018-03-10 12:45:28.750 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2018-03-10 12:45:28.750 Detail, Node005, QueryStage_ProtocolInfo
2018-03-10 12:45:28.751 Detail, Node005, Queuing (Query) Get Node Protocol Info (Node=5): 0x01, 0x04, 0x00, 0x41, 0x05, 0xbf
2018-03-10 12:45:28.751 Detail, Node005, Queuing (Query) Query Stage Complete (ProtocolInfo)
2018-03-10 12:45:28.751 Info, Node005, Initializing Node. New Node: false (false)
2018-03-10 12:45:28.751 Detail, Node008,   Expected reply was received
2018-03-10 12:45:28.751 Detail, Node008,   Message transaction complete
2018-03-10 12:45:28.751 Detail,
2018-03-10 12:45:28.751 Detail, contrlr, Removing current message
2018-03-10 12:45:28.751 Detail, contrlr, Notification: DriverReady
2018-03-10 12:45:28.757 Detail, Node001, Notification: NodeNew
2018-03-10 12:45:28.757 Detail, Node001, Notification: NodeAdded
2018-03-10 12:45:28.785 Detail, Node005, Notification: NodeNew
2018-03-10 12:45:28.789 Detail, Node005, Notification: NodeAdded
2018-03-10 12:45:28.831 Detail,
2018-03-10 12:45:28.832 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x06) - FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2018-03-10 12:45:28.834 Detail, contrlr,   Received: 0x01, 0x05, 0x01, 0x06, 0x64, 0x0f, 0x96
2018-03-10 12:45:28.834 Detail,
2018-03-10 12:45:28.834 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_SET_TIMEOUTS
2018-03-10 12:45:28.834 Detail, Node015,   Expected reply was received
2018-03-10 12:45:28.834 Detail, Node015,   Message transaction complete
2018-03-10 12:45:28.834 Detail,
2018-03-10 12:45:28.834 Detail, contrlr, Removing current message
2018-03-10 12:45:28.834 Detail,
2018-03-10 12:45:28.834 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x00) - FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2018-03-10 12:45:28.836 Detail, contrlr, Removing current message
2018-03-10 12:45:28.836 Detail,
2018-03-10 12:45:28.836 Info, Node001, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=1): 0x01, 0x04, 0x00, 0x41, 0x01, 0xbb
2018-03-10 12:45:28.839 Detail, Node001,   Received: 0x01, 0x09, 0x01, 0x41, 0x93, 0x16, 0x01, 0x02, 0x02, 0x01, 0x33
2018-03-10 12:45:28.839 Detail,
2018-03-10 12:45:28.839 Info, Node001, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2018-03-10 12:45:28.839 Info, Node001,   Protocol Info for Node 1:
2018-03-10 12:45:28.839 Info, Node001,     Listening     = true
2018-03-10 12:45:28.839 Info, Node001,     Beaming       = true
2018-03-10 12:45:28.839 Info, Node001,     Routing       = false
2018-03-10 12:45:28.839 Info, Node001,     Max Baud Rate = 40000
2018-03-10 12:45:28.839 Info, Node001,     Version       = 4
2018-03-10 12:45:28.839 Info, Node001,     Security      = false
2018-03-10 12:45:28.857 Info, Node001,   Basic device class    (0x02) - Static Controller
2018-03-10 12:45:28.857 Info, Node001,   Generic device Class  (0x02) - Static Controller
2018-03-10 12:45:28.857 Info, Node001,   Specific device class (0x01) - Static PC Controller
2018-03-10 12:45:28.857 Info, Node001,     COMMAND_CLASS_BASIC is not mapped
2018-03-10 12:45:28.858 Info, Node001,   Mandatory Command Classes for Node 1:
2018-03-10 12:45:28.858 Info, Node001,     None
2018-03-10 12:45:28.858 Info, Node001,   Mandatory Command Classes controlled by Node 1:
2018-03-10 12:45:28.858 Info, Node001,     COMMAND_CLASS_BASIC
2018-03-10 12:45:28.859 Detail, Node022,   Expected reply was received
2018-03-10 12:45:28.859 Detail, Node022,   Message transaction complete
2018-03-10 12:45:28.859 Detail,
2018-03-10 12:45:28.859 Detail, Node001, Removing current message
2018-03-10 12:45:28.859 Detail, Node001, Notification: NodeProtocolInfo
2018-03-10 12:45:28.871 Detail, Node001, Notification: ValueAdded
2018-03-10 12:45:28.879 Detail, Node001, Query Stage Complete (ProtocolInfo)
2018-03-10 12:45:28.879 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2018-03-10 12:45:28.879 Detail, Node001, QueryStage_Probe
2018-03-10 12:45:28.879 Info, Node001, NoOperation::Set - Routing=true
2018-03-10 12:45:28.879 Detail, Node001, Queuing (NoOp) NoOperation_Set (Node=1): 0x01, 0x09, 0x00, 0x13, 0x01, 0x02, 0x00, 0x00, 0x25, 0x0a, 0xc9
2018-03-10 12:45:28.879 Detail, Node001, Queuing (Query) Query Stage Complete (Probe)
2018-03-10 12:45:28.880 Detail,
2018-03-10 12:45:28.880 Info, Node001, Sending (NoOp) message (Callback ID=0x0a, Expected Reply=0x13) - NoOperation_Set (Node=1): 0x01, 0x09, 0x00, 0x13, 0x01, 0x02, 0x00, 0x00, 0x25, 0x0a, 0xc9
2018-03-10 12:45:28.881 Warning, Node001, WARNING: NAK received...triggering resend
2018-03-10 12:45:28.882 Error, Node001, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:28.882 Detail, Node001, Removing current message
2018-03-10 12:45:28.882 Detail,
2018-03-10 12:45:28.882 Info, Node005, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=5): 0x01, 0x04, 0x00, 0x41, 0x05, 0xbf
2018-03-10 12:45:28.885 Detail, Node005,   Received: 0x01, 0x09, 0x01, 0x41, 0xd3, 0x9c, 0x01, 0x04, 0x10, 0x01, 0xed
2018-03-10 12:45:28.885 Detail,
2018-03-10 12:45:28.885 Info, Node005, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2018-03-10 12:45:28.885 Info, Node005,   Protocol Info for Node 5:
2018-03-10 12:45:28.885 Info, Node005,     Listening     = true
2018-03-10 12:45:28.885 Info, Node005,     Beaming       = true
2018-03-10 12:45:28.885 Info, Node005,     Routing       = true
2018-03-10 12:45:28.885 Info, Node005,     Max Baud Rate = 40000
2018-03-10 12:45:28.885 Info, Node005,     Version       = 4
2018-03-10 12:45:28.885 Info, Node005,     Security      = false
2018-03-10 12:45:28.885 Info, Node005,   Basic device class    (0x04) - Routing Slave
2018-03-10 12:45:28.885 Info, Node005,   Generic device Class  (0x10) - Binary Switch
2018-03-10 12:45:28.886 Info, Node005,   Specific device class (0x01) - Binary Power Switch
2018-03-10 12:45:28.886 Info, Node005,     COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_SWITCH_BINARY
2018-03-10 12:45:28.886 Info, Node005,   Mandatory Command Classes for Node 5:
2018-03-10 12:45:28.886 Info, Node005,     COMMAND_CLASS_BASIC
2018-03-10 12:45:28.886 Info, Node005,     COMMAND_CLASS_SWITCH_BINARY
2018-03-10 12:45:28.886 Info, Node005,     COMMAND_CLASS_SWITCH_ALL
2018-03-10 12:45:28.886 Info, Node005,   Mandatory Command Classes controlled by Node 5:
2018-03-10 12:45:28.887 Info, Node005,     None
2018-03-10 12:45:28.887 Detail, Node156,   Expected reply was received
2018-03-10 12:45:28.887 Detail, Node156,   Message transaction complete
2018-03-10 12:45:28.887 Detail,
2018-03-10 12:45:28.887 Detail, Node005, Removing current message
2018-03-10 12:45:28.887 Detail, Node005, Notification: NodeProtocolInfo
2018-03-10 12:45:28.889 Detail, Node005, Notification: ValueAdded
2018-03-10 12:45:28.951 Detail, Node005, Notification: ValueAdded
2018-03-10 12:45:28.954 Detail, Node005, Query Stage Complete (ProtocolInfo)
2018-03-10 12:45:28.954 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2018-03-10 12:45:28.955 Detail, Node005, QueryStage_Probe
2018-03-10 12:45:28.955 Info, Node005, NoOperation::Set - Routing=true
2018-03-10 12:45:28.955 Detail, Node005, Queuing (NoOp) NoOperation_Set (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x00, 0x00, 0x25, 0x0b, 0xcc
2018-03-10 12:45:28.955 Detail, Node005, Queuing (Query) Query Stage Complete (Probe)
2018-03-10 12:45:28.955 Detail,
2018-03-10 12:45:28.955 Info, Node005, Sending (NoOp) message (Callback ID=0x0b, Expected Reply=0x13) - NoOperation_Set (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x00, 0x00, 0x25, 0x0b, 0xcc
2018-03-10 12:45:28.963 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-03-10 12:45:28.963 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2018-03-10 12:45:33.044 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x0b, 0x01, 0x01, 0x99, 0x79
2018-03-10 12:45:33.044 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x0b received (expected 0x0b)
2018-03-10 12:45:33.044 Info, Node005, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2018-03-10 12:45:33.044 Warning, Node005, WARNING: Device is not a sleeping node.
2018-03-10 12:45:33.044 Info, Node005, QueryStageRetry stage Probe requested stage Probe max 3 retries 0 pending 1
2018-03-10 12:45:33.045 Detail, Node001,   Expected callbackId was received
2018-03-10 12:45:33.045 Detail, Node001,   Expected reply was received
2018-03-10 12:45:33.045 Detail, Node001,   Message transaction complete
2018-03-10 12:45:33.045 Detail,
2018-03-10 12:45:33.045 Detail, Node005, Removing current message
2018-03-10 12:45:33.045 Detail, Node005, Notification: Notification - NoOperation
2018-03-10 12:45:33.047 Detail, Node001, Query Stage Complete (Probe)
2018-03-10 12:45:33.047 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=WakeUp live=1
2018-03-10 12:45:33.048 Detail, Node001, QueryStage_WakeUp
2018-03-10 12:45:33.048 Detail, Node001, QueryStage_ManufacturerSpecific1
2018-03-10 12:45:33.048 Detail, Node001, Checking for ManufacturerSpecific CC and Requesting values if present on this node
2018-03-10 12:45:33.048 Detail, Node001, QueryStage_NodeInfo
2018-03-10 12:45:33.048 Detail, Node001, Queuing (Query) Request Node Info (Node=1): 0x01, 0x04, 0x00, 0x60, 0x01, 0x9a
2018-03-10 12:45:33.048 Detail, Node001, Queuing (Query) Query Stage Complete (NodeInfo)
2018-03-10 12:45:33.048 Detail, Node005, Query Stage Complete (Probe)
2018-03-10 12:45:33.048 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=1 queryStage=Probe live=1
2018-03-10 12:45:33.048 Detail, Node005, QueryStage_Probe
2018-03-10 12:45:33.048 Info, Node005, NoOperation::Set - Routing=true
2018-03-10 12:45:33.048 Detail, Node005, Queuing (NoOp) NoOperation_Set (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x00, 0x00, 0x25, 0x0c, 0xcb
2018-03-10 12:45:33.048 Detail, Node005, Queuing (Query) Query Stage Complete (Probe)
2018-03-10 12:45:33.049 Detail,
2018-03-10 12:45:33.049 Info, Node005, Sending (NoOp) message (Callback ID=0x0c, Expected Reply=0x13) - NoOperation_Set (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x00, 0x00, 0x25, 0x0c, 0xcb
2018-03-10 12:45:33.056 Warning, WARNING: Out of frame flow! (0x04).  Sending NAK.
2018-03-10 12:45:33.059 Detail, Unsolicited message received while waiting for ACK.
2018-03-10 12:45:33.559 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2018-03-10 12:45:33.560 Detail, Unsolicited message received while waiting for ACK.
2018-03-10 12:45:34.060 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2018-03-10 12:45:35.060 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:35.062 Detail, Node005, Removing current message
2018-03-10 12:45:35.063 Detail, Node005, Notification: Notification - TimeOut
2018-03-10 12:45:35.065 Detail,
2018-03-10 12:45:35.065 Info, Node001, Sending (Query) message (Callback ID=0x00, Expected Reply=0x49) - Request Node Info (Node=1): 0x01, 0x04, 0x00, 0x60, 0x01, 0x9a
2018-03-10 12:45:36.065 Error, Node001, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:36.065 Detail, Node001, Removing current message
2018-03-10 12:45:36.066 Detail, Node001, Notification: Notification - TimeOut
2018-03-10 12:45:36.068 Detail, Node001, Query Stage Complete (NodeInfo)
2018-03-10 12:45:36.068 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodePlusInfo live=1
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_NodePlusInfo
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_SecurityReport
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_ManufacturerSpecific2
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_Versions
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_Instances
2018-03-10 12:45:36.068 Info, Node001, Essential node queries are complete
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_Static
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_Associations
2018-03-10 12:45:36.068 Detail, Node001, QueryStage_Neighbors
2018-03-10 12:45:36.069 Detail, Requesting routing info (neighbor list) for Node 1
2018-03-10 12:45:36.069 Detail, Node001, Queuing (Command) Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00, 0x00, 0x03, 0x7a
2018-03-10 12:45:36.069 Detail, Node001, Queuing (Query) Query Stage Complete (Neighbors)
2018-03-10 12:45:36.069 Detail, Node001, Notification: EssentialNodeQueriesComplete
2018-03-10 12:45:36.069 Detail,
2018-03-10 12:45:36.069 Info, Node001, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00, 0x00, 0x03, 0x7a
2018-03-10 12:45:37.070 Error, Node001, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:37.070 Detail, Node001, Removing current message
2018-03-10 12:45:37.070 Detail, Node001, Notification: Notification - TimeOut
2018-03-10 12:45:37.072 Detail, Node005, Query Stage Complete (Probe)
2018-03-10 12:45:37.072 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=0 queryStage=WakeUp live=1
2018-03-10 12:45:37.072 Detail, Node005, QueryStage_WakeUp
2018-03-10 12:45:37.073 Detail, Node005, QueryStage_ManufacturerSpecific1
2018-03-10 12:45:37.073 Detail, Node005, Checking for ManufacturerSpecific CC and Requesting values if present on this node
2018-03-10 12:45:37.073 Detail, Node005, QueryStage_NodeInfo
2018-03-10 12:45:37.073 Detail, Node005, Queuing (Query) Request Node Info (Node=5): 0x01, 0x04, 0x00, 0x60, 0x05, 0x9e
2018-03-10 12:45:37.073 Detail, Node005, Queuing (Query) Query Stage Complete (NodeInfo)
2018-03-10 12:45:37.073 Detail, Node001, Query Stage Complete (Neighbors)
2018-03-10 12:45:37.073 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2018-03-10 12:45:37.073 Detail, Node001, QueryStage_Session
2018-03-10 12:45:37.073 Detail, Node001, QueryStage_Dynamic
2018-03-10 12:45:37.073 Detail, Node001, QueryStage_Configuration
2018-03-10 12:45:37.073 Detail, Node001, QueryStage_Complete
2018-03-10 12:45:37.073 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2018-03-10 12:45:37.073 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0
2018-03-10 12:45:37.073 Detail, Node001, Notification: NodeQueriesComplete
2018-03-10 12:45:37.075 Detail,
2018-03-10 12:45:37.076 Info, Node005, Sending (Query) message (Callback ID=0x00, Expected Reply=0x49) - Request Node Info (Node=5): 0x01, 0x04, 0x00, 0x60, 0x05, 0x9e
2018-03-10 12:45:38.076 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:38.076 Detail, Node005, Removing current message
2018-03-10 12:45:38.076 Detail, Node005, Notification: Notification - TimeOut
2018-03-10 12:45:38.084 Detail, Node005, Query Stage Complete (NodeInfo)
2018-03-10 12:45:38.084 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodePlusInfo live=1
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_NodePlusInfo
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_SecurityReport
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_ManufacturerSpecific2
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_Versions
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_Instances
2018-03-10 12:45:38.084 Info, Node005, Essential node queries are complete
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_Static
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_Associations
2018-03-10 12:45:38.084 Detail, Node005, QueryStage_Neighbors
2018-03-10 12:45:38.084 Detail, Requesting routing info (neighbor list) for Node 5
2018-03-10 12:45:38.084 Detail, Node005, Queuing (Command) Get Routing Info (Node=5): 0x01, 0x07, 0x00, 0x80, 0x05, 0x00, 0x00, 0x03, 0x7e
2018-03-10 12:45:38.085 Detail, Node005, Queuing (Query) Query Stage Complete (Neighbors)
2018-03-10 12:45:38.085 Detail, Node005, Notification: EssentialNodeQueriesComplete
2018-03-10 12:45:38.088 Detail,
2018-03-10 12:45:38.089 Info, Node005, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=5): 0x01, 0x07, 0x00, 0x80, 0x05, 0x00, 0x00, 0x03, 0x7e
2018-03-10 12:45:39.089 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:39.089 Detail, Node005, Removing current message
2018-03-10 12:45:39.089 Detail, Node005, Notification: Notification - TimeOut
2018-03-10 12:45:39.091 Detail, Node005, Query Stage Complete (Neighbors)
2018-03-10 12:45:39.091 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2018-03-10 12:45:39.092 Detail, Node005, QueryStage_Session
2018-03-10 12:45:39.092 Detail, Node005, Queuing (Query) SwitchAllCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x27, 0x02, 0x25, 0x0d, 0xef
2018-03-10 12:45:39.092 Detail, Node005, Queuing (Query) Query Stage Complete (Session)
2018-03-10 12:45:39.092 Detail,
2018-03-10 12:45:39.092 Info, Node005, Sending (Query) message (Callback ID=0x0d, Expected Reply=0x04) - SwitchAllCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x27, 0x02, 0x25, 0x0d, 0xef
2018-03-10 12:45:40.092 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:40.092 Detail, Node005, Removing current message
2018-03-10 12:45:40.093 Detail, Node005, Notification: Notification - TimeOut
2018-03-10 12:45:40.095 Detail, Node005, Query Stage Complete (Session)
2018-03-10 12:45:40.095 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2018-03-10 12:45:40.095 Detail, Node005, QueryStage_Dynamic
2018-03-10 12:45:40.095 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x0e, 0xee
2018-03-10 12:45:40.095 Detail, Node005, Queuing (Query) Query Stage Complete (Dynamic)
2018-03-10 12:45:40.095 Detail,
2018-03-10 12:45:40.095 Info, Node005, Sending (Send) message (Callback ID=0x0e, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x0e, 0xee
2018-03-10 12:45:41.096 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-03-10 12:45:41.096 Detail, Node005, Removing current message
2018-03-10 12:45:41.096 Detail, Node005, Notification: Notification - TimeOut
2018-03-10 12:45:41.098 Detail, Node005, Query Stage Complete (Dynamic)
2018-03-10 12:45:41.098 Detail, Node005, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2018-03-10 12:45:41.098 Detail, Node005, QueryStage_Configuration
2018-03-10 12:45:41.098 Detail, Node005, QueryStage_Complete
2018-03-10 12:45:41.098 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2018-03-10 12:45:41.099 Warning, CheckCompletedNodeQueries all=1, deadFound=0 sleepingOnly=1
2018-03-10 12:45:41.099 Info,          Node query processing complete.
2018-03-10 12:45:41.099 Detail, Node005, Notification: NodeQueriesComplete
2018-03-10 12:45:41.101 Detail, contrlr, Notification: AllNodesQueried

Sorry, I don’t know anything about that controller.

No. OpenZWave is already in HASS.

No? I didn’t see in your log where it WASN’T working?

If someone could please explain to me how I can figure out what is needed in oder to construct my docker-compose.yaml file, I would greatly appreciate it. I was able to get HA, Ha-dockermon and Portainer installed thanks to the examples above.

Now I would like to install Samba, SSH, Configurator and different others from this site: https://hub.docker.com/u/homeassistant/ but when I click details, none of them will list what is required to place in my compose file. How do I come up with a valid configuration?

Lastly, is there a proper way to either shutdown or reboot your pi in a docker environment? Is there anything to shutdown first on the docker side of things. Also do I hear correctly that to upgrade to a new version of HA, the only thing I need is to delete the existing container (through Protainer) and restart docker-compose up -d?

Thanks

You can view the GitHub pages on the hassio stuff to see how their composing the containers, but those things are all hassio and probably require the hassio framework to work.

Why not just do it yourself with some docker containers?

Sudo reboot or sudo poweroff.

Shouldn’t be anything special you need to do.

You can do docker-compose down then docker-compose pull , and lastly, docker-compose up -d

So I assume that you are referring to other Docker containers that are not really specific to HA? I can surely look into that. I just thought that these were built to work closely with Home Assistant. Still I need to figure out how Configurator works.

I would have thought that will all the pulls that were listed that we would have seen a whole lot more questions on this board on the setup.

THanks for your replies, this is very helpful!

Yep!

They’re built specifically for hassio.

:+1:

I didn’t log while I was doing things like “Add Node”, etc.

Got Z-Wave finally working by installing Z-Way using this script
wget -q -O - razberry.z-wave.me/install | sudo bash
from https://z-wave.me/z-way/download-z-way/.

Guess there were some dependencies missing to get the RaZberry board working. But I am not sure.

Since the Raspberry images are not part of the automatic build process and currently are lacking actuality (still at 0.65.0), I’d like to get a assistence on how to build my own RPi3 images which match the configuration of the “official” homeassistant/raspberrypi3-homeassistant image.

Check the dockerfile of the official build. I checked the rpi-image once inside the container and it’s based on alpine contrary to the x86 build. And on top of that you can check the build layers of an image with portainer. Gives you an overview of the dependencies you need. Check out resin’s doc if you’re interested in auto builds.