Open Source Home Automation (Raspberry)
-
@bjornhallberg
Disable the ssl in config/system.default.properties or copy and paste the below line in config.properties (default has precedence)server.enablessl = falseAnd it will be even faster, it then disables the certificate generation(at least 5 seconds), ssl websocket, http and raw socket instances (couple seconds per instance type).
I'm glad you got it up and running quite quickly if i understood correct because the downloads are still in alpha state (snapshots). I wish i already had some example sensors in the DB so it could by tried out without having to create XML definition files yourself.
-
@John
Your project looks great! I'm looking around for an home automation controller and was tossing between domoticz, openhab and FHEM.My criteria are:
- MySensors support (whether directly or through a gateway)
- Z-Wave support
- Visual floor plan
- Runnable on a Pi
May have to add yours to the mix to trial.
How difficult would it be to compile openzwave and integrate it by some mechanism to PiDome, do you think?
-
@John
Your project looks great! I'm looking around for an home automation controller and was tossing between domoticz, openhab and FHEM.My criteria are:
- MySensors support (whether directly or through a gateway)
- Z-Wave support
- Visual floor plan
- Runnable on a Pi
May have to add yours to the mix to trial.
How difficult would it be to compile openzwave and integrate it by some mechanism to PiDome, do you think?
- MySensors support: Almost completely done with todo's as including AUTO addressing and datatype assignments.
- Visual Floor plan: Available in the server and desktop client.
- Runnable on a Pi: This is the primary target.
- Z-Wave support: On our todo list: https://bitbucket.org/pidome/pidome-server/issue/70/add-zwave-support
OpenZWave is the best candidate to use but has not yet been completely looked into yet because the internal pidome device, web interface, and package management bindings api is not completely finished yet and grows with supporting protocols etc.. It is possible it takes between two and three months before it is included by default if i follow my roadmap.
MQTT is planned to be implemented after MySensors and other stuff, so if there is an MQTT interface for OpenZWave it should be possible somewhere in the end of September/begin October.
-
@Damme TTS caught my eye the first time around, but I sort of dismissed it because it was node.js, immature, unheard of, and seemed reluctant to show much of its web gui. Seemed more like a concept and a bunch of techno babble. Also, support for a bunch of expensive commercial stuff that I'll never buy (Tesla cars anyone?). And, no smartphone apps (yet). I guess they're the sort of hipsters that like to run things in their smartphone browsers. But I can see the potential here. The web ui seems pretty snappy from their vimeo demo, and like you say, they have basically served up a functioning example of how to interface with an Arduino.
They sort of shut me up about user interfaces also. Their web ui is so different it seems to be from the future ;-)
http://vimeo.com/88873020#t=240@bjornhallberg said:
TTS caught my eye the first time around, but I sort of dismissed it because it was node.js, immature, unheard of, and seemed reluctant to show much of its web gui. Seemed more like a concept and a bunch of techno babble.
The spiel on The Thing System about having "magic" in place of user visible control raises my caution flags. It remind me of the frustrations that Microsoft's software sometimes generates - when what you want it to do matches what they expected you to want, it automagically just does it behind the scenes and you say "wow, cool" -- but when you step off the paved path and want to do something different, the branbles can become very complex and difficult if not impossible.
So if your water leak detector activates, the system should "just know" what the most appropriate actions are - without the user needing to specify or configure or any of that difficult stuff. But in many decades of dancing with computers, the software has never (in any complex system) done exactly what I want. I don't trust that there is one size that fits all when it comes to "automagically" doing what I want, that adapts to all varieties of systems and all preferences. I need the option (1) to clearly know what actions will be triggered by some event by default, and (2) to be able to override or customize that action.
The Ignite video "the Trouble with Things" linked from their site does not inspire confidence. They show a wireless keyboard television control and a three button remote control and suggest that the latter is much to be preferred. Yeah, I love using up/down/left/right screen keyboards for finding youtube videos, it's so much more intuitive than typing.
When I worked on dedicated word processor systems many years ago, we used to talk about the need for a DWIM button on the keyboard (Do What I Mean). But at least we knew that we were joking. I'm not sure TTS knows when they are blowing smoke in thinking they can design some kind of hidden smarts that magically and accurately does what the user means.
I am much more interested in user interfaces where the effort has been making complex things clear to understand and easy to control, than those that think they know what I need better than I do and want me not to worry my pretty little head about what they are going to do or how on my behalf.
(And I do get that their target market is not people who are willing to solder together and program their own wireless sensor network. They want to attract people who want home automation to be as easy as using a microwave oven or driving a go-kart. But I've seen misguided and arrogant implementations of DWIM frustrate and confuse non-technical users many, many times as well).
That said, they may come up with something worthwhile in some niches. But my warning flags are up.
-
@bjornhallberg said:
TTS caught my eye the first time around, but I sort of dismissed it because it was node.js, immature, unheard of, and seemed reluctant to show much of its web gui. Seemed more like a concept and a bunch of techno babble.
The spiel on The Thing System about having "magic" in place of user visible control raises my caution flags. It remind me of the frustrations that Microsoft's software sometimes generates - when what you want it to do matches what they expected you to want, it automagically just does it behind the scenes and you say "wow, cool" -- but when you step off the paved path and want to do something different, the branbles can become very complex and difficult if not impossible.
So if your water leak detector activates, the system should "just know" what the most appropriate actions are - without the user needing to specify or configure or any of that difficult stuff. But in many decades of dancing with computers, the software has never (in any complex system) done exactly what I want. I don't trust that there is one size that fits all when it comes to "automagically" doing what I want, that adapts to all varieties of systems and all preferences. I need the option (1) to clearly know what actions will be triggered by some event by default, and (2) to be able to override or customize that action.
The Ignite video "the Trouble with Things" linked from their site does not inspire confidence. They show a wireless keyboard television control and a three button remote control and suggest that the latter is much to be preferred. Yeah, I love using up/down/left/right screen keyboards for finding youtube videos, it's so much more intuitive than typing.
When I worked on dedicated word processor systems many years ago, we used to talk about the need for a DWIM button on the keyboard (Do What I Mean). But at least we knew that we were joking. I'm not sure TTS knows when they are blowing smoke in thinking they can design some kind of hidden smarts that magically and accurately does what the user means.
I am much more interested in user interfaces where the effort has been making complex things clear to understand and easy to control, than those that think they know what I need better than I do and want me not to worry my pretty little head about what they are going to do or how on my behalf.
(And I do get that their target market is not people who are willing to solder together and program their own wireless sensor network. They want to attract people who want home automation to be as easy as using a microwave oven or driving a go-kart. But I've seen misguided and arrogant implementations of DWIM frustrate and confuse non-technical users many, many times as well).
That said, they may come up with something worthwhile in some niches. But my warning flags are up.
@Zeph Yeah, it almost seems like a trend these last couple of years. I agree completely with what you say. I don't know how or why this came about, perhaps we are all experiencing the consequences of the Iphone boom and all that it ushered in. Windows 8, Windows Phone and even Android seem to be creeping towards this goal. A desire to reach out to tech illiterate people (and ultimately profit from them).
I just realized it's hard not to sound like a complete elitist though when talking about these things. Haha.
"Magic" wouldn't be so bad if it just didn't strip away user control and choice, dumbing things down, but it always seems to be the case. Like it is some ideological tenet. I can't shake the feeling that more often than not (in the case of Microsoft for instance) there are murkier reasons for doing what they do. Just like with the rise of "the cloud". takes off tinfoil hat
-
A little late to the thread here, but as I'm constantly looking at open source automation software, thought I'd chip in.
My first forays into HA were with an RFXTRX and domotiga - it's a great system with plenty of interfaces. The downside for me was that it needs (maybe doesn't any more) a linux host to run the UI - I use a windows PC and the extra step of having to run a Linux VM to make any changes got in the way.... that said the vast number of options gave me a lot of ideas about what and how I want to automate things.
I spent around 18 months running AgoControl - I was impressed with this from the outset, and persevered for sometime with it's quirky interface (web gui isn't intuitive for building scenes and doesn't resize for tablet/mobiles). The deal breaker recently for me was one of reliability - I found the RPi needed to be rebooted every 4-5 days due to a memory leak issue with the AMPQ engine, a daily cron reboot of the RPi seemed to improve things, but then for some reason certain events wouldn't reload. I think (not sure) there were some issues with the openzwave wrapper which caused a few issues and slowness with the response times. The second issue I had was that the majority of the plugins are written in perl, which seemed to dramatically slow down the system when more than a couple were running.
I haven't given up on it - I still have an RPi set aside for AgoControl, and will look into it again when I have more time.
It was time to investigate issues which led me to purchase a veralite a couple of months ago, and while not in itself not quirky (multiple lua restarts needed to pick up changes etc), it has been faultlessly reliable in that two months.
I have looked at OpenHAB, it's vast number of interfaces (bindings?) and mature looking interface being the appeal. Unfortunately, despite being technically minded, I'm not a hardcore developer - and having looked at the documentation for OpenHAB, it looks hellishly complicated just to set up, let alone build scenes and so on for.
I've also played around with NodeRed and a few jeenodes and am considering/planning to use nodered and the mqtt gateway for mysensors to re-use some of the code I built to send sensor data to emoncms.org.
Cheers
James -
Domoticz crew is looking for someone to implement (in C++) the MySensors api/gateway…
Here's the ticket if anyone is interested. -
A little late to the thread here, but as I'm constantly looking at open source automation software, thought I'd chip in.
My first forays into HA were with an RFXTRX and domotiga - it's a great system with plenty of interfaces. The downside for me was that it needs (maybe doesn't any more) a linux host to run the UI - I use a windows PC and the extra step of having to run a Linux VM to make any changes got in the way.... that said the vast number of options gave me a lot of ideas about what and how I want to automate things.
I spent around 18 months running AgoControl - I was impressed with this from the outset, and persevered for sometime with it's quirky interface (web gui isn't intuitive for building scenes and doesn't resize for tablet/mobiles). The deal breaker recently for me was one of reliability - I found the RPi needed to be rebooted every 4-5 days due to a memory leak issue with the AMPQ engine, a daily cron reboot of the RPi seemed to improve things, but then for some reason certain events wouldn't reload. I think (not sure) there were some issues with the openzwave wrapper which caused a few issues and slowness with the response times. The second issue I had was that the majority of the plugins are written in perl, which seemed to dramatically slow down the system when more than a couple were running.
I haven't given up on it - I still have an RPi set aside for AgoControl, and will look into it again when I have more time.
It was time to investigate issues which led me to purchase a veralite a couple of months ago, and while not in itself not quirky (multiple lua restarts needed to pick up changes etc), it has been faultlessly reliable in that two months.
I have looked at OpenHAB, it's vast number of interfaces (bindings?) and mature looking interface being the appeal. Unfortunately, despite being technically minded, I'm not a hardcore developer - and having looked at the documentation for OpenHAB, it looks hellishly complicated just to set up, let alone build scenes and so on for.
I've also played around with NodeRed and a few jeenodes and am considering/planning to use nodered and the mqtt gateway for mysensors to re-use some of the code I built to send sensor data to emoncms.org.
Cheers
James@jdr0berts Yes, it is unfortunate that both domoticz and agocontrol are such dinosaurs since they are the only ones doing C++. If PIDOME wasn't making such progress I'd probably have to give up on MySensors. At least mothball it for six months and see if something has changed. Sad truth of the day.
There are two things I wish I had realized from the beginning. One being how literally everyone is using a Vera (and z-wave devices as well) and is happy with that and secondly that the controller is responsible for more than just receiving and sending messages so mimicking the Vera is not entirely easy. Like the automatic nodeIDs? I had been a tad more skeptical as to the outcome had I known this. I'm not griping, I've just suddenly gotten a better understanding of what a 3rd party developer has to go through.
@andriej Slim chance of that happening. They're also looking for someone to write a C++ MQTT implementation. The current one is some sort of node.js to lua. With the lua missing. I've asked in their forums and at the guy's github about where to find the file. No reply. I understand the implementation was also quite slow so it might not matter. I.e. the antitheses of the quick C++ core.
@John Perhaps you could set up a dedicated PIDOME thread for some q&a and troubleshooting? It would probably also get PIDOME some more visibility for people ending up in the Raspberry forum looking for a solution.
-
@bjornhallberg
I think i've missed your mention. Yeah it would be a good idea, albeit not for exposure but for helping out if there are any issues with it (i already find my mailbox filling up with mysensors questions). So yeah i think it is handy to have a dedicated thread. But only if @hek agrees with having such a dedicated thread.If PIDOME wasn't making such progress...
It still is going to slow (in my personal opinion).. especially with not having enough hardware to test with ;).
My Domotica project: http://www.pidome.org
-
@bjornhallberg
I think i've missed your mention. Yeah it would be a good idea, albeit not for exposure but for helping out if there are any issues with it (i already find my mailbox filling up with mysensors questions). So yeah i think it is handy to have a dedicated thread. But only if @hek agrees with having such a dedicated thread.If PIDOME wasn't making such progress...
It still is going to slow (in my personal opinion).. especially with not having enough hardware to test with ;).
-
I stumbled upon HouseMon the other day ... anyone here try that? Seems pretty damn great, but a bit obscure and very hard (for me at least) to make heads or tails of. Uses a slew of catchy, modern tech (Dataflow, MQTT, LevelDB, WebSockets, AngularJS, CoffeeScript/Jade/Stylus, Go) all across the board and, most importantly, is quicker on the Raspberry than I would have ever imagined possible, including the web front-end. At least for the test setup. Probably because it uses a pre-compiled binary.
Installation:
http://aka-lightbulb.com/2014/04/28/housemon-0-9-x-on-linux-binary-installation/Not exactly ready for public consumption yet but not so unlike OpenHAB in its design and complexity either.
-
Perhaps this discussion should be taken to a more rudimentary level, trying to figure out which automation software we actually want to bet on. And what software will actually run WELL on the resource limited RPi. It would take some convincing before I ever installed java-based solutions for instance, like openHab.
Has anyone actually tried Ago Control? Is it any good? Does it work well with the Pi? The installation is 130MB no less. A ton of dependencies. Makes you wonder about RAM and CPU usage.
It feels like this entire market is a bit premature at the moment.
@bjornhallberg I installed AGO and the Mysensor plugin on my RPI/b and after much head scratching and picking out little tidbits here and there on how to get this to load I have a MySensor sending data to it. -- The webgui is reasonably fast, but for the world I can't figure out what you actually can do with it or how you could use the GUI to configure any action to be taken depending on a Sensor reading. The Documentation is totally missing any hints as to how to use the thing.
Without any clue as to how to make this do anything useful I will format the Rpi's SD card again...
-
@bjornhallberg I installed AGO and the Mysensor plugin on my RPI/b and after much head scratching and picking out little tidbits here and there on how to get this to load I have a MySensor sending data to it. -- The webgui is reasonably fast, but for the world I can't figure out what you actually can do with it or how you could use the GUI to configure any action to be taken depending on a Sensor reading. The Documentation is totally missing any hints as to how to use the thing.
Without any clue as to how to make this do anything useful I will format the Rpi's SD card again...
@GaryStofer Haven't used Ago Control in a long time. I wouldn't have recommended it in the past. Didn't like the AMQP deal. And there were other nuisances. However with version 1.0 coming up perhaps they have made enough improvements to warrant a new look. Support for the ImperiHome Android app is a big deal for instance since their own Android app was pretty basic. If you're not using 1.0 from their testing repository I can understand your frustration.
Personally I'm quite content with Domoticz for the time being. Easy to use and just works.
-
Hello I am new to all of this but I was so happy that this library worked out of the box. I went with MySensors and AgoControl and was elated until I saw that my servo would not move. It reported the distance sensor and switches worked, but "drapes" and "dimmer" did not. It was not difficult to find out how to add support and now my servos turn but I have not submitted code.
https://github.com/mce35/agocontrol/blob/master/devices/MySensors/agoMySensors.cpp#L732
Actually MySensors seems to have an enormous amount of supported types, and AgoControl seems to have a good amount but the glue, seriously probably the easiest part, is missing. -
@GaryStofer Haven't used Ago Control in a long time. I wouldn't have recommended it in the past. Didn't like the AMQP deal. And there were other nuisances. However with version 1.0 coming up perhaps they have made enough improvements to warrant a new look. Support for the ImperiHome Android app is a big deal for instance since their own Android app was pretty basic. If you're not using 1.0 from their testing repository I can understand your frustration.
Personally I'm quite content with Domoticz for the time being. Easy to use and just works.
@bjornhallberg I like to give Domoticz a try, but I can't find any mention of a MySensor plug-in anywhere in their Documentation nor on the Wiki. The only mentioning I see is on the MySensor.org controller page saying that it's supported.
How are your MySensors talking to it?
gary
-
@bjornhallberg I like to give Domoticz a try, but I can't find any mention of a MySensor plug-in anywhere in their Documentation nor on the Wiki. The only mentioning I see is on the MySensor.org controller page saying that it's supported.
How are your MySensors talking to it?
gary
@GaryStofer Take a look at topic, you need the Domoticz beta feed. The Domoticz Wiki pages are not updated for the MySensors implementation. @hek was there any new documentation?
-
No, I haven't seen any new MySensors documentation on their wiki yet. Rob is on a business trip so I doubt there will be any the coming couple of weeks.
