Open Source Home Automation (Raspberry)
-
Those that did try openHAB (and felt it was slow), what version of java did you use? Did changing versions make any difference?
I see that they recommend a very aggressive memory split also, leaving nothing for the GPU on the RPi. That is obviously impossible for those of us that also run the camera module.
Edit: Perhaps someone would be daring enough to try openHAB 2.0 if and when it works:
http://kaikreuzer.blogspot.com/2014/06/openhab-20-and-eclipse-smarthome.html
Includes HABmin, and ...A second major design goal of openHAB 2.x is the optimization for embedded platforms. Although openHAB 1.x works on a Raspberry Pi, it sometimes feels a bit sluggish at startup or with huge installations - this is due to the fact that openHAB had never been specifically optimized for embedded systems and thus uses libraries such as Xtext, which are not meant to be used in constrained environments. In consequence, we will try to provide a minimal openHAB runtime that will work with alternatives or strategies such as pre-compilation etc.
-
Maybe I'll leave the topic a bit, because I don't use raspberry myself but a linux server for my 'brain' so I don't have any problem with 'slowness'.
I tried out openhab and actually likes it now, it is a bit ass to start up the configuration but then you learn it you'll easy put in new stuff. I might do a tutorial later on..But right now I'm looking at the communication between mysensors and openhab and yes I know there is one script written but I was thinking of making a new gateway software for the arduino.
using mqtt protocol that is supported in openhab, and has a arduino library http://knolleary.net/arduino-client-for-mqtt/ ( https://github.com/knolleary/pubsubclient )an alternative to mqtt is to write something completely new using tcp binding or so, but I think its inventing the wheel all over again.
-
Maybe I'll leave the topic a bit, because I don't use raspberry myself but a linux server for my 'brain' so I don't have any problem with 'slowness'.
I tried out openhab and actually likes it now, it is a bit ass to start up the configuration but then you learn it you'll easy put in new stuff. I might do a tutorial later on..But right now I'm looking at the communication between mysensors and openhab and yes I know there is one script written but I was thinking of making a new gateway software for the arduino.
using mqtt protocol that is supported in openhab, and has a arduino library http://knolleary.net/arduino-client-for-mqtt/ ( https://github.com/knolleary/pubsubclient )an alternative to mqtt is to write something completely new using tcp binding or so, but I think its inventing the wheel all over again.
@Damme I use a standard Ethernet gateway for mysensors and convert the mysensors messages using a quite simple Perl script running on my server (also not using RPI, so who cares about performance ;-) ).
This script automatically publishes and subscribes to the mosquito MQTT broker, also running on the server. Works quite well!http://yveaux.blogspot.nl
-
@Damme I use a standard Ethernet gateway for mysensors and convert the mysensors messages using a quite simple Perl script running on my server (also not using RPI, so who cares about performance ;-) ).
This script automatically publishes and subscribes to the mosquito MQTT broker, also running on the server. Works quite well! -
@Yveaux do you want to share? I am still waiting for my ethernet sheild so I cant do much programming there yet but would be fun to try out the mqtt protocol.. :)
@Damme Ok, take a look at https://github.com/Yveaux/MySensors_MQTTGateway
No documentation or getting started yet, no time :-1: Sorry...http://yveaux.blogspot.nl
-
@Damme Ok, take a look at https://github.com/Yveaux/MySensors_MQTTGateway
No documentation or getting started yet, no time :-1: Sorry... -
@hek Thanks! But I really need to start on my blog to document all the stuff I do... I'm afraid it isn't really self-documentary...
@Yveaux I made it work but with lots of changes, first I use serial and not ethernet on the arduino, and then I didnt find the AnyEvent::MQTT, I use Net:MQTT instead. So basically its not much left of your original script, but it was just for testing MQTT a bit.
I think it would direcly in arduino..
-
@Damme Ok, take a look at https://github.com/Yveaux/MySensors_MQTTGateway
No documentation or getting started yet, no time :-1: Sorry...@Yveaux I have the classic one : https://github.com/empierre/domoticz?files=1
but since you're perling I can contribute... and maybe add/create the imperihome rest intetface on top... but You'll have to overcome some isdues related to the absence of UI
z-wave - Vera -> Domoticz
rfx - Domoticz <- MyDomoAtHome <- Imperihome
mysensors -> mysensors-gw -> Domoticz -
@Yveaux I have the classic one : https://github.com/empierre/domoticz?files=1
but since you're perling I can contribute... and maybe add/create the imperihome rest intetface on top... but You'll have to overcome some isdues related to the absence of UI
-
@epierre I'm afraid I don't get you...
So you're on domoticz, and you already have a gateway to mysensors?
Why do you want to switch to MQTT then? -
@Yveaux I made it work but with lots of changes, first I use serial and not ethernet on the arduino, and then I didnt find the AnyEvent::MQTT, I use Net:MQTT instead. So basically its not much left of your original script, but it was just for testing MQTT a bit.
I think it would direcly in arduino..
@Damme I did start with an arduino implementation buy as MQTT is text-based I needed quite some flash to store all the strings to convert the mysensors variable names and stuff.
This filled up my atmega328 almost completely and I got tired of all the trickery required to stay within the 32kb. I just wanted to prove and test the cooperation of my sensors and MQTT.
Then I realized the MQTT broker had to run on a 'heavier' platform anyway and decided that also my gateway could -- I see no use to stuff everything into an arduino.If you're interested I can share the arduino implementation, but I no longer see the use for it.
If your changes improved my implementation then please share them with us :+1:
http://yveaux.blogspot.nl
-
@Damme I did start with an arduino implementation buy as MQTT is text-based I needed quite some flash to store all the strings to convert the mysensors variable names and stuff.
This filled up my atmega328 almost completely and I got tired of all the trickery required to stay within the 32kb. I just wanted to prove and test the cooperation of my sensors and MQTT.
Then I realized the MQTT broker had to run on a 'heavier' platform anyway and decided that also my gateway could -- I see no use to stuff everything into an arduino.If you're interested I can share the arduino implementation, but I no longer see the use for it.
If your changes improved my implementation then please share them with us :+1:
@Yveaux My script is not better than yours, I kind of broke it.. :)
I had a thought that the atmega328 isn't enough, one option is to have external flash but no program code can be stoored there. The 32kb is still very limiting.
I had a thought of atmega2560, there is one model with build in ethernet and some with external, total cost ~30USD. It has 256KB flash memory.
So, yes I would be interessed in yout arduino code.. I might be able to slim the program down.. :) -
Hello
go Jeedom
the project progresses faster
and I motivated to make a plugin for MySensors
there will be more people motivate
faster plugin advance -
@Yveaux My script is not better than yours, I kind of broke it.. :)
I had a thought that the atmega328 isn't enough, one option is to have external flash but no program code can be stoored there. The 32kb is still very limiting.
I had a thought of atmega2560, there is one model with build in ethernet and some with external, total cost ~30USD. It has 256KB flash memory.
So, yes I would be interessed in yout arduino code.. I might be able to slim the program down.. :) -
@Damme My code does only implement a MQTT client, not the broker. But if you still want it, chat me your email and I'll send it to you.
-
Hello
go Jeedom
the project progresses faster
and I motivated to make a plugin for MySensors
there will be more people motivate
faster plugin advance@filoucaenais so bad all the core features in the market are to be bought... and that only zway which is now dying is supported, not openzwave...
@bjornhallberg @Damme even domoticz guy are pushing people to use something better than raspberry... for a little more you have a cubieboard2 which has 1Go RAM and 2 cores @ 2011 bogomips... For z-wave OpenHab is still the best choice...
z-wave - Vera -> Domoticz
rfx - Domoticz <- MyDomoAtHome <- Imperihome
mysensors -> mysensors-gw -> Domoticz -
@filoucaenais so bad all the core features in the market are to be bought... and that only zway which is now dying is supported, not openzwave...
@bjornhallberg @Damme even domoticz guy are pushing people to use something better than raspberry... for a little more you have a cubieboard2 which has 1Go RAM and 2 cores @ 2011 bogomips... For z-wave OpenHab is still the best choice...
@epierre Yes there are a lot better options out there, but I'm not going to buy a new platform just so I can run JAVA ;-) Nothing in this price range is going to be fast enough for that I suspect. Faster, sure, but not fast as in virtually instantaneous.
I actually tried openhab2 branch on the RPi just a few minutes ago. Slow Sunday, I know. Don't know if it has been optimized yet as promised but it took about 4 minutes to start. And then it used up 25% of available RAM right out of the box, running the demo config. Would be interesting to see how fast it boots on a cubieboard2 or similar. Even if it could get it down to a minute it would be a minute too much imo. Perhaps it will run fine after it's been loaded, but those loading times were enough to deter me. I mean, in 4 minutes your house could get burgled several times over ;-) I just don't see what openhab has to offer that is worth all that.
The reason I got a RPi was the camera module. And the extremely wide support for the platform. I swore I would never touch an ARM platform again after my first Android phone and my Synology NAS but I guess the price (and camera) got the better of me. I also don't have any z-wave devices.
On a side note, I've ordered another Arduino Uno Ethernet Shield to complete the bridge to the MQTT broker. I will just have to find some automation software that will run fine on the Pi.
-
@epierre Yes there are a lot better options out there, but I'm not going to buy a new platform just so I can run JAVA ;-) Nothing in this price range is going to be fast enough for that I suspect. Faster, sure, but not fast as in virtually instantaneous.
I actually tried openhab2 branch on the RPi just a few minutes ago. Slow Sunday, I know. Don't know if it has been optimized yet as promised but it took about 4 minutes to start. And then it used up 25% of available RAM right out of the box, running the demo config. Would be interesting to see how fast it boots on a cubieboard2 or similar. Even if it could get it down to a minute it would be a minute too much imo. Perhaps it will run fine after it's been loaded, but those loading times were enough to deter me. I mean, in 4 minutes your house could get burgled several times over ;-) I just don't see what openhab has to offer that is worth all that.
The reason I got a RPi was the camera module. And the extremely wide support for the platform. I swore I would never touch an ARM platform again after my first Android phone and my Synology NAS but I guess the price (and camera) got the better of me. I also don't have any z-wave devices.
On a side note, I've ordered another Arduino Uno Ethernet Shield to complete the bridge to the MQTT broker. I will just have to find some automation software that will run fine on the Pi.
@bjornhallberg on my cubie (paid $50 with a box), I have imperihome gateway, mysensors gateway, jeedom, domoticz and openhab running... load: 0,6 more than 200 Mo ram available even with kernel cache...
remember that the pi has no FPU... BogoMIPS : 464.48 ...
