Hassio Docker

这货是 github 2020年推出的 docker 镜像托管服务 众所周知,国内链接 github 多难基本下载只有 50KB左右,而且国内也没有针对 ghcr.io 的加速镜像,所以要么忍一下,等国内阿里云等建好 ghcr.io 的加速源,要么就逐步抛弃 supervisor 吧。. D /home/user/docker/hassio - Optional but I strongly recommend that you list a known path to store HASS.io data. The path listed here is just an example. The path listed here is just an example. Upon successful execution of the HASS.io Docker installation script, the output should look something similar to the one below.

Zigbee2MQTT uses zigbee-herdsman-converters to parse messages to and from devices.

This page will guide you through the process of adding support for new devices to zigbee-herdsman-converters.

In case you require any help feel free to create an issue.

Before starting, first check if you devices is not already supported in the Zigbee2MQTT dev branch! This can be done by searching on your Zigbee model (see step 1 below) in any of the files here.

  1. This profile does not have any public repositories. Overview What is a Container. Product Overview. Product Offerings.
  2. When I was on 5mbps internet, it took nearly an hour to get the home assistant docker image. From the installation page you linked to and said you followed: If your router doesn’t support mDNS, then you’ll have to use the IP address of your Pi instead of hassio.local.

Instructions #

1. Pairing the device with Zigbee2MQTT #

The first step is to pair the device with Zigbee2MQTT. It should be possible to pair your unsupported device out of the box because Zigbee2MQTT can pair with any zigbee device. You need to find out how to bring your device into pairing mode, most of the time via a factory reset.

Once you successfully paired the device you will see something like:

NOTE: Make sure that permit_join: true is set in configuration.yaml otherwise new devices cannot join the network.

2. Adding your device #

The next step is to create an external converter file. This file has to be created next to the configuration.yaml, in this example we will call it WSDCGQ01LM.js (make sure it ends with .js). In order to provide support for e.g. the lumi.sens from step 1 we would add the following to this file:

Hassio Docker Install

If your device is advertised as “Tuya compatible” and/or requires Tuya gateway/app to operate look here for additional info

Now set the Zigbee2MQTT log_level to debug and enable the external converter by adding the following to your Zigbee2MQTT configuration.yaml.

Once finished, restart Zigbee2MQTT and trigger some actions on the device. You will see messages like:

In case your device is not reporting anything, it could be that this device requires additional configuration. This can be done by adding a configure: section. It may help to look at similar devices.

If your device reports anything with ‘manuSpecificTuya’ then it’s a “Tuya compatible” device and additional instructions for adding those are here.

Hassio docker install

Some basic external converter examples:

  • Definitions of already supported devices can be found here. It may help to look at devices from the same vendor or type.

3. Adding converter(s) for your device #

In order to parse the messages of your Zigbee device we need to add converter(s). Probably existing converters can be reused, those can be found here.

Docker

For E.G. the following message we could use the already existing fz.temperature converter:

Now update your external converter.

Hassio

Hassio Docker Raspberry Pi

Repeat until your device does not produce any more log messages like: 2018-5-1 18:19:41 WARN No converter available for 'WSDCGQ01LM' with....

In case you need to add custom converters you can find an external converter example here.

3.1 Retrieving color temperature range (only required for lights which support color temperature) #

If your device is a light and supports color temperature you need to define the color temperature range. This range indicates the minimum and maximum color temperature value the light supports. This can be retrieved from the light by sending to zigbee2mqtt/DEVICE_FRIENDLY_NAME/set with payload {'read': {'cluster': 'lightingColorCtrl', 'attributes': ['colorTempPhysicalMin', 'colorTempPhysicalMax']}}

The result will be logged to the Zigbee2MQTT log, e.g.

In the above example set colorTempRange to {colorTempRange: [153, 500]}, e.g.:

In case none of the existing converters fit you can add custom ones, external converter example for this can be found here.

4. (Optional) Add device to zigbee2mqtt.io documentation #

This step is optional and can be skipped as the device page will automatically be generated on the next Zigbee2MQTT release. Only do it when you e.g. want to a specific pairing instructions for this device.

  1. Clone zigbee2mqtt.io
  2. Add a markdown file for your device to docs/devices, use the model property of your definition as the filename.
  3. Add a picture (.jpg, 150x150) to docs/images/devices and link it in file of the previous step.
  4. Create a Pull Request to zigbee2mqtt.io.

On the next release of Zigbee2MQTT, the documentation will be updated and your device file will be linked in docs/information/supported_devices.md automatically.

5. Done! #

Now it’s time to submit a pull request to zigbee-herdsman-converters so this device is supported out of the box by Zigbee2MQTT. This can be done by adding the definition to the vendor file of your device. :smiley:

In this post we’re going to take a look at the easiest way to evaluate Home Assistant on a PC. In the end, we’ll have a fully operational copy of Home Assistant (Hass.io flavor), which is accessible via browser in your home network.

Terminology

  • Home Assistant (HA) - a top ten’s fastest-growing open-source project (as of 2019) of home automation system written on Python language. It carries on a huge number of components to integrate with the most if not all devices and services on the market
  • Guest - a Virtual Machine with Home Assistant installed
  • Host - a computer with Microsoft Windows/Linux/macOS, with Oracle VirtualBox installed

Hass.io - the framework consisting of a few Docker containers which make it easier to install and upgrade Home Assistant and allows you to install tenths of Hass.io addons literally in a mouse click.

The screenshots below were taken from macOS version of Oracle VirtualBox, though it should work the same way in other operating systems like Windows or Linux.

Step 1: Install Oracle VirtualBox and Use an Official Hass.io Image

First of all, we need to download an installation package for your OS here and install it. Then go to Home Assistant site and pick up an official VM image, the one you want is “VDI”.

Create a new VM (guest) in Oracle VirtualBox, specify Linux 64 bit as “OS Type” and allocate 2-4 Gb of RAM for better performance.

Choose your downloaded VM image in the guest’s storage settings:

Finish the creation wizard, but don’t start your guest yet.

Step 2: Set Up The Virtual Machine

To access Home Assistant UI, we have to adjust the network settings of our guest. Open the Settings and change Network settings so that the guest uses Bridged Adapter instead of NAT:

Another important setting is to Enable EFI in the System tab. Without it your guest will not be able to boot:

Step 3: Run It

Start your guest and open the following URL in your browser: http://xx.xx.xx.xx:8123, where хх.xx.xx.xx is the IP address, assigned to your guest. If you don’t know it, the easiest way is to check the list of devices in your home router/access point settings. If your hardware is not up-to-date, the first boot process may take a few minutes as it includes download and install of recent Hass.io image from the net.

Step 4: Using Hass.io Command Line

Since you have access to the guest console, you may also ssh to the Hass.io command line. One has to realize that this is not the full access to the host OS command line. Instead, this is Hass.io command line toolset which is running inside a container.

Hassio Docker Image

In order to access it, open the guest console and hit Enter to see the welcome prompt:

Type root and press Enter to login to the Hass.io.

Hassio Docker Raspberry Pi 4

Try to type help to get the list of available commands. You may also edit the configuration file of your Home Assistant instance by the following command:

Hassio Docker Swarm

To leave the editor, Ctrl+x hotkey can be used.