Using OpenHAB, any better (looking) alternatives?
-
The latest version of domoticz is apparently broken, but I think it compiles with a version from a few days ago... Typical :-)
-
@bjornhallberg I use domoticz for some reed sensors. I am about to create a sensor that plays a tone and lights a LED when they are opened - What is best way to do this? Via the controller scripts or direct comms from the sensors? I have tucked away the sensors so don't really want to reprogram but if its best option then I will!
Thanks.
@shabba I guess any approach would work, if your sensor is awake and listening for incoming messages. I actually have a similar idea for the front porch where I will use an audio player module (WTV020-SD-16P - glitchy stuff but easy to find) and an amplifier (PAM8403) with a pair of 4Ω 3W speakers to get prospective visitors to crap their pants. It seems best to have the sensor do the triggering in that case. But why not have it set up to play another file as a warning or alarm when triggered from the controller.
-
@AWI said:
Domoticz
Thanks for the suggestion of Domoticz, I will definitely look into it a bit more closely.
Apart from not being as nerdy, are there any other features that set it apart (above) OpenHAB?
@kolaf I do not have experience with OpenHAB, so hard to say. I appreciate the learning curve for Domoticz and ability to do the nerdy stuff in Lua and JSON from Python. To be honest ;I still have my own Python-JSON script running to interface between Domoticz and MySensors as there is no broad native support for requesting variables. (especially eg. V_KWH, I use MySensors also to display information in the whole building. ;) )
-
The latest version of domoticz is apparently broken, but I think it compiles with a version from a few days ago... Typical :-)
-
Downloaded Domoticz and had it set up and running in ~15 min on a beaglebone black. Had a little bit of trouble getting my serial gateway to show up. It looks like Domoticz will only look for serial ports in the form of /dev/ttyUSB##. Since I am using the UARTS on the beaglebone it did not work right off. On a hunch I added a symlink:
sudo ln -s /dev/ttyO4 /dev/ttyUSB2Worked like a charm. I have been using openhab for a few months and like it, however I was able to do in Domoticz in 15 min what took hours to figure out in openhab, and the graphs looks a lot better in Domoticz also.
-
@kolaf said:
The latest version of domoticz is apparently broken, but I think it compiles with a version from a few days ago... Typical :-)
No, it doesn't 😯
-
Eventually I got it to compile by deleting my current subversion version and doing a new checkout of revision 2361. I think the reason why this didn't work the first time was that I wasn't able to clean the compile environments enough after checking out the earlier version. This revision is reported to work by many people in the forum, and for me as well.
I have spent the past few days playing with it, and I have it controlling my zwave network, my nexa and Oregon scientific devices through rfxcom, and finally my mysensors devices, all without any additional plug-ins :-)
I have also managed to get mqtt working space by using the approach outlined in the wiki, but I have no idea how to access the apparently built-in mqtt support. My plan for today is to post notification messages to my mqtt broker so that they can be picked up by mqttwarn.
I like that they have a graphical rule building interface, this makes it easy for new users, but I found that I quickly reverted to the lua scripting functionality. Both because it is much more powerful, and it's actually faster to work with this than a graphical interface :-)
-
Downloaded Domoticz and had it set up and running in ~15 min on a beaglebone black. Had a little bit of trouble getting my serial gateway to show up. It looks like Domoticz will only look for serial ports in the form of /dev/ttyUSB##. Since I am using the UARTS on the beaglebone it did not work right off. On a hunch I added a symlink:
sudo ln -s /dev/ttyO4 /dev/ttyUSB2Worked like a charm. I have been using openhab for a few months and like it, however I was able to do in Domoticz in 15 min what took hours to figure out in openhab, and the graphs looks a lot better in Domoticz also.
@reddy11 could you please help (step-by-step) how to determine which /dev/tty is UART and how to connect Arduino to it? (RX->TX, TX->RX + Vcc + Gnd is everything I need?)
I'd like to write a Wiki about it, but first I have problems with connecting arduino serial output to OrangePi (never used it, to be honest, neither GPIO or UART).
-
I succeeded in compiling the latest domoticz, found a post on the domoticz forum (http://www.domoticz.com/forum/viewtopic.php?t=6018#p39336) that solved the issue.
Basically what happens is, that cmake finds the wrong libcurl libraries to include in the build. You have to specify it on the command line with -DCURL_LIBRARY like
cmake -DCMAKE_BUILD_TYPE=Release -DCURL_LIBRARY=/usr/lib/arm-linux-gnueabihf/libcurl.so.4 CMakeLists.txtAbove is for building on raspberrypi.
-
Eventually I got it to compile by deleting my current subversion version and doing a new checkout of revision 2361. I think the reason why this didn't work the first time was that I wasn't able to clean the compile environments enough after checking out the earlier version. This revision is reported to work by many people in the forum, and for me as well.
I have spent the past few days playing with it, and I have it controlling my zwave network, my nexa and Oregon scientific devices through rfxcom, and finally my mysensors devices, all without any additional plug-ins :-)
I have also managed to get mqtt working space by using the approach outlined in the wiki, but I have no idea how to access the apparently built-in mqtt support. My plan for today is to post notification messages to my mqtt broker so that they can be picked up by mqttwarn.
I like that they have a graphical rule building interface, this makes it easy for new users, but I found that I quickly reverted to the lua scripting functionality. Both because it is much more powerful, and it's actually faster to work with this than a graphical interface :-)
-
Sorry, I used the native mysensors support, not mqtt.
