I have not yet been able to get the floorplan function to work. I added my lights thorugh the "Download Config" route on the web admin site, and added the lights to my map. However, I see no lights on the map on orbiters!

Another thing: reaction to the web interface is sometimes quite slow, or the command does not get processed at all. To any of you experienced Z-wave users: Is that normal?

Thanks,Mark

After adding your lights and then adding them to the lighting floorplan you must do a regen all. Then they should appear on the lighting floor plan.

ZWave for a single device should be pretty quick. However many devices responding or network problems will slow ZWave down to a crawl. Every device in the system needs to get from the controller to the device to be live or the system will stall looking for them. I usually get almost instant response.

Domodude

I am not a happy camper. Got everything recognized, including the three dimmers, I put them on my floorplan, and I even have the option of selecting 10%, 20% etc.

That's the good new. Bad news is that the dimming to let's say 20% didn't do anything at all to the light. So, just to make sure, I reset the dcerouter and regenerated all orbiters. But after that exercise, all three dimmers are gone.

Sat Jan 19 22:15:57 CET 2008 Restart========== NEW LOG SECTION ==========101/19/08 22:16:0571 (spawning-device)Starting... 8101/19/08 22:16:0571 (spawning-device)Found /usr/pluto/bin/ZWave0501/19/08 22:16:08.322Creating child 72 <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire events. <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR. <0xb79186d0>0501/19/08 22:16:08.326Creating child 80 <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb79186d0>0501/19/08 22:16:08.326Creating child 81 <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb79186d0>0501/19/08 22:16:08.326Creating child 82 <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb79186d0>0501/19/08 22:16:08.326Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb79186d0>0501/19/08 22:17:42.016Got a reload command from 0 <0xb5112b90>0501/19/08 22:17:42.519void ClientSocket::Disconnect() on this socket: 0x809a1e8 (m_Socket: 7) <0xb79186d0>Return code: 2201/19/08 22:17:4271 (spawning-device)Device requests restart... count=8/50 dev=71Sat Jan 19 22:17:42 CET 2008 Restart========== NEW LOG SECTION ==========101/19/08 22:17:5071 (spawning-device)Starting... 8101/19/08 22:17:5071 (spawning-device)Found /usr/pluto/bin/ZWave0501/19/08 22:17:57.040### Go to timeout queue <0xb68e2b90>0501/19/08 22:17:57.040### execute the next job from timeout queue <0xb68e2b90>0501/19/08 22:17:57.040ZWJobInitialize::timeoutHandler <0xb68e2b90>0501/19/08 22:18:02.041### Go to timeout queue <0xb68e2b90>0501/19/08 22:18:02.041### execute the next job from timeout queue <0xb68e2b90>0501/19/08 22:18:02.041ZWJobInitialize::timeoutHandler <0xb68e2b90>0501/19/08 22:18:03.610Creating child 72 <0xb78e56d0>0501/19/08 22:18:03.610Note: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire events. <0xb78e56d0>0501/19/08 22:18:03.610Note: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR. <0xb78e56d0>

Domodude

What do you see under lighting on the Web panel?This is similar to the problem I have loosing a light form the system.

I saw no lights anymore on the web panel.

Yesterday, I again added all lights, and so far have all three lights in the system.

When I test it now, nothing is happening when I try to turn them on or off using an XP orbiter.Checking the interface log shows problems connecting to the ttyS0 ZWave device, so I'm gonna see what will happen after a reboot. *hmm* Even though ZWave works sometimes, as far as I am concerned it is far from stable/predictable (at least with a RS232 interface).

Mark

Logged

Domodude

I'm just wondering...I frequently have no reaction to commands (mostly through the web page), but get the following in the log:05 01/20/08 11:41:53.005 ### Go to timeout queue <0xb6977b90>05 01/20/08 11:41:53.005 ### skip the next job from timeout queue <0xb6977b90>What do those two lines mean? It looks like the command will just get skipped.

What also happens is that I try three commands fairly quickly after each other, and I only get the above two lines once. I'd expect at least six lines. Is there a way to get more verbose debugging output?

I'm just wondering...I frequently have no reaction to commands (mostly through the web page), but get the following in the log:05 01/20/08 11:41:53.005 ### Go to timeout queue <0xb6977b90>05 01/20/08 11:41:53.005 ### skip the next job from timeout queue <0xb6977b90>What do those two lines mean? It looks like the command will just get skipped.

What also happens is that I try three commands fairly quickly after each other, and I only get the above two lines once. I'd expect at least six lines. Is there a way to get more verbose debugging output?

Domodude

I installed LMCE on a different machine, that I was previously using as an MD. And guess what! It works.

The wizard did not initially recognize the RS232 interface, of course. So I skipped it initially, then I went to the web panel and manually added a Pluto/ZWave device. This recognized the interface, and immediately the video-Lady came on. Just to make sure, I reloaded the dcerouter anyway. I went back to the Setup Wizard through the orbiter, and it recognized my interface. What's more, it already knew that I have three lights. Is that cool or what? Every step from that point on was easy and just *worked*. It's still working after a core reboot (that was a gamble on the other setup!).

So it seems that the ZCS201 is fully supported, obivously aside from the PnP-functionality.

It also seems that there are computers that have some sort of serial port stupidity going on that prevents proper communication. At the moment, I don't feel like investigating anymore. Perhaps later!

I installed LMCE on a different machine, that I was previously using as an MD. And guess what! It works.

The wizard did not initially recognize the RS232 interface, of course. So I skipped it initially, then I went to the web panel and manually added a Pluto/ZWave device. This recognized the interface, and immediately the video-Lady came on. Just to make sure, I reloaded the dcerouter anyway. I went back to the Setup Wizard through the orbiter, and it recognized my interface. What's more, it already knew that I have three lights. Is that cool or what? Every step from that point on was easy and just *worked*. It's still working after a core reboot (that was a gamble on the other setup!).

So it seems that the ZCS201 is fully supported, obivously aside from the PnP-functionality.

It also seems that there are computers that have some sort of serial port stupidity going on that prevents proper communication. At the moment, I don't feel like investigating anymore. Perhaps later!

I've started to update the Wiki with the implementation details I learned from communicating with Eugen on the Pluto Zwave implementation and with with going over his code to create an Insteon PLC driver. The code could use a clean up and a refresh to bring it up to the current Z-Wave standard of functionality and I think documenting its current fucntionality is a good first step. I'll be adding more to it over the next few days.

Domodude

Merten has a fairly substantial Z-wave product line, and on February 8th, a salesperson will come by and show me some of their stuff. I will let the forum know about current possibilities and issues. Merten also has a USB interface, I will check that one too (I'll probably need Hari's fresh hack ).