machinehead

My first pi is fully used and has hit production mode where it runs the house and I can't use it as a play toy anymore. It's running Jessie, which is super stable. Guess to move on, I've got a 2nd pi which I've decided to put raspbian stretch and here are some notes of the install because it never really goes as planned. After downloading and running raspi-config to region, etc. apt upgrade failed with hash sum mismatch using the default apt sources.  I tried a few and what worked for me was: deb http://mirror.rise.ph/raspbian/raspbian/ stretch main contrib non-free rpi after apt-get upgrade worked, I went on to install java.  I had some issues as well with  "Error: missing `server' JVM at `/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'."  which was fixed with sudo apt-get purge openjdk-8-jre-headless sudo apt-get install openjdk-8-jre-headless sudo apt-get install openjdk-8-jre Ok, moving on to some software, i prefer a ...

Once everything is merged, the challenge will be to make sure all devices are reported to the correct status. There are 2 main stores of device state in my setup; Domoticz Fibaro Basically we want Domoticz to know the state of the Fibaro devices and also Fibaro to be able to know the state of the domoticz devices. There shouldn't be 2 different master sources of data. As Domoticz seems to be the master controller and other devices, e.g. Philips hue is capable of updating the status in domoticz automatically and homebridge uses the domoticz plugin, I'm going with Domoticz as the master status and everything will just query domoticz for the state. To do this, there need to be a virtual device for each appliance that will be have it's state reported. Domotics support all sorts of virtual device, the more common ones we will use is  Switches Sockets (On/Off) Motion Sensor Contact Sensors Lamps/Dimmer Temperature The full list is located here. https...