The Vera Community forums have moved!

General => Lighting & Load Control => Topic started by: thedeadstone on April 21, 2013, 05:17:58 pm

Title: Veralite doesn't get scene id from controller
Post by: thedeadstone on April 21, 2013, 05:17:58 pm
Hello! I'm very new at z-wave and I need help.

I have Veralite, lamp with z-wave and Duwi scene controller 05443.

I've successfully added my two z-wave devices to Verlite, created two scenes - to switch lamp on and off. When I run these scenes from Veralite everything works fine.

But when I try to add triggers to scenes there is a problem. Vera gets only two scenes ID from scene controller - 0 and 1. But my scene controller has about 12 different scenes:

Scene 1: Single Click on Upper Part of Paddle
Scene 2: Single Click on Lower Part of Paddle
Scene 3: Single Click Dim Up
Scene 4: Single Click Dim Down
Scene 5: Single Click Dim Up Stop
Scene 6: Single Click Dim Down Stop
Scene 11: Double Click on Upper Part of Paddle
Scene 12: Double Click on Lower Part of Paddle
Scene 13: Double Click Dim Up
Scene 14: Double Click Dim Down
Scene 15: Double Click Dim Up Stop
Scene 16: Double Click Dim Down Stop

I added two configuration settings to scene controller as it said in http://en.z-wave.me/docs/ZME_06443_UserManual.pdf, but it didn't help.
Veralite only understand scene 1 (Single Click on Upper Part of Paddle), but all other are scene 0 for Veralite.

Then I tried to watch the logs of Veralite, and I figured out that my scene controller is actually sending right scene ID.

Code: [Select]
02 04/21/13 13:47:04.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:47:04.236 <0x2c1ff680>
02 04/21/13 13:48:34.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:48:34.236 <0x2c1ff680>
02 04/21/13 13:50:04.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:50:04.236 <0x2c1ff680>
02 04/21/13 13:51:34.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:51:34.266 <0x2c1ff680>
08 04/21/13 13:52:24.698 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: LogIpRequest <0x2d3ff680>
08 04/21/13 13:52:24.699 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x2d3ff680>
08 04/21/13 13:52:24.699 JobHandler_LuaUPnP::HandleActionRequest argument action=LogIpRequest <0x2d3ff680>
08 04/21/13 13:52:24.699 JobHandler_LuaUPnP::HandleActionRequest argument IpAddress=192.168.1.34 <0x2d3ff680>
08 04/21/13 13:52:24.700 JobHandler_LuaUPnP::HandleActionRequest argument MacAddress=5c:0a:5b:9f:2f:95 <0x2d3ff680>
02 04/21/13 13:53:04.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:53:04.236 <0x2c1ff680>
08 04/21/13 13:53:18.557 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: LogIpRequest <0x2ddff680>
08 04/21/13 13:53:18.558 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x2ddff680>
08 04/21/13 13:53:18.558 JobHandler_LuaUPnP::HandleActionRequest argument action=LogIpRequest <0x2ddff680>
08 04/21/13 13:53:18.558 JobHandler_LuaUPnP::HandleActionRequest argument IpAddress=192.168.1.34 <0x2ddff680>
08 04/21/13 13:53:18.558 JobHandler_LuaUPnP::HandleActionRequest argument MacAddress=5c:0a:5b:9f:2f:95 <0x2ddff680>
02 04/21/13 13:54:34.103 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:54:34.236 <0x2c1ff680>
02 04/21/13 13:56:04.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:56:04.266 <0x2c1ff680>
02 04/21/13 13:57:34.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:57:34.236 <0x2c1ff680>
02 04/21/13 13:59:04.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 13:59:04.266 <0x2c1ff680>
06 04/21/13 13:59:21.785 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 0 now: 0 #hooks: 2 upnp: 0 v:0xbaaf10/NONE duplicate:0 <0x2c1ff680>
07 04/21/13 13:59:21.786 Event::Evaluate 1 11 scene Lamp on is false repeat 0/-1 <0x2c1ff680>
07 04/21/13 13:59:21.786 Event::Evaluate 2 2 scene Lamp off is false repeat 0/-1 <0x2c1ff680>
06 04/21/13 13:59:21.786 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneID was: 11 now: 11 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2c1ff680>
06 04/21/13 13:59:21.787 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneTime was: 1366576295 now: 1366577961 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>
08 04/21/13 14:00:04.617 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: LogIpRequest <0x2d3ff680>
08 04/21/13 14:00:04.617 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1 <0x2d3ff680>
08 04/21/13 14:00:04.617 JobHandler_LuaUPnP::HandleActionRequest argument action=LogIpRequest <0x2d3ff680>
08 04/21/13 14:00:04.618 JobHandler_LuaUPnP::HandleActionRequest argument IpAddress=192.168.1.34 <0x2d3ff680>
08 04/21/13 14:00:04.618 JobHandler_LuaUPnP::HandleActionRequest argument MacAddress=5c:0a:5b:9f:2f:95 <0x2d3ff680>
02 04/21/13 14:00:34.102 ZW_Send_Data node 2 NO ROUTE (nil) <0x2c3ff680>
04 04/21/13 14:00:34.246 <0x2c1ff680>
06 04/21/13 14:01:02.735 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 0 now: 0 #hooks: 2 upnp: 0 v:0xbaaf10/NONE duplicate:0 <0x2c1ff680>
07 04/21/13 14:01:02.736 Event::Evaluate 1 11 scene Lamp on is false repeat 0/-1 <0x2c1ff680>
07 04/21/13 14:01:02.736 Event::Evaluate 2 2 scene Lamp off is false repeat 0/-1 <0x2c1ff680>
06 04/21/13 14:01:02.736 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneID was: 11 now: 14 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>
06 04/21/13 14:01:02.737 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneTime was: 1366577961 now: 1366578062 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>
06 04/21/13 14:01:03.725 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 0 now: 0 #hooks: 2 upnp: 0 v:0xbaaf10/NONE duplicate:0 <0x2c1ff680>
07 04/21/13 14:01:03.726 Event::Evaluate 1 11 scene Lamp on is false repeat 0/-1 <0x2c1ff680>
07 04/21/13 14:01:03.726 Event::Evaluate 2 2 scene Lamp off is false repeat 0/-1 <0x2c1ff680>
06 04/21/13 14:01:03.726 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneID was: 14 now: 16 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>
06 04/21/13 14:01:03.727 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneTime was: 1366578062 now: 1366578063 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>
06 04/21/13 14:01:05.775 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 0 now: 0 #hooks: 2 upnp: 0 v:0xbaaf10/NONE duplicate:0 <0x2c1ff680>
07 04/21/13 14:01:05.776 Event::Evaluate 1 11 scene Lamp on is false repeat 0/-1 <0x2c1ff680>
07 04/21/13 14:01:05.776 Event::Evaluate 2 2 scene Lamp off is false repeat 0/-1 <0x2c1ff680>
06 04/21/13 14:01:05.776 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneID was: 16 now: 12 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>
06 04/21/13 14:01:05.777 Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneTime was: 1366578063 now: 1366578065 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>

I can see in logs that LastSceneID is changing through the time to the right button combination that I use one my scene controller. But triggers for these scenes doesn't work.

Maybe it is somehow connected with sl_SceneActivated variable in logs, I don't know.

Does anyone have any ideas what can I do?
Title: Re: Veralite doesn't get scene id from controller
Post by: oTi@ on April 25, 2013, 09:44:00 am
@thedeadstone,

Welcome!

I have no experience with the Duewi scene controller. Does it actually show as a scene controller in Vera?
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on April 28, 2013, 05:14:58 am
Yes, it is scene controller

Title: Re: Veralite doesn't get scene id from controller
Post by: RexBeckett on April 28, 2013, 05:40:25 am
How did you setup your scene triggers?  What you need to do is:

Under Automation tab, click New scene and enter an appropriate name (instead of New scene). Go to TRIGGERS tab and click Add trigger. Select your controller in the Device pull-down and in the What type of event is the trigger? pull-down, select A scene is activated. Give your trigger a catchy name and enter the controller scene number (1-16) in Which scene number. Click  Confirm changes, click Save/Reload and refresh your browser page. The new scene should show up in your scene controller's UI. You may need to repeat the Reload and browser refresh.

Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on April 28, 2013, 10:59:21 am
It was done absolutely as you said.

Here is screenshop of my trigger
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on May 02, 2013, 06:42:14 am
I've found similar problem here:
http://forum.micasaverde.com/index.php?topic=9182.5
As far as is understand it is Vera problem.

It is told in this post http://forum.micasaverde.com/index.php/topic,9182.msg79140.html#msg79140 that you have to change Vera firmware.
download.mios.com/brcm_betafirmware/wl500gP_Luup_ui5-1.5.401-en-mios.squashfs
But it is for Vera2. And firmware is too old.
Can I try to use this old firmware?
Title: Re: Veralite doesn't get scene id from controller
Post by: garrettwp on May 02, 2013, 06:57:58 am
You can not use Vera2 firmware with VeraLite or Vera3. They are different platforms and will not work. Also 1.5.401, even though it had the changes for the scene controllers, there have been a lot of changes from 1.5.401 to 1.5.622.

- Garrett
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on May 03, 2013, 01:49:32 am
Do you have any ideas what I can do?
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on May 08, 2013, 04:11:25 pm
I will ask again..

My switch is working ok with two scenes - 0 and 1. It really turns on and turn off my lamp. Strange thing is that double click up button also turns off my lamp.

Here are my settins:
http://i48.fastpic.ru/big/2013/0508/b5/7e8ee2dff7bbb07ea2776e75a137d0b5.png (http://i48.fastpic.ru/big/2013/0508/b5/7e8ee2dff7bbb07ea2776e75a137d0b5.png)

http://i47.fastpic.ru/big/2013/0508/c6/17e15cbf2f32551f97adcc2f3011b8c6.png (http://i47.fastpic.ru/big/2013/0508/c6/17e15cbf2f32551f97adcc2f3011b8c6.png)

http://i47.fastpic.ru/big/2013/0508/3b/fda44414f72721487c9db7d89d62023b.png (http://i47.fastpic.ru/big/2013/0508/3b/fda44414f72721487c9db7d89d62023b.png)

And here is logs, where the first red block - it is when i press up button, second red block - down button.

http://i47.fastpic.ru/big/2013/0508/96/15fa2a8a1b00633af4aaf6110cc21a96.png (http://i47.fastpic.ru/big/2013/0508/96/15fa2a8a1b00633af4aaf6110cc21a96.png)

And this is logs when i use long press down:
http://i47.fastpic.ru/big/2013/0508/f8/e121eaed0396883c7bafb7e3641dc1f8.png (http://i47.fastpic.ru/big/2013/0508/f8/e121eaed0396883c7bafb7e3641dc1f8.png)
I can see here than variable LastSceneID is changed to 4, but trigger for this scene number doesn't work.
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on May 16, 2013, 10:45:18 am
Please someone help!
Title: Re: Veralite doesn't get scene id from controller
Post by: oTi@ on May 17, 2013, 12:33:59 pm
Is this your only type of scene controller, or do you have others? If so, what brand/model are they?
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on May 21, 2013, 06:08:06 am
This is only type I have.
Title: Re: Veralite doesn't get scene id from controller
Post by: oTi@ on May 24, 2013, 09:07:47 am
Are you interested in a small experiment? (Requires making a backup, access to the log files, and executing a few lines of Luup code.)
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on May 28, 2013, 01:24:45 pm
Are you interested in a small experiment? (Requires making a backup, access to the log files, and executing a few lines of Luup code.)

Absolutelly!
Title: Re: Veralite doesn't get scene id from controller
Post by: thedeadstone on June 03, 2013, 03:46:13 pm
oTi@, i'm still waiting for experiment. You can access me via Skype (thedeadstone). And I can give you remote access to Veralite interface.
Title: Re: Veralite doesn't get scene id from controller
Post by: mulb on July 15, 2013, 08:45:44 am
Hello,

I have the same issue with a Duwi controller.
When I single press up, it triggers scene 1, but it does not work for other scenes.
As a matter of fact, each time I activate another scene, the log puts the right scene number in LastSceneID, but the sl_SceneActivated is always 0 or 1 !!

It's the same in you exemple

06   04/21/13 14:01:02.735   Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 0 now: 0 #hooks: 2 upnp: 0 v:0xbaaf10/NONE duplicate:0 <0x2c1ff680>
07   04/21/13 14:01:02.736   Event::Evaluate 1 11 scene Lamp on is false repeat 0/-1 <0x2c1ff680>
07   04/21/13 14:01:02.736   Event::Evaluate 2 2 scene Lamp off is false repeat 0/-1 <0x2c1ff680>
06   04/21/13 14:01:02.736   Device_Variable::m_szValue_set device: 4 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneID was: 11 now: 14 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2c1ff680>


What can we do to have vera take the right scene ID into account?

Mulb
Title: Re: Veralite doesn't get scene id from controller
Post by: mulb on July 22, 2013, 04:42:35 am
Hello,

after several hours, I found a solution !!

As explained in my last message, the good information is not sl_SceneActivated but LastSceneID.
So the idea is to take this field into account.
I created a scene, which is activated by all scene IDs (in my case, 0, 1, 2 6 and 99 are seen in sl_SceneActivated)

After, in this scene, I get the LastSceneID of my Duwi controller with the following command.
 local BoutonActifget = luup.variable_get("urn:micasaverde-com:serviceId:SceneController1", "LastSceneID", 66)

Then depending on the answer, I run the scene I want :
 if BoutonActif == 1 then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "0"}, 65)
  elseif  BoutonActif == 2  then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, 65)
 
and so on.....

But it was still not working. With the help of the logs, I understood that the LastSceneID taken was the one of the previous click.
One solution is to delay the luup.variable_get

The solution is to create a function and call this function with delay (0.01 second, which is not visible, but enough to have the variable with the right scene.
Code: [Select]
luup.call_delay('chambre', 0.01)

function chambre()
  local BoutonActifget = luup.variable_get("urn:micasaverde-com:serviceId:SceneController1", "LastSceneID", 66)

 if BoutonActif == 1 then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "0"}, 65)
  elseif  BoutonActif == 2  then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, 65)
 elseif BoutonActif == 3 then
    luup.call_action("urn:upnp-org:serviceId:WindowCovering1","Up",{ },3)
  elseif BoutonActif == 4 then
    luup.call_action("urn:upnp-org:serviceId:WindowCovering1","Down",{ },3)
  elseif BoutonActif == 5 then
    luup.call_action("urn:upnp-org:serviceId:WindowCovering1","Stop",{ },3)
  elseif BoutonActif == 6 then
    luup.call_action("urn:upnp-org:serviceId:WindowCovering1","Stop",{ },3)
  elseif BoutonActif == 11 then
    luup.call_action("urn:upnp-org:serviceId:Dimming1","SetLoadLevelTarget",{newLoadlevelTarget=100},3)
  elseif BoutonActif == 12 then
    luup.call_action("urn:upnp-org:serviceId:Dimming1","SetLoadLevelTarget",{newLoadlevelTarget=0},3)
  end
end

AND IT WORKS perfectly !!!

I can open or close my shutter, turn on and off my lamp depending on how I click on the Duwi :)

Mulb

Title: Re: Veralite doesn't get scene id from controller
Post by: gdeboos on August 21, 2013, 07:47:27 am
How did you guys get the Duwi 05443 to accept the variables?
I have entered them and tried the configure now button + Duwi up/down x3 but this does not work.
:(

have tried repeating the x3 Duwi presses after different intervals but can not get the information to the device.
Title: Re: Veralite doesn't get scene id from controller
Post by: fepalmytho on November 07, 2013, 10:58:44 am
Hi everybody,

I would like to share with you the solution to correctly parameter the scene controller DUWI 06443.

I used the precious advice from MULB, who put me on the right way, but i will detail it:

Also i noticed mistakes on his code, so mine is correct, and working.

You will find my code below:

Where 44 is the ID of my scene controller (duwi).
33 is the ID of one light relay.
43 another one.

You have to get in mind that:
Parameters 13 and 14 of the controller need to be set at "3", but i think you know that.
Then, Scenes from 1 to 6 and 11 to 16 are definitely sent correctly by the scene controller to the Vera, (i will show you why).
Those scenes depends on how you press UP and Down buttons (short or long, double, etc...), but i think you know that.

Press once on the UP button, you should get the scene ID "1", lets verify this.
Refresh the page, and go into parameters of your scene controller.

When you enter in the advanced parameters of your scene controller (see picture), you will notice two parameters:
sl_SceneActivated and LastSceneID.
In my example, sl_SceneActivated is set at "12", and LastSceneID at "6" (cause in my case i did a LONG DOWN).
You should have whatever on sl_SceneActivated, but "1" on LastSceneID (cause you did SHORT UP).
It's the sl_SceneActivated which is tricky, cause it's this one that the vera will "see", and not the LastSceneID.

But why is it tricky?
Cause this parameter is totally "random".
In my case, when i press long up or long down, i get the same sl_SceneActivated to 12.
(But the parameter LastSceneID is correct, 5 or 6).
And Vera "see" only this parameter sl_SceneActivated.
So if you created a scene or a module depending on this parameter, it will be commanded by both actions, and that's not what we want. (in my case, when i pressed UP long, all my lights were Off, and i didnt get why).
So the aim is to know all the sl_SceneActivated that are sent from your scene controller.
Then, when you get all those parameters, you create a scene which will be triggered by all of them.
And INSIDE this scene, you will create the LUUP code that will launch the correct command.
It's really easy!

In my case, i did a draft of my buttons, UP, DOWN, LONG and DOUBLE.
I did all the possibilities, step by step, refreshing the page each time, going to advanced parameters of my scene controller, and noting the sl_SceneActivated accordingly.
That's how i noticed that pressing Long Up or Long down, the same sl_SceneActivated was sent to my Vera...
After that, i created a scene (called "Exterior scenes"), which was triggered by all these numbers.
Example:
module: scene controller
type: a scene is activated
name:12
scene:12

and i created triggers as much as i got different sl_SceneActivated numbers.

Then, and finally, i created the Luup code who will differentiate the sl_SceneActivated and the LastSceneID( which is the one that is correct and we need).
See the code below:
You see that "BoutonActif" is READING the LastSceneID, which is CORRECT.
Then, you just need to decide what to do with this ID.
In my case:
Short UP switch on my Light on the relay 33.
Long UP switch Off this light.
Short Down switch on my Light on the relay 43.
Long Down switch Off this light.


luup.call_delay('jardin', 1)

function jardin()
  local BoutonActif = luup.variable_get("urn:micasaverde-com:serviceId:SceneController1", "LastSceneID", 44)

 if (BoutonActif == "1") then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, 33)
  elseif  (BoutonActif == "2")  then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, 43)
elseif  (BoutonActif == "5")  then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "0"}, 33)
elseif  (BoutonActif == "6") then
    luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "0"}, 43)
end
end

Enjoy!

Fred.
Title: Re: Veralite doesn't get scene id from controller
Post by: monions on November 07, 2013, 12:11:24 pm
@fepalmytho,

This is brilliant - and such a simple solution.

I've been trying to write a guide to help people use this device but found that while the assigned si_SceneActivated is random, it is consistent. It's just random between different VERAs.

I've tested your solution, but just to confirm.

You create a scene and for this scene you create triggers for each of the scene numbers that are different.

For instance in my system

SceneActivated = 1, Last Scene = 1
SceneActivated = 5, Last Scene = 2

From this you can see a single down press creates a scene number 5 (not 2)

In the scene I have created a trigger for scene ID 5.

Then put the LUA code and actions (changing the Scene controller ID number and device numbers for the actions) into the LUA section.



 
Title: Re: Veralite doesn't get scene id from controller
Post by: fepalmytho on November 08, 2013, 07:05:45 am
Hi Monions,

That's totally right.

The only thing that i didn't investigate, is how to assign a long press (Up or Down), to a dimmer relay (O to 100%).

I don't need it actually, but i think it could be useful.

If someone wants to give a try...

Have a nice day,

Title: Re: Veralite doesn't get scene id from controller
Post by: mulb on January 14, 2015, 09:42:17 am
Hi,

I did the try on the long press...
the result is that you have one information for the beginning of the press, in my case (LastSceneID= 3 (up),LastSceneID = 4 (down))
and one information when you stop pressing (in my case, 5 and 6).

I use it for my roller shutter, launch open the roller shutter when I start pressing (LastSceneID = 3),
  elseif BoutonActif == 3 then
    luup.call_action("urn:upnp-org:serviceId:WindowCovering1","Up",{ },3)
 and stops it when I stop pressing ( LastSceneID = 5)

 elseif BoutonActif == 5 then
    luup.call_action("urn:upnp-org:serviceId:WindowCovering1","Stop",{ },3)

See my first post for the full code.

Mulb