Nodon Octan Remote with UI5 and UI7

manfaiho · September 3, 2015, 11:52pm

I tried to configure Nodon Octan remote into my VeraLite UI5 and VeraEdge UI7 for scene management but found very strange not being properly configured to set the scene association. In UI5, I can’t see the scene list box for 4 buttons ON and OFF. In UI7, it requests me to enter the number of buttons then create the scene list box for each button but no naming on which button # (except “false”). I also installed Aeon Minimote before which is very straight forward that I can use “Advance ZWave Device” Option then “add one” for battery-powered secondary scene in UI5. In UI7, I can even find the right brand Z device for configuration without any issue. Anyone can help? Many thanks.

amg0 · September 11, 2015, 6:53am

I have the same issue and reported it to MCV twice so far. I am on vera edge UI7.11
using Nodon Octan zWave and I tried both CENTRAL-SCENE and SCENE-ACTIVATION mode ( param 3 ), neither work fine but I do not believe it is an issue with the remove

by default , the remote is in CENTRAL-SCENE, in that mode, when I press one of the 4 button, I can see that the scene triggers “a Scene is Activated” is passed a value which is not correct.
for button 1 , 2 , 3 it receives 1 , 2 ,3 which is correct
for button 4 ( the - one ) , it receives 1 which is not correct
I have seen in the log that the variable sl_sceneActivated which is what the scene trigger receives I believe is the one not correct , it is indeed 1,2,3 for the first 3 button and 1 for the 4th button

What is really strange is that VERA does see the difference with the 4th button properly, in the log again, we can see the variable “LastSceneID” of the scene controller devices, receiving the right value 1, 2, 3 or 4 in the log. unfortunately this happens after the scene triggers are evaluated. I sent the logs to MCV, no reply yet

I also tried the remote in SCENE_ACTIVATION mode, in that scene each of the 4 button can report a different value depending on if it is clicked, double clicked, long click … ) in fact 4 buttons => 16 scenes should be possible
but in that mode again , we see the logs that the “LastSceneID” variables receives the good scene values but the sl_SceneActivated receives really strange values and unfortauntely, this is what the scene triggers gets passed in ( “a Scene is activated”, scene id ) when they are evaludated, so it does not work. and since this “LastSceneID” variables seems set after the trigger is evaluated, it is not even possible to read this value in the trigger lua or scene lua code…

really bad because the device is neat
I hope MCV can fix this

button 2 press

06 09/11/15 8:55:37.789 Device_Variable::m_szValue_set device: 208 service: urn:micasaverde-com:serviceId:SceneController1 variable: esl_SceneActivatede was: 2 now: 2 #hooks: 4 upnp: 0 skip: 0 v:0xad7750/NONE duplicate:0 <0x77012520> 07 09/11/15 8:55:37.790 Event::Evaluate 24 AUTO_GENERATED scene Nodon RP On is false repeat 0/-1 <0x77012520> 07 09/11/15 8:55:37.790 Event::Evaluate 25 AUTO_GENERATED scene Nodon RP Off is true users: allow:1 <0x77012520> 08 09/11/15 8:55:37.791 Scene::RunScene running 70 Nodon RP Off <0x77012520> 08 09/11/15 8:55:37.791 JobHandler_LuaUPnP::HandleActionRequest device: 24 service: urn:upnp-org:serviceId:SwitchPower1 action: eSetTargete <0x77012520> 08 09/11/15 8:55:37.792 JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x77012520> 06 09/11/15 8:55:37.792 Device_Variable::m_szValue_set device: 24 service: urn:upnp-org:serviceId:SwitchPower1 variable: eTargete was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0xada570/NONE duplicate:1 <0x77012520> 07 09/11/15 8:55:37.794 Event::Evaluate 26 AUTO_GENERATED scene Nodon RP On is false repeat 0/-1 <0x77012520> 07 09/11/15 8:55:37.794 Event::Evaluate 27 AUTO_GENERATED scene Nodon RP Off is false repeat 0/-1 <0x77012520> 06 09/11/15 8:55:37.795 Device_Variable::m_szValue_set device: 208 service: urn:micasaverde-com:serviceId:SceneController1 variable: eLastSceneIDe was: 2 now: 2 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x77012520> 06 09/11/15 8:55:37.795 Device_Variable::m_szValue_set device: 208 service: urn:micasaverde-com:serviceId:SceneController1 variable: eLastSceneTimee was: 1441953832 now: 1441954537 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x77012520>

button 4 press
(see the sl_sceneactivated taking the wrong value 1 and then later the LastSceneID taking the right value 4 but too late and wrong trigger is selected)

06 09/11/15 8:57:43.309 Device_Variable::m_szValue_set device: 208 service: urn:micasaverde-com:serviceId:SceneController1 variable: esl_SceneActivatede was: 2 now: 1 #hooks: 4 upnp: 0 skip: 0 v:0xad7750/NONE duplicate:0 <0x77012520> 07 09/11/15 8:57:43.310 Event::Evaluate 24 AUTO_GENERATED scene Nodon RP On is true users: allow:1 <0x77012520> 08 09/11/15 8:57:43.310 Scene::RunScene running 69 Nodon RP On <0x77012520> 08 09/11/15 8:57:43.311 JobHandler_LuaUPnP::HandleActionRequest device: 24 service: urn:upnp-org:serviceId:SwitchPower1 action: eSetTargete <0x77012520> 08 09/11/15 8:57:43.311 JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x77012520> 06 09/11/15 8:57:43.312 Device_Variable::m_szValue_set device: 24 service: urn:upnp-org:serviceId:SwitchPower1 variable: eTargete was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xada570/NONE duplicate:0 <0x77012520> 07 09/11/15 8:57:43.313 Event::Evaluate 25 AUTO_GENERATED scene Nodon RP Off is false repeat 0/-1 <0x77012520> 07 09/11/15 8:57:43.314 Event::Evaluate 26 AUTO_GENERATED scene Nodon RP On is false repeat 0/-1 <0x77012520> 07 09/11/15 8:57:43.314 Event::Evaluate 27 AUTO_GENERATED scene Nodon RP Off is false repeat 0/-1 <0x77012520> 06 09/11/15 8:57:43.315 Device_Variable::m_szValue_set device: 208 service: urn:micasaverde-com:serviceId:SceneController1 variable: eLastSceneIDe was: 2 now: 4 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x77012520> 06 09/11/15 8:57:43.315 Device_Variable::m_szValue_set device: 208 service: urn:micasaverde-com:serviceId:SceneController1 variable: eLastSceneTimee was: 1441954537 now: 1441954663 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x77012520>

manfaiho · September 28, 2015, 4:13am

I follow through the article their CEO, Thomas provided. Thank you so much for your excellent support, Thomas. It already resolved all of my problem.

In scene-activation mode, I can even configure all types of “press” for my various scenes using one Luup code. Please note that some typo on this document: One you need to check LastSceneID on IF statement which is required to use “”. Another one is the table of all types of “press” which are integers instead of hex code. Interesting and funny remote control even better Aeon Remote Enjoy!

manfaiho · September 28, 2015, 4:48am

Here is the table of all types of press for your reference. Thanks.

amg0 · September 28, 2015, 5:54am

[quote=“manfaiho, post:3, topic:188671”]I follow through the article their CEO, Thomas provided. Thank you so much for your excellent support, Thomas. It already resolved all of my problem.

In scene-activation mode, I can even configure all types of “press” for my various scenes using one Luup code. Please note that some typo on this document: One you need to check LastSceneID on IF statement which is required to use “”. Another one is the table of all types of “press” which are integers instead of hex code. Interesting and funny remote control even better Aeon Remote Enjoy![/quote]

can you point us to the Thomas’ article so we can have a look ? thank you

manfaiho · September 30, 2015, 9:17am

The doc is big and Thomas didn’t give me the download link. Ivcan send the doc to you by email.

Sent from my SM-G9200 using Tapatalk

Targeter · October 1, 2015, 12:53pm

I’m having the same problem and like to know a solution as well.

Targeter · October 6, 2015, 8:48pm

Can anyone shed any light on this?

amg0 · October 7, 2015, 6:05am

no solution that I know of , except:

1- use it in SCENE ACTIVATION mode

2- using ALTUI plugin or PLEG plugin or directly lua code, put a variable watch on the variable of LastSceneID of the Remote device

3- the values you will receive are the ones in the table listed above, (with ALTUI you can use a watch as a trigger for a scene, with PLEG you can fire an action , with LUA you ll need to write a callback function which triggers the run of a scene )

guntherp · October 14, 2015, 7:38am

Below the LUA code that works for me in scene activation, there are still some errors in the manual:

luup.call_delay('scene_controller',1)
function scene_controller()
   local lastSceneID = luup.variable_get("urn:micasaverde-com:serviceId:SceneController1","LastSceneID",#DEVICE_ID#)  
   if (lastSceneID == "#REMOTE_BUTTON_ID#") then
      luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "#scene_num#"}, 0)
   end
end

#DEVICE_ID# replace with octan remote device id
#REMOTE_BUTTON_ID#ervangen replace with button id (ex 10,20,30,40,…)
#scene_num# replace with vera scene id

backkri · October 22, 2015, 8:35pm

I have this code in my startup LUA:

luup.call_delay(‘scene_controller’,1)
function scene_controller()
local lastSceneID = luup.variable_get(“urn:micasaverde-com:serviceId:SceneController1”,“LastSceneID”,189)
if (lastSceneID == “2”) then
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”, “RunScene”, {SceneNum = “57”}, 0)
end
end

Scene 57 is a test scene which sets a virtual switch.

No matter what value I put in the lastSceneID compairison, the scene always triggers, independent which button I push on the remote…

Anyone else facing this problem or has suggestions on this subject?

backkri · October 22, 2015, 9:33pm

Got it working trough PLEG. But… >:(

If I push the buttons, the only values I get are 1,2,3 or 4. Double push or long push don’t change anything.

Regards,

Kristof.

amg0 · October 22, 2015, 9:35pm

Have you put the device in scene activation mod ? Zwave parameter 3 value 1

Envoy? de mon iPad en utilisant Tapatalk

guntherp · October 23, 2015, 9:44am

[quote=“backkri, post:11, topic:188671”]I have this code in my startup LUA:

luup.call_delay(‘scene_controller’,1)
function scene_controller()
local lastSceneID = luup.variable_get(“urn:micasaverde-com:serviceId:SceneController1”,“LastSceneID”,189)
if (lastSceneID == “2”) then
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”, “RunScene”, {SceneNum = “57”}, 0)
end
end

Scene 57 is a test scene which sets a virtual switch.

No matter what value I put in the lastSceneID compairison, the scene always triggers, independent which button I push on the remote…

Anyone else facing this problem or has suggestions on this subject?[/quote]

This is not going to work if you place in the startup LUA, you need to make a scene triggered on your remote with scene number 0.
Then you place your lua code in the scene’s lua code.

domlanz · October 31, 2015, 7:23am

I have a NodOn Soft Remote, which has the same challenges. I contacted the NodOn support and got the attached detailed manual how use the 16 options (same as described above with luup code). However, the manual is well mode, detailed, step-by-step. It may be helpful for some.

I also got the information that NodOn and Vera are working on simplifying things for the future.

Manual (too large to attach here): https://drive.google.com/file/d/0B1tOOx_kE2lGRS1uT1dSSWFGV1ktdGhaTWZvYms0a1FPUlpB/view?pli=1

Kullematz · November 3, 2015, 7:29pm

My Octan still don’t work correctly in Scene Activation Mode. I have followed all the instructions in the Tutorial, but whatever I configured under LastSceneID (like “10” for the left upper button), the scene will only execute if I press the lower right button (40,41,42,43) on the remote. The scene will even execute via remote without any LUUP-code! Therefore, I believe there is something wrong with the LUUP-code shown in the Tutorial.
Btw, I’m still on UI5 (1.5.672) with my VeraLite.

Kullematz · November 4, 2015, 9:10am

Here is the LUUP-code I have:

luup.call_delay(‘scene_controller’,1)
function scene_controller()
local lastSceneID = luup.variable_get(“urn:micasaverde-com:serviceId:SceneController1”,“LastSceneID”,101)
if (LastSceneID == “10”) then luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”, “RunScene”, {SceneNum = “40”}, 0)
end
end

Kullematz · November 4, 2015, 6:30pm

Interestingly, if I change LastSceneID == “40” and short press the lower right button on the remote (which generate a “40”) I get a blinking light (scene is a toggle light), which can be stopped if I press one of the buttons and generate any value but not “40” (e.g. double klick same button).

backkri · November 8, 2015, 1:17pm

Found some time to do some more testing, and indeed these 2 suggestions did the trick (also received the manual from Nodon support which describes this in detail. Not simple, but it works

[quote=“amg0, post:13, topic:188671”]Have you put the device in scene activation mod ? Zwave parameter 3 value 1

Envoy? de mon iPad en utilisant Tapatalk[/quote]

[quote=“guntherp, post:14, topic:188671”]This is not going to work if you place in the startup LUA, you need to make a scene triggered on your remote with scene number 0.
Then you place your lua code in the scene’s lua code.[/quote]

itgo · November 16, 2015, 4:14pm

Hi,
i followed all the instruction in the linked manual, testing both nodon wall switch and soft remote but they still don’t work correctly.
I’m on the ui7 last firmware.