My first vlan setup brought isolated networks for both wired and wireless clients, at the cost of having a dedicated ssid per vlan.

As each ssid takes a bit of bandwidth, this didn’t scale and as I renewed some of my equipment, I took the opportunity to try something else :

ssid1: 802.1x with mikrotik user-manager as radius server to authenticate and assign vlans

ssid2: wpa2-psk with mikrotik user-manager in the background to assign per mac address vlans

I am slowly bringing floor heating to some rooms, and decided I would use a kincony a8 board to pilot the valves for the different circuits.

So I got this board and was not sure where to start. I found this link which was simple enough to give it a try.

It worked nicely, although this was actually aimed at esphome integration, which is not (yet) what I want. I would rather see how far I can get with an isolated solution, not depending on my homeassistant setup.

Setting up a minimal configuration on a Mikrotik device sometime requires a subtle sequence where access method changes so as to avoid cutting the branch you’re sitting on.

Layer 2 connection

I’ve often found mactelnet to work when winbox would not, so don’t forget to give it a try.

sudo mactelnet AA::BB:CC:DD:EE  -n  -u admin -p ""

Wifi connection

Sometime a wifi setup can give a more stable connection when changing vland and bridge settings :

Context

• cheap noname adapter with EFR32MG21 chip

• comes with a deprecated (from zigbee2mqtt’s pov) firmware that works with this setup :

serial:
  port: /dev/zigbee2mqtt      # Use the correct serial port (or create a udev rule for a persistent symlink)
  adapter: ezsp               # Specify the new EFR32MG21 adapter (EZSP protocol)

However, zigbee2mqtt logs about deprecation and missing features. Was this a waster of money on a doomed electronic crap ? Maybe not…

• pigallery2

• used the source
• set node version with asdf

/opt/pigallery2 :

asdf local nodejs 18.20.0

And edited the systemd service to load asdf

ExecStart=/bin/bash -c '. /home/mikael/.asdf/asdf.sh && npm start'
WorkingDirectory=/opt/pigallery2

• phockup : follow the doc at https://github.com/ivandokov/phockup

But also do like this:

python -m venv .
source bin/activate

change shebang towards #!/opt/phockup/bin/python3

read the docs : https://www.home-assistant.io/installation/linux

• stop service

• with same python version

1cd homeassistant
2source bin/activate
3pip install --upgrade homeassistant

• with new python version

1mv homeassistant homeassistant-oldpython
2
3mkdir homeassistant & cd homeassistant
4asdf install python 3.12.5
5asdf local python 3.12.5
6
7python -m venv .
8source bin/activate
9pip install homeassistant

• stop services (systemctl | grep zwave)

• do the update

1cd zwave-js-server
2
3git pull origin master
4
5npm install

• restart services

• go to /var/www/monica and read the doc at docs/installation/update.md

• open a shell a www-data

1sudo su www-data -s /bin/bash

• fetch latest branches

1git fetch -a 

• follow the rest of the documentation…