Sunday, December 8, 2019

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


Issuing the following command:
sudo hciattach /dev/ttyAMA0 bcm43xx 921600

solves the error till next reboot.