feat: Wire bunq2ynab in provisioner

[mvgijssel]

ref #451

TODO

• Cache current platform image from regctl
• Remove minikube from provisioner + tests (also from remote)
• Install sudo into the provisioner docker container (previously done with rules_docker).
• Wire bunq2ynab version into provisioner deploy (use env specific group variables to load in the remote_tags)
• Make the image sleep for 5 minutes before exiting (after being restarted always)
• Add provisioner tests
• Make sure the test works with a local version of the container (that way can test new changes immediately inside provisioner?)
• Limit scope of bunq dev token
• Make the image private
• Store dev image inside separate package
• Create provisioner release
• Only deploy provisioner if the provisioner version updated (this makes sure all release assets are ready before deploying and enables selective delivery)
• Generate changesets
• Fix provisioner not being available?

[mvgijssel]

Remove bridge device and use regular dhcp on eno1 interface:

maarten@hypervisor:~$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
    eno1:
      dhcp4: no
      addresses: [192.168.1.30/24]
      gateway4: 192.168.1.1
      nameservers:
        addresses: [192.168.1.1]

Following https://github.com/home-assistant-libs/python-matter-server set following flags:

sudo sysctl -w net.ipv6.conf.eno1.accept_ra=1
sudo sysctl -w net.ipv6.conf.eno1.accept_ra_rt_info_max_plen=64

From home-assistant-libs/python-matter-server#296 (comment) configure systemd-networkd as follows

root@hypervisor:/data/home-assistant# cat /etc/systemd/network/01-accept-ra.network
[Match]
Name=eno*

[Network]
DHCP=yes
IPv6AcceptRA=true
root@hypervisor:/data/home-assistant#

and run systemctl enable systemd-networkd.

1. Setting the homekit eve motion device in pairing mode
2. Copying the configuration code
3. Opening Home Assistant iOS app
4. Add matter device
5. Click on more options
6. Paste in the configuration code
7. Wait and the matter server gives the following logs:

matter-server  | 2023-12-14 08:16:29 hypervisor chip.CTL[1] ERROR Commissioning discovery over BLE failed: src/platform/Linux/BLEManagerImpl.cpp:687: CHIP Error 0x00000003: Incorrect state
matter-server  | 2023-12-14 08:16:29 hypervisor chip.-[1] ERROR src/platform/Linux/BLEManagerImpl.cpp:687: CHIP Error 0x00000003: Incorrect state at src/controller/SetUpCodePairer.cpp:324
matter-server  | 2023-12-14 08:16:29 hypervisor chip.BLE[1] ERROR No adapter available for new connection establishment
matter-server  | 2023-12-14 08:16:40 hypervisor PersistentStorage[1] INFO SetSdkKey:...
matter-server  | 2023-12-14 08:16:40 hypervisor PersistentStorage[1] INFO Committing...
matter-server  | 2023-12-14 08:16:40 hypervisor PersistentStorage[1] INFO SetSdkKey:  ...
matter-server  | 2023-12-14 08:16:40 hypervisor PersistentStorage[1] INFO Committing...
matter-server  | 2023-12-14 08:16:40 hypervisor PersistentStorage[1] INFO SetSdkKey: ...
matter-server  | 2023-12-14 08:16:40 hypervisor PersistentStorage[1] INFO Committing...
matter-server  | 2023-12-14 08:16:49 hypervisor matter_server.server.client_handler[1] WARNING [139740365198480] Disconnected: Received non-Text message.
matter-server  | 2023-12-14 08:16:55 hypervisor matter_server.server.device_controller.[node 1][1] INFO Subscription succeeded
matter-server  | 2023-12-14 08:17:00 hypervisor matter_server.server.device_controller.[node 1][1] INFO Subscription succeeded

Pairing works, but seems the hypervisor machine is missing bluetooth.