KPL Relay + Zwave scenes

Hi there! First of all, I’d like to thank fba, who has done a ton of work to make this work. I am very surprised that vera people hasn’t purchased his work and include it in the standard package. seems like nonsense to me.

Anyway, after playing with this for a bit, i’ve finally managed to get most things up and running. I have a setup where I have 10 or so z-wave switches, blinds and plug-in modules. I didn’t like the way the z-wave scene controllers (with local load) were working so I switch 3 scene controllers with local load to insteon 6 button relays. I’ve managed to get the local load working no problem. I can control it now, no lag or anything, which is great, thanks again fba!

question is this now, can I use the 4 buttons to control scenes with z-wave devices? I see that the scene controller that’s added has no options to manage scene (in the scene tag, everything is empty). I’ve added all of the buttons to plm. Here is what I got when I added it to altsteon:

Cmd : add_device 1e.01.4f
1e.01.4f:001C,02,02 - Insteon version 2.

1e.01.4f:003D,02 - Device added. (0x02)

1e.01.4f:0007,FF,02,1E - DevCat : 02 SubCat : 1E

1e.01.4f:001C,02,02 - Insteon version 2.

1e.01.4f:002B,00,EA,01,1C,F8,6F,03,1C,01,0F,FF - Aldb record, Flags : EA Group : 01 Addr : 1C.F8.6F Data1 : 03 Data2 : 1C Data3 : 01 High : 0F Low : FF

1e.01.4f:002B,00,AA,01,1C,F8,6F,FF,1C,01,0F,F7 - Aldb record, Flags : AA Group : 01 Addr : 1C.F8.6F Data1 : FF Data2 : 1C Data3 : 01 High : 0F Low : F7

1e.01.4f:002B,00,EA,03,1C,F8,6F,03,1C,03,0F,EF - Aldb record, Flags : EA Group : 03 Addr : 1C.F8.6F Data1 : 03 Data2 : 1C Data3 : 03 High : 0F Low : EF

1e.01.4f:002B,00,AA,01,1C,F8,6F,FF,1C,03,0F,E7 - Aldb record, Flags : AA Group : 01 Addr : 1C.F8.6F Data1 : FF Data2 : 1C Data3 : 03 High : 0F Low : E7

1e.01.4f:002B,00,EA,04,1C,F8,6F,03,1C,04,0F,DF - Aldb record, Flags : EA Group : 04 Addr : 1C.F8.6F Data1 : 03 Data2 : 1C Data3 : 04 High : 0F Low : DF

1e.01.4f:002B,00,EA,05,1C,F8,6F,03,1C,05,0F,D7 - Aldb record, Flags : EA Group : 05 Addr : 1C.F8.6F Data1 : 03 Data2 : 1C Data3 : 05 High : 0F Low : D7

1e.01.4f:002B,00,AA,01,1C,F8,6F,FF,1C,06,0F,CF - Aldb record, Flags : AA Group : 01 Addr : 1C.F8.6F Data1 : FF Data2 : 1C Data3 : 06 High : 0F Low : CF

1e.01.4f:002B,00,EA,06,1C,F8,6F,03,1C,06,0F,C7 - Aldb record, Flags : EA Group : 06 Addr : 1C.F8.6F Data1 : 03 Data2 : 1C Data3 : 06 High : 0F Low : C7

1e.01.4f:002C,00 - ALDB records end.

1e.01.4f:0008,02,FF - 1e.01.4f button/group 255 is on.

Which tells me it sees all of the buttons. I couldn’t find any info on actual scene creation and management so I’m find of stuck now.

Any help?

Thanks

I believe that the scene would have to use the kpl button you want as a trigger.

  • Garrett

Strange but after some playing around, now only the local load appears as a device. When going through trigger options, I see _Scene Controller there but no options for buttons. Any direction would be appreciated

And one more question, one of the kpl’s does not have any local load attached to it. Is there any way to use the local load buttons to control scenes?

anybody? ;D

I’m having a similar issue. I have two KeypadLinc’s in my living room. I’m using Altsteon software to control them. My plan was to use the scene buttons to run both Insteon and Z-Wave devices. I have been able to control a Z-Wave light switch and an Insteon OutletLinc Dimmer from the KeypadLinc’s ON/OFF button so I’m assuming the scene buttons would yield the same results.

– dima237, I think this answers one of your question. I think since it’s possible to control a Z-Wave device with the ON/OFF (programmically, not with the load) then it should be able to control a Z-Wave device with a scene button.

After creating the KeypadLinc device(s), Altsteon created the KeypadLinc Scene Controller automatically. This is where I’m stuck. Shouldn’t I see options under the Scene’s tab of the configuration page of the scene controller? I’ve attached a few pics for clarity.

What am I missing?

No, when creating a scene you set up a trigger and select the scene controller. You will then select something like a button is pressed in the action drop down. You then choose the correct button number.

  • Garrett

Thank you. That was it!

For whatever reason though, vera (or actually altsteon) stopped adding the scene controller as a second device. I only get the main switch and that’s it. I tried both Device type : urn:geektaco-info:device:dimmer-kpl:1 as per instructions and and Device type : urn:geektaco-info:device:relay-kpl:1 as per intuition. Nothing. Just get steady working main switch and no scene controller

Mine didn’t populate until I used the Reload button. Try deleting the device and adding it back in, then hit Reload.

I’m still new at this so take my advice with that in mind…

Fixed! by re-uploading all xml files. Now I can control scene when the scene button on kpl is on, but when scene is turned off, that doesn’t seem to be caught as a trigger. Is that right? still fighting :slight_smile:

Ok, a little more debugging got me here:

I have two scenes, hall on and hall off. They are set to be run as: “hall on” runs on “scene a” on and “hall off” on “scene a” off.

But when looking through logs, I see that only Hall On scene is being considered:

50 09/02/12 0:41:38.181 luup_log:67: Parsing : 1e.01.4f:0008,00,03 - 1e.01.4f button/group 3 is on. <0x2db69680>
50 09/02/12 0:41:38.182 luup_log:67: Sending to child id 69 (1e.01.4f) <0x2db69680>
50 09/02/12 0:41:38.182 luup_log:67: Scene 03 has been activated. <0x2db69680>
06 09/02/12 0:41:38.182 Device_Variable::m_szValue_set device: 70 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 4 now: 3 #hooks: 1 upnp: 0 v:0xee4720/NONE duplicate:0 <0x2db69680>
07 09/02/12 0:41:38.183 Event::Evaluate 1 Hall On scene Hall On is true users:(null) allow:1 <0x2db69680>
08 09/02/12 0:41:38.183 Scene::RunScene running 22 Hall On <0x2db69680>

after that:

50 09/02/12 0:41:55.881 luup_log:67: Parsing : 1e.01.4f:0009,00,03 - 1e.01.4f button/group 3 is off. <0x2db69680>
50 09/02/12 0:41:55.882 luup_log:67: Sending to child id 69 (1e.01.4f) <0x2db69680>
50 09/02/12 0:41:55.882 luup_log:67: Scene 03 has been deactivated. <0x2db69680>
06 09/02/12 0:41:55.882 Device_Variable::m_szValue_set device: 70 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 3 now: 3 #hooks: 1 upnp: 0 v:0xee4720/NONE duplicate:0 <0x2db69680>
07 09/02/12 0:41:55.883 Event::Evaluate 1 Hall On scene Hall On is true users:(null) allow:1 <0x2db69680>
08 09/02/12 0:41:55.883 Scene::RunScene running 22 Hall On <0x2db69680>

This is probably a question for fba. What could I be doing wrong?

Still stuck. Could someone help me debug this ? ::slight_smile: I’m just not sure if it’s me or is it really supposed to work like this (no scene off functionality)

It appears that fba has been mia for a few weeks. I am not sure if I’ll have time to mess with my KPL switch in the next few days. But if I can some time, I’ll create a scene to see if I can get the off portion of the scene button to work. It would be you or the kpl plugin files. But if I have the same problem, it could be the kpl files.

  • Garrett

That would be great thanks! Let’s see if you can replicate the same problem. I’m sure it’s easy to fix, as altsteon is sending the right information, just a matter of interpreting it properly. I didn’t want to mess with the parsing functions myself…

dima237,

Good news, I was able to solve the issue by making a few modifications to a few files. It was in fact an issue in the plugin files and not you. :slight_smile:

Here are the updated files for both the relay and dimmer kpl.

  • Garrett

Wow! thank you very much! I will try this when I get home and report back. When in Toronto, a beer or two are on me :slight_smile:

UPDATE: WORKED LIKE A CHARM!! thanks a million. These two files need to get picked up by fba to be updated in the distribution.

Next on the menu, trying to sync the scene button lights to reflect reality if device is turn off by a different method.

By the way, I can confirm that local load buttons can be used as triggers for a scene. I have one kpl, that’s not connected to a local load, so I use now the ON and OFF buttons to control a neighbouring light

;D

As always wanting to perfect the solution a little more… Has anyone done anything about the syncing of scene buttons? I see that all of the functionality in the binary is there (as in there is a function to turn on and off led’s behind scene buttons). I’m not sure if the led status actually changes the status of the scene button (if I manually turn on the led behind “scene a” and press “scene a” will be be interpreted as “scene A off”?). If that’s the case, then I somehow think it should be possible to code some sort of check at the end of scene execution, which triggers participate in that scene and set them accordinly depending on the status of the scene devices. If we can get this syncing in place, I can’t think of anything else that really needs improvement, at least in my setup

fba and myself were working on this awhile back. At this point it is not working. The commands to change the led light status was not working for me via the command line. it would cause some wonky issues with the plm/kpl (causing it to be unresponsive). Fba said he was going to look into it, but no new news.

  • Garrett

Thanks! I can confirm the same. I was playing with set status led, and got the kpl being unresponsive, keys would become unpressable etc. hopefully fba will have some time to look into it.

I’m trying to get the same functionality as dima237, with a 6 button kpl, of scene on - scene off control. I’ve loaded the new .xml files provided by Garrett (Thanks) onto the vera and hit the reload button, but still have the same operation - the scene off isn’t being recognized.

I also tried deleting the devices and recreating them, that did not help.

I’ve attached a screenshot of how I’m creating the scene trigger. Can anyone tell me what I’m doing wrong?