HASSIO on NUC - My Journey

Just restart. That should wipe the additional rules.
Or:

From:

List all commands that were used to create the currently used rules, useful to edit or delete rules.

sudo iptables -S

To delete a specific rule choose a rule from sudo iptables -S and replace -A with -D .

# -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT

sudo iptables -D INPUT -p tcp -m tcp --

I think I know what hapend (?). Basically if I use your tecquique AND keep zerotier client in a pi3 it does have problems with the pi3, its enough to uninstall zerotier one from the pi3 and UNCHECK the device in the zerotier network webui.
If , as I did, you DELETE the device from the zerotier network webui the pi3 disappears entirely from the network, do you know how to get it back?. Nothing I did works

I noticed that when you click DELETE you get this message

ā€œThis marks a member as permanently hidden and banned. Deleted member records are purged from the database after a period of time. To ā€œun-deleteā€ manually add the member.ā€

. (How to ā€œadd the memberā€ back???

What I did is reflash the SD card of the pi3, and NOT install Zerotier on it.

My goal is still accomplished since I can reach the devices at 192.168.1.xxx outside my LAN.

To manually add, just note the Address (10 Digits looks similar to a MAC) and add it to the add manual field in ZeroTier website

Ok, but which address is that? Since I delete that pi3, I do not have that address anymore (?)

For example when you start the Hassio Addon, it shows the address in the Log:

[12:22:04] INFO: ZeroTier node address: XXYY0011ZZ
You can probably see the same when you installed it manually on Linux. Just check the manual or logs when you start it.

very good,thank you

Hi, never mind, the easiest and fastest solution is to delete the zerotier network and redo another one (I think zerotier has a small bug when you delete a member, because you simply canā€™t add it again).

From scratch to fully working it takes 5 minutes at the most.

Great tool, and great instructions, thanks a lot

Some new updatesā€¦ since there is no Hassio Addon available so far for Face/Person Recognition via Camera i decided to first try to install Facebox via docker-compose and get it to run.

This means basically following this guide:

So i logged into my Ubuntu via SSH and created a new folder for facebox where i could add my docker-compose.yml for it:

mkdir facebox
cd facebox
nano docker-compose.yml

In the docker compose i added this:

Important to note:

  1. In contrast to the official guide i do not have ${ YOURKEY } where the key goes.
    This didnt work for me, only the plain key worked.
  2. I added an additional environment attribute to load state (the faces i taught facebox) after every restart since facebox is stateless and does not save anything if your not a premium subscriber.
    (This seems to only work from an web accessible address. I was not able to use filesystem for this.)
  3. Since i already use port 8080 for the unifi addon, i had to switch the listening port to something different. i chose 8083 for it.
  4. I had to use the _noavx version since my CPU seems to not be supported.
version: '3'
services:
  facebox:
    image: machinebox/facebox_noavx
    container_name: facebox
    restart: unless-stopped
    ports:
      - 8083:8080
    environment:
      - MB_KEY=YOURKEY
      - MB_FACEBOX_DISABLE_RECOGNITION=false
      - MB_FACEBOX_STATE_URL=https://myserver.duckdns.org/local/facebox/state/state.facebox

Hassio configuration:

I use this in my configuration.yaml:

image_processing: !include image_processing.yaml

And then for the image_processing.yaml itself:

   - platform: facebox
     ip_address: localhost
     port: 8083
     scan_interval: 10000
     source:
       - entity_id: camera.xiaomilivingroom
         name: FaceBox

I chose the scan_interval of 10000 because of this post:

It makes a lot of sense to me, to only manually trigger the scanning. i.e.: When motion is detected.

I also used the python script robmarkcole posted here to automate the teaching:

For this i created a new facebox folder in my home assistant shared folder and for each person an extra folder with all the images. The script lies in the facebox folder and is simply called via:

python3 teach_facebox.py

After the teaching was done, i simply downloaded the state through the local website: localhost:8083 and added it as state.faceboy to my /config/www/facebox/state folder

Now, after every restart, it automatically load the state back into my facebox.

The automation for scanning and handling of the data i do via Node Red.

1 Like

Forgive me mate, but iā€™m really noob with home assistant. I successful installed facebox, and it works. I was looking around for re-teach faces on restart. How do you add the state downloaded from the facebox frontend as state for facebox?

Nevermind, got it :smiley:

Ok, i still have a problem. The state reloading only works if i manually restart the docker container of facebox, not if i restart the host machine. Why?

I finally got around to test this. And you are right.
I now implemented a new flow in my node-red, that upon restart just uploads the state file to my facebox.
Im using the simple URL method:

POST /facebox/state?url={url}

And then simply add the state file to my config/www folder to reference it in an absolute URL