For those of you who just want to start playing with the Raspberry Pi and your Z-wave devices, this is pretty much the laziest way. I took the latest Wheezy Rasbian (2012-10-28) image, grabbed all the updates, put nginx, php, and a couple open-zwave clients and servers into a new downloadable disk image. The image will unzip using 7-zip to fit on a 2 gb card but there is not a lot of empty space since I did not remove anything from the default image other than the python_games folder.
UPDATE: Check out Open-Zwave Christmas Lights.
How To:
- Download the image: openZwavePi-12-12-12.7z (445mb)
- Write the image to your SD card. Great tutorial.
- Plug everything in including your Aeon Labs Z-stick S2. (I recommend paring it with at least one Z-wave device before you start up your Pi so you can see the magic from the very start.) The image is already set up to run headless, so you don’t have to plug in your keyboard or monitor unless desired.
- Let it boot up. Normally, this goes pretty quick and you can watch the lights blink on the Pi rapidly. I would give it a couple minutes just to be safe.
- If you went headless, ssh to [email protected] from any machine on your network. The password is still set to the default ‘raspberry’.
- There are two options for starting the open-Zwave socket server depending on what client you want to use. Option 1 was made by Conrad Vassallo and is call Lights Control. It has a nice interface and lots of functionality – I would consider it the “default. The second, is a very basic version made by me without any bells and whistles. To start option 1, type “lightscontrol” on the command line. Option 2 will start if you type “basic”. Both servers cannot run at the same time, but you can switch between them by typing “killOZW” and then the command for whatever server you want to start up.
- Then to control your lights, navigate to http://openzwave.local/ (if you are using option 1) or http://openzwave.local/basic/ if you are using option 2. To log in to Lights Control, you will need to type in “Admin” for the username and “admin” for the password (note the case). The first time you load Light Control without any imported devices, it will return an error after you put in the password. To clear up this error, enter “http://openzwave.local/index.php?r=devices” after you have authenticated and click the “import” button. From then on, you should be good to go.
A Few Notes:
The software is very much still under development and this is just a quick start. The security, configuration, permissioning, and future upgrades are up to you but what you have is an almost immediately working open-Zwave solution. I also recommend taking your time between opening and closing the different servers. Every time one of the open-Zwave servers start up, it contacts all the nodes and runs through their status and configuration. As your network grows, this process takes a little longer.
I ran the initial version on a 2gb class 2 SanDisk card and it ran quickly so anything better should have great performance.
UPDATES:
I switch back and forth between the servers a lot and Alison was always checking two urls to turn on the Christmas tree (firstworldproblem).
To fix this, I created a file called “indexbasic.php” and put it in the /usr/share/nginx/www/ directory. It contains the following code:
<!--?php
header("Location: /basic/");
</pre-->Then I made a copy of the default index I had in the root directory:
cp /usr/share/nginx/www/index.php /usr/share/nginx/www/indexlightscontrol.php
and I updated my /home/pi/.bashrc to switch in the appropriate index page when I launched a specific open-Zwave server.
alias lightscontrol='cp /usr/share/nginx/www/indexlightscontrol.php /usr/share/nginx/www/index.php && ozw && nohup ./lightscontrol-server > /dev/null &' alias basic='cp /usr/share/nginx/www/indexbasic.php /usr/share/nginx/www/index.php && ozw && nohup ./basic-server > /dev/null &'
A Few Images:
An example of a Z-wave node using the Basic Control Panel
Comments
The link at the image file don’t work . . .
Wow. I spelled my own name wrong in the link. Sorry about that.
I downloaded the archive but 7zip throws an error when I try to open it, “Cannot open file [file] as archive.”
Well that is not fun. Do you want me to put it up in a different archive format? I tried duplicating the problem but no dice. What OS are you using? Example from my attempt on debian:
7z x openZwavePi-12-12-12.7z
7-Zip 9.04 beta Copyright (c) 1999-2009 Igor Pavlov 2009-05-30
p7zip Version 9.04 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,4 CPUs)
Processing archive: openZwavePi-12-12-12.7z
Extracting openZwavePi-12-12-12.img
Everything is Ok
Size: 2032664576
Compressed: 467287344
hahaha, that spelles exhaustion for ya…
Any change on the instructions for a non-raspian setup?
Yes – I think so – do you have open-zwave compiled in the same structure as open-zwave svn download? What I found is if I took, the files I sent you and Conrad’s Makefile and Main.cpp and put them in a new directory under/cpp/examples/linux/(make a new directory) I could build it without changing the Makefile. (it should solve your “Main.cpp:45:26: fatal error: ServerSocket.h: No such file or directory” problem) I tested it by running ./test and then connecting via telnet (on port 6004). Then I pick a web server (in my case nginx) and installed it and php5, curl, sqlite. When I got it up and running, I got some directory permissions errors – so fix that the horribly insecure way chmod 777 and then got an error because a redirect (change in headers) was being called after text output. I went to whatever line it specified and saw that it was a curl statement outputting the response. I added “curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);” so the return from curl goes to a variable and does not get outputted to the screen.
I am downloading voyage linux and I will give it a try there.
Haha, no thomas, I really appreciate this. I don’t own a Pi… I want to run it on a ALIX board running debian wheezy.
I tried again and it turns out Chrome didn’t download the entire file. Now that I got the entire zip, all appears to be working like a charm. Thanks!
Hi Thomas,
I installed the image and my raspberry part correctly, but unfortunately does not see my z-stick s2, where am I doing wrong?
I tested my z-stick with a trial version of “homesser” and it works correctly.
Thanks in advance
Is your stick plugged into a powered hub? Some pi’s can’t power them. (or try changing power supply)
My stick is inserted directly into the Rapsberry and lights are up properly, I’ll try to put a powered HUB.
thanks
hi,
I have used a new powered USB HUB but nothing in changenged.
After boot I have tried to import the devices using the URL http://openzwave.local/index.php?r=devices, but in the page I can see only
Node ID = 0
Device Name = error Connection refused
Device Type = null
Room = Undefined
If you want, I can publish my raspberry . . . . . . .
Did you start the server on the command line? Type lightscontrol in the cli. Wait 2-3 minutes and hit enter a couple times – do you see the nohup failing?
Hi,
sorry but I made a mistake.
now everything is working and I thank you for your patience.
A small request: I can not run the http server on port 82, I have changed many times the file nginx.conf, but without success.
Any suggestions?
Thank you.
Of the top of my head, it should be in /etc/nginx/sites-available/default. If you have a problem with running on a port that low without root, try 8080.
(Reminder, restart nginx after config change)
Hi,
Looks great!!! But while I’m waiting for the image to download I think that I’d really love to play with the code myself and extend it to work with other Zwave devices (like the motion sensor and the energy tracking adaptor). Do you have blogs or other references that give hints about how you came to what you have now?
Thanks! and happy Holidays!
I hope you are having luck with the image. For more information, please checkout http://thomasloughlin.com/projects/z-wave/ and http://code.google.com/p/open-zwave/.
Hello
I can’t get this to recognise any devices. I get an “error connection refused” when importing.
Not sure what else to do?
Hi Andy, are you starting the basic or lightcontrol server before trying to connect via the website? Can you telnet port 6004 (telnet localhost 6004)? If that works try typing in ALIST (then enter). Do any devices return?
I’ve tried basic, but only get one blank box. Not sure what to do with that! In lightcontrol I click import and get the error.
Just tried telnet and get “unable to connect to remote host: Address family not supported by protocol”
I am putting the telnet localhost 6004 into an ssh session on the pi right? I did try to use putty to telnet from my windows PC to the pi, but doesn’t connect either.
Did you run ‘basic’ on the command line before starting to start the server? (it does not start automatically)
Yes. But no devices show
Sorry – just to confirm – You have already paired your devices?
I would kill any processes running – easy way is to just reboot or type killOZW
Then I would type ‘ozw’ which will bring you to the directory of the server and I would run ./basic-server
This will display all the output info from the openzwave driver. Let me know what it says.
I’m not sure how to pair the devices? I don’t have the same usb stick as yourself as they aren’t available anymore. I got this one
http://zwave-products.co.uk/shop/article_332/Z-Wave.Me-Z-Stick-Z-Wave-USB-Dongle.html?sessid=GTDrckTzzMHv5H7Uw4u7vvwI5B0Q0nG8e4phCwJ3CfxCkyYXNEAHS1tNu1knssdN&shop_param=cid%3D75%26aid%3D332%26
This is the output from the command above.
[email protected] ~/open-zwave-read-only/cpp/examples/linux/testserv $ ./basic-server2013-01-15 19:25:18:554 mgr, Added driver for controller /dev/ttyUSB0
2013-01-15 19:25:18:557 Opening controller /dev/ttyUSB0
2013-01-15 19:25:18:558 Trying to open serial port /dev/ttyUSB0 (attempt 1)
2013-01-15 19:25:18:562 Serial port /dev/ttyUSB0 opened (attempt 1)
2013-01-15 19:25:18:565 contrlr, Queuing command: FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2013-01-15 19:25:18:567 contrlr, Queuing command: FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2013-01-15 19:25:18:568 contrlr, Queuing command: FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2013-01-15 19:25:18:570 contrlr, Queuing command: FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2013-01-15 19:25:18:571 contrlr, Queuing command: FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2013-01-15 19:25:18:573 contrlr, WriteMsg WriteNextMsg m_currentMsg=01d6fed8
2013-01-15 19:25:18:575
2013-01-15 19:25:18:576 contrlr, Sending command (Callback ID=0x00, Expected Reply=0x15) – FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2013-01-15 19:25:20:578 contrlr, WriteMsg Wait Timeout m_currentMsg=01d6fed8
2013-01-15 19:25:20:580
2013-01-15 19:25:20:582 contrlr, Sending command (Attempt 2, Callback ID=0x00, Expected Reply=0x15) – FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2013-01-15 19:25:22:586 contrlr, WriteMsg Wait Timeout m_currentMsg=01d6fed8
2013-01-15 19:25:22:588
2013-01-15 19:25:22:590 contrlr, Sending command (Attempt 3, Callback ID=0x00, Expected Reply=0x15) – FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2013-01-15 19:25:24:593 contrlr, WriteMsg Wait Timeout m_currentMsg=01d6fed8
2013-01-15 19:25:24:595 contrlr, ERROR: Dropping command, expected response not received after 3 attempt(s)
2013-01-15 19:25:24:597 contrlr, WriteMsg WriteNextMsg m_currentMsg=01d70118
2013-01-15 19:25:24:599
2013-01-15 19:25:24:601 contrlr, Sending command (Callback ID=0x00, Expected Reply=0x20) – FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2013-01-15 19:25:26:604 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70118
2013-01-15 19:25:26:606
2013-01-15 19:25:26:608 contrlr, Sending command (Attempt 2, Callback ID=0x00, Expected Reply=0x20) – FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2013-01-15 19:25:28:611 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70118
2013-01-15 19:25:28:613
2013-01-15 19:25:28:615 contrlr, Sending command (Attempt 3, Callback ID=0x00, Expected Reply=0x20) – FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2013-01-15 19:25:30:618 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70118
2013-01-15 19:25:30:620 contrlr, ERROR: Dropping command, expected response not received after 3 attempt(s)
2013-01-15 19:25:30:623 contrlr, WriteMsg WriteNextMsg m_currentMsg=01d70470
2013-01-15 19:25:30:625
2013-01-15 19:25:30:627 contrlr, Sending command (Callback ID=0x00, Expected Reply=0x05) – FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2013-01-15 19:25:32:630 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70470
2013-01-15 19:25:32:632
2013-01-15 19:25:32:634 contrlr, Sending command (Attempt 2, Callback ID=0x00, Expected Reply=0x05) – FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2013-01-15 19:25:34:637 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70470
2013-01-15 19:25:34:639
2013-01-15 19:25:34:641 contrlr, Sending command (Attempt 3, Callback ID=0x00, Expected Reply=0x05) – FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2013-01-15 19:25:36:644 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70470
2013-01-15 19:25:36:646 contrlr, ERROR: Dropping command, expected response not received after 3 attempt(s)
2013-01-15 19:25:36:648 contrlr, WriteMsg WriteNextMsg m_currentMsg=01d70610
2013-01-15 19:25:36:650
2013-01-15 19:25:36:652 contrlr, Sending command (Callback ID=0x00, Expected Reply=0x07) – FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2013-01-15 19:25:38:655 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70610
2013-01-15 19:25:38:657
2013-01-15 19:25:38:659 contrlr, Sending command (Attempt 2, Callback ID=0x00, Expected Reply=0x07) – FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2013-01-15 19:25:40:662 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70610
2013-01-15 19:25:40:664
2013-01-15 19:25:40:666 contrlr, Sending command (Attempt 3, Callback ID=0x00, Expected Reply=0x07) – FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2013-01-15 19:25:42:669 contrlr, WriteMsg Wait Timeout m_currentMsg=01d70610
2013-01-15 19:25:42:671 contrlr, ERROR: Dropping command, expected response not received after 3 attempt(s)
2013-01-15 19:25:42:674 contrlr, WriteMsg WriteNextMsg m_currentMsg=01d707b0
2013-01-15 19:25:42:676
2013-01-15 19:25:42:678 contrlr, Sending command (Callback ID=0x00, Expected Reply=0x56) – FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2013-01-15 19:25:44:681 contrlr, WriteMsg Wait Timeout m_currentMsg=01d707b0
2013-01-15 19:25:44:683
2013-01-15 19:25:44:685 contrlr, Sending command (Attempt 2, Callback ID=0x00, Expected Reply=0x56) – FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2013-01-15 19:25:46:688 contrlr, WriteMsg Wait Timeout m_currentMsg=01d707b0
2013-01-15 19:25:46:689
2013-01-15 19:25:46:689 contrlr, Sending command (Attempt 3, Callback ID=0x00, Expected Reply=0x56) – FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2013-01-15 19:25:48:691 contrlr, WriteMsg Wait Timeout m_currentMsg=01d707b0
2013-01-15 19:25:48:693 contrlr, ERROR: Dropping command, expected response not received after 3 attempt(s)
I tested the image with Tricklestar 300ZW-EU-W / 300ZW-US-W Z-Wave USB Stick, which is Open-Zwave compatible and driver is not installed. Is it planned to be included in the future?
You should be able to get the latest copy of openswave and re make. I will put an updated version up this weekened
Hello,
I would like to build a little home automation box.
I am a beginner so I need some help….
Do you think it’s possible to use :
raspberry-pi + RaZberry + domotiga
to turns Raspberry Pi into Z-Wave Home Controller ?
What do you think of this configuration ? Is it difficult to put in place ?
Thanks a lot for your help
Hi Thomas,
my question is about – have you succeeded in cross compiling Open Zwave for Raspberry and then cross compiling another C/C++ application again on the Host machine that uses the open zwave library. I can’t cross compile open zwave for Raspi as my Ubuntu complains that I don’t have proper libudev
Not sure what can I do?
P.S. – how is Nunya, hope she’s getting better!
Thanks for asking about Nunya. She is doing very well.
I have only compiled open-zwave/server/client/control panel on the Pi. Your timing was actually perfect as the comment came in right as I finally got my server to compile with the latest openzwave on a fresh install. I plan on releasing a new img tomorrow.
What version of ubuntu are you working on? Do you show both libudev-dev and libudev0:armhf? I am also assuming that you are using openzwave rv 628.
Hi Thomas, I also have a cute little doggy waiting to me to go back home in the evening so I’m glad Nunya is getting well 🙂
Great that you’re releasing a new img soon! I’ll try to recompile everything on the Pi but it would be great to make the cross compilation work too as it would be so much faster.
I’m having Ubuntu 12.4 and the latest openzwave source code. I think I don’t have libudev0:armhf. Apt-cache search doesn’t have it – I have only libudev0 and liudev-dev and they are currently installed. Do you know where should I get it from, may be it’s a part of another package… I’m now trying to find the libudev source, so that I can cross compile it for the Pi by myself. Hope it works! and all the best 🙂
hello,
I sent the other usb device I was using above back, it was faulty. I now have a aeon. I can see the devices in basic and switch them on, but then not off.
in lightscontrol I clicked import and now get the error below?
PHP notice
Trying to get property of non-object
/usr/share/nginx/www/framework/base/CComponent.php(607) : eval()’d code(1)
Which open-zwave socket server are you running with Lightscontrol?
I’m not sure. How do I find out?
type ‘killOZW’ into the command prompt, then ‘lightscontrol’. Wait a few minutes and see if you can import.
Is the basic version working normally?
In lightscontrol I get the php error above on the devices page and control page, so don’t see the website.
Basic works, but won’t switch the lights off, only on
I have a z-stick 2 paired with a single dimmer switch. Both basic and lightscontrol show three devices. Static Controller, Routing Binary Sensor and Multilevel Power Switch. In lightscontrol I am able to toggle the Multilevel Power Switch on and off. I don’t know what the other two devices do. In Basic the other two devices are represented by light bulbs and have a status but the Multilevel Power Switch has a broken link image and no status. When I click on it, nothing happens and I get the message “Last MSG: MSG~ZWave Node=4 Level=255” every time. Any idea whats going on?
Can you post or email me (email address is my first name at this domain) some of your OZW log?
Hi Thomas
Thanks for the images. After a little initial trouble changing everything to listen to /dev/ttyUSB1 instead of USB0, it seems to be working… now I just have to wait for my actual first Z-Wave device so I can properly test it. 🙂
@Andy : I have an AEON LABS Z-Stick 2 and it gaves me same output errors as your old. Can’t get it to work on my board but it looks fine on my windows PC
hi, just a liitle question, is it possible to execute shell scripts (bash) on incoming events?
Eg a door sensor reports an event and that will start shell script that sends sms ( gammu-smsd)
thanks
Hi,
I have just bought a RPI basic starter kit with a preconfigured SD card. Do you have an image that I can copy caste to this card in order to get started
Would you be interested helping me out getting Z-wave up and running on my board for a fixed fee?
Thanks
I can put up an image for you – what are you looking to have running on your Pi – just openzwave?
Hi Thomas,
Thanks for your reply.
Actually we plan to have several things running on the PI; Z-wave, ZigBee, WiFi, BT and serial communication to wired standards like KNX and M-Bus to smart meters..So on top of the IP stack we are planning a layer across different standards to be joined into JSON sripcts, pretty much like the SMARTTHINGS project.
First step would be to combine both your project with http://shop.basis.biz/shop/Raspberry-PI/piggy-back-board/ where an IP stack is available on the Pi for serial communication to meters.
A first major step would be having your openzwave up and running, and then secondly to combine it with the piggy back board as well. So if you have a basic image working with openzwave we would have one Pi running with that first, or do you have an idea of the best way forward… ?
Thanks !
The easiest image is located under download here: http://thomasloughlin.com/new-open-zwaveraspbian-image-ready-for-download/
Hi, Can we run the openzwave-control-pannel on archlinux raspberry Pi . I don’t want to run a complete format for my system.
You should be able to compile it from the google svn source.
I downloaded the image from here: http://thomasloughlin.com/new-open-zwaveraspbian-image-ready-for-download/
and i’m getting the same error as Andy above when i run ./basic-server: ERROR: Dropping command, expected response not received after 3 attempt(s)
When i try to “import devices” i get a device with device name “error Connection Refused”. I can’t telnet into the device, and even after i reset it i still can’t do anything. i have paired the usb stick with a device and still it’s a no go. what am i doing wrong? ANDY WHERE ARE YOU?!?!? DID YOU EVER FIX THIS?!?!?!
any ideas anyone?
Are you running the basic server with the basic client or Conrad’s client with the basic server? Also are you using /dev/ttyUSB0? Z-stick 2?
i kept getting the “error Connection Refused” when trying to import the devices on conrad’s client (using the lightscontrol server). so i rebooted, and ran ./basic-server from /open-zwave-read-only/cpp/examples/linux/testserv. this spits out basically the same log as Andy, although sometimes i get a “Expected reply was received”. and yeah i’m using the z-stick 2 and /dev/ttyUSB0 (i checked /dev/ and ttyUSB0 exists).
I also tried rebooting, not starting any servers, then running the openzwave control panel and initializing /dev/ttyUSB0. it will spit out the same log as ./basic-server, and when i try to reset the device it gives me this error: “mgr, Manager::GetDriver failed – Home ID 0x00000000 is unknown ozwcp: ../../src/Manager.cpp:320: OpenZWave::Driver* OpenZWave::Manager::GetDriver(uint32): Assertion `0′ failed.”
Few thoughts:
If you are on a PI, do you have the Z-stick plugged into a powered hub? (sorry if this feels like a backward question)
Can you delete all configuration files that might be left over (OZW_log.txt, zwcfg_*.xml and zwscene.xml?
What happens if you start either server and walk away for 30-45 minutes – do you ever hit the line saying “6004 ZWaveCommander Server”?
so i got it to work eventually. dont really know how. i tried running the reset function from openzwavecontrolpanel and then re-paired my device to the usb stick. i was then able to import my device without getting the “error Connection Refused” device showing up. thanks for the help!
for future reference i’m *not* running this on a powered hub.
The interface works great! I do, however have a question – one of my z-wave modules is a water sensor. Is there a way to treat it as an input device, rather than associate on/off functionality with it?
Can you send me what you see for the z-wave module after running /Client/debug.php? Should be a quick fix.
Hi,
How i can start up after reboot to “lightscontrol” mode?
You should be able to add lightscontrol to the /etc/rc.local file.
Hi
It is not work,
I’ll need to write “lightscontrol” before exit 0?
and maybe something before?
Thanks for the help
Sorry for the delay. You will have to check what the “lightscontrol” alias is calling and put that in. (look at the .bashrc file in the home directory).
Hi Thomas,
you seen my last post?
Thanks
Kobi
hi
How i can strat up after boot to “lightscontrol” mode and not the basic mode?
Thanks
Hi Thomas — Thanks for putting together this great package!! It got me up and running amazingly quickly. I am having an issue with the lightscontrol scheduler and was wondering if you had any tips on troubleshooting? I have a simple binary light that I am trying to get to turn on in the evenings. NTP looks good and date is reporting the correct time. I tried deleting the schedule and readding. The light turns on and off using the lightcontrol software and hitting the buttons manually just not with the scheduler.
I’ve got openzwave to compile right away with only a little mod , but python-openzwave that is different matter , 3 full day of playing and given up on it in the end.
Looks like it has been a while on comments on this project, but I am just now getting into the zwave stuff and have a small problem. I got everything loaded up on my raspberry pi, started up the ./ozwcpPI -p 55555, brought up the browser, entered my com port and initialized it. My devices start to show up, but with no manufacturer names. Looking at the log, its says “unable to load manufacturer_specific.xml.” I see that file in the “read-only/config” directory, but not in the other config directory. Is it supposed to be there as well ?