#Raspberry pi light logger update
#Raspberry pi light logger windows

Gas meter logging using reed switch on meter and new logging / counter board which will interface with the Raspberry PiДЄdditional mains current sensors on each fuse so we can log the current consumption on each circuit. Gas boiler running sensor using a flame detector

#Raspberry pi light logger windows

We are now planning to include the following additional sensors and upgradesДЇull central heating control via the Cental Heating Control via Windows Phone and Raspberry Pi project and new interface and back end to use the Raspberry Pi to control the central heating boiler times and settings.

Temperature sensor on thermal solar panel output pipe.

Temperature sensor on water cylinder base.

Temperature sensor on water cylinder top.

DC Current on battery to distribution fuse box.

The current system comprises of the following sensors:

#Raspberry pi light logger update

We are now planning to build a new energy logging system using the Raspberry Pi to process and upload the data and also store a local copy on a mySql database to enable an Android tablet in the house to easily view the data and also update the central heating system timer settings. Note: in some threads or documentation pages (I donвЂ™t remember) you can find that is enough to log defining a logger for but that does not work since the KNX libraries does not use common conventions for logger names.It has now been a year since the first Raspberry Pi solar data logger was launched and over the past 12 months it has been running continuously uploading data from our sensors to our online reporting site at every minute. If you keep an eye on that file using tail, you can see all messages from the bus. Where you find other RollingFile appenders.ДЄll that creates new file in the /var/log/openhab folder named knx.log.

Not exactlyвЂ¦ anyway I finally worked out to have everything logged out of the KNX traffic and internal events.Д®dit the file /var/lib/openhab/etc/log4j2.xml and add: To try to find our what was not working, being openHAB written in Java and using slf4j, I hoped my 20 years in Java development could have helped me. Be aware of this different since I have not found that documented (so I lose a lot of time trying to set openHAB to use the port 6720).Д¬onfiguring knxd is still something of magic to me, so I donвЂ™t share my configuration since it is just as I left it when it started to work! Enabling logging OpenHAB can connect only with UDP, while knxtool uses TCP. UDP is on port 3671 while TCP is on port 6720. Knxd can be configured to listen as UDP and as TCP. As soon as I changed the KNX address in openHAB to a different address (3.1.1 вЂ“ absolutely random) everything started to work. In short: the openHAB KNX/IP Gateway was configured with the same address set on kndx deamon configuration (in my case 1.1.128). Sending the identical commands with openHAB there was no way to switch the light. The tool installed automatically with the knxd (0.14) package in a вЂњopenHABianвЂќ distribution.

The problem was this: using the knxtool from a Raspberry Pi, I was able to turn on and off a light. IвЂ™m using an USB device to connect the Rapsberry Pi to the automation bus. This notes are not necessarily connected to the home automation by Vimar, but IвЂ™ve faced the problem with this kind of bus. Playing with those tools is a good way to get crazy but is even funny, after all.