Simple Lua Scene not working

[m-joy 3]

Hello,

 

i have a simple scene to turn off lights:

Please login or register to see this code.

all of them are fibaro rgbw devices expect for ID 72. this is a fibaro power plug which is configured as "light" type. 

When i start the scene, all lights turn off as expected expect for the power plug with id 73. It stays on. When i manually control the ID 73 i did not experience any problems. The plug also works with the android app when i control lights.

What is wrong with this scene ?

 

Greets

[A.Socha 133]

Please login or register to see this code.

can you check is console what command it send after pressing button manually?

[m-joy 3]

Thank you so i missed the initialisation of "i" i guess. I will try this at home

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[petergebruers 1,268]

Like A.Socha said, you probably forgot to copy paste the initializer for "i". Or "i" was initialized somewhere else, so the loop doesn't start at 1, but at a number obtained somewhere else.

 

I would write it like this. Use 'ipairs" to iterate, test if device is off so you don't send "off" to an already "off" device, add a small delay.

Please login or register to see this code.

[m-joy 3]

Hello, I just checken my scene and i=1 was defined i just did not copy. I also tried the second solution but both scenes do not work. The switch does not react...

[m-joy 3]

Okay i just realized that the Power plug id changed after reinclusion.

My fault....

[petergebruers 1,268]

No worries! I'm glad it's solved. Thanks for the feedback.

[m-joy 3]

No worries! I'm glad it's solved. Thanks for the feedback.

 

 

Hello,

 

i want to thank you for the good idea of scene concept.

But the strange thing is, i thought it was the wrong ID,

but even with the correct ID it seems not work.

I will investigate this problem and keep you up to date.

[m-joy 3]

Okay i figuered out whats wrong.

Sometimes when i manually turn on the switch with the Hardware Button, the Controller Shows the device as being off. Since my new scene checks for on Status before turning off, it does not work.

The switch is located 3 m away from the hc2... Why does it show as off... Should i write a bug Report? Is it a global Problem or for my specific configuration mmm

[petergebruers 1,268]

I try to monitor this forum closely and I can't say there have been many reports with clear causes of "non reporting devices". Or to be more precise... "sometimes non-reporting" devices. As such, I can't say with certainty what to do... If it was *never* reporting back to the controller, I'd check the associations.

 

At the moment, I have 2 ideas. The first has to do with mesh networking. But since you freshly included the plug and it's close to the controller, well, I am not sure. But it's a bit like rebooting a computer or a phone: try it anyway.

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" /> So could you please go to Z-Wave network configuration, Mesh network reconfiguration, then select "Entire Z-Wave network". Wait at least 15 minutes before you try anything else. You'll see errors in the status bar for your battery operated devices, that is to be expected. You shouldn't see errors for your mains operated modules. If you haven't done this before, you might be surprised that you get status messages many hours after you've launched this command. This happens because the HC2 queues the "update nearest neighbor" to battery operated devices, and when they wake up, a status message appears.

 

The second possibility is that your Z-Wave network is very busy sometimes. Unfortunately, there is no diagnostic tool to find out. Possible causes are scenes, Vds and reporting from devices (for instances: power usage reporting on a Wall Plug). One possible test is this. Please make a dashboard and add the "scenes" panel. You'll have a quick overview of what is running on your HC2. Now stop all scenes. Or even better, certainly try this if scenes restart themselves quickly (because of a trigger), remove the checkmark next to "Active Scene" on the advanced page of the scene.

 

I'd like to have an idea of what is on your HC2 (devices,scenes,firmware versions). I'll send you a PM on how to communicate that.

[m-joy 3]

Hi Peter,

 

it is great to have people like you around.

I did check the assositations of the power plug.

It looks like this:

 

Endpoint 0

-Group 1

-Group 2

-Group 3

 

 

None of these groups had the HC2 set. I checked another power plug that worked and this plug had Group 3 assosiated with HC2 in Single Channel Assosiation.

I am not sure why Group 3 and not group 1 is used, but anyway.... I also put the HC2 in Group 3 of the non working power plug and now it seeems to work out. But i still have an eye on that.

Anyway, i do not know why the assosiation was not set because i never changed anything in the assosiation panel.

 

Greetings