IObroker in Homematic

Finally, after one year with Homematic IP and Homematic running via a Raspi and the ELV expansion module, I'll try to include more Raspis via iobroker into my automation.

Right now, the role or structure for accessing other Raspis GPios through Homematic IP is not clear to me. However I have the following idea:
Setup will be as follows:
- Rasberrymatic with ELV expansion and iobroker addin --> multihost slave
- Raspberry with some kind of ubuntu and iobroker installed --> multihost master



After some thinking I will got with an Iobroker installation on another PI only to test ioBroker.
Simulatneously I installed debmatic:
https://github.com/alexreinert/debmatic
on that pi and will try to link it to the first homematic as well as iobroker.


Next step with IOBroker on second PI was to install RPI extension as well as Vis.
RPI needs config in Instance Menu. If error with writing to certain block occurs,e.g.:

18309) Cannot evaluate: Filesystem 1K-blocks Used Available Use% Mounted on /dev/mmcblk0p2 7318052 4276676 2701448 62% / /1024

Then you probably need to uncheck the Raspberry Checkbox in RPI Config on IoBroker


Iobroker auf raspi 4 installieren
https://technikkram.net/2019/07/funktioniert-iobroker-auf-neuem-raspberry-pi-4-installieren



Io Broker move to new host:
https://forum.iobroker.net/topic/12365/raspberrypi-defekt-daten-retten/6

Break.

Iobroker went to new Raspi4 because of Memory consumption.

Debmatic ist out of discussion as well as running iobroker on the homematic pi.

Now I'm gonna link Iobroker on PI 1 to homematic on Pi 2 via Network.

Problems with radar2.plugin on Raspi3 Ubuntu:

 After reboot i get:

host.RelayPi1	2020-06-09 21:10:54.654	error	Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:61:11) errno: 19, code: 'ENODEV', syscall: 'bind' }
host.RelayPi1	2020-06-09 21:10:54.653	error	Caught by controller[0]: at process.nextTick (/opt/iobroker/node_modules/@abandonware/noble/lib/noble.js:60:24)
host.RelayPi1	2020-06-09 21:10:54.653	error	Caught by controller[0]: at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
host.RelayPi1	2020-06-09 21:10:54.652	error	Caught by controller[0]: at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
host.RelayPi1	2020-06-09 21:10:54.652	error	Caught by controller[0]: { Error: ENODEV, No such device

Issuing the following command:

sudo hciattach /dev/ttyAMA0 bcm43xx 921600

solves the error till next reboot.

https://www.iobroker.net/#de/documentation/install/linux.md

Nextcloud on Raspi

Installing NextCloud on Raspi @ Home
- Followed that guide here:
https://strobelstefan.org/?p=5790


Ran into the problems:
- mariadb  was only available in Version 10.0 an not 10.1 because of Ubuntu Version 16.1
- mariadb setup was not available as of Version 10.0 --> used mysql command instead
- Error for Setup of letsencrypt-auto because of certbot-auto solved here: https://community.letsencrypt.org/t/certbot-auto-failed-to-complete-had-a-problem-while-installing-python-packages/83697/5
and another fix here:
https://community.letsencrypt.org/t/certbot-auto-broken-in-debian-based-systems/83754
Error was: valueerror too many values to unpack


Nothing helped for me till now.

Last but not least:
Apply the --no-download option to letsencrypt-auto lines around 1000 like in certbot-auto


Debugging:

Obtaining the Client Log File

To obtain the client log file:

1. Open the Nextcloud Desktop Client.
2. Press F12 on your keyboard.

The Log Output window opens.

Errors on raspbian with apache 2.4:
403 Forbidden.

Prior to that  I moved the wwwroot of apache.
For this the following lines have to be in /etc/apache2/apache2.conf:

<Directory /media/newroot/www/>
        Options Indexes FollowSymLinks
        AllowOverride None
        Require all granted

</Directory>

Securing Nextcloud with iptables if bind-adress is more than localhost:

Allowing certain hosts:

iptables -A INPUT -p tcp -s X.X.X.X --dport 3306 -j

Denying all other hosts:

iptables -A INPUT -p tcp --dport 3306 -j DROP

Upgrading to latest certbot package:

https://webdock.io/en/docs/webdock-control-panel/ssl-certificate-guides/upgrading-lets-encrypt-certbot-latest-version-ubuntu