Is V5 Missing "Copy Attributes from Scene"?

[TrojanHorse]

I no longer see the "copy attributes from scene" button when selecting a controller in a scene.  I believe I read before that this functionality doesn't exist in v5.  Is that true?  Is there another method or workaround for this functionality?

[Michel Kohanim]

@TrojanHorse,

Unfortunately yes since, with multi protocol scenes, it's rather difficult to apply the same login to nodes that are applied to scenes.

With kind regards,
Michel

[TrojanHorse]

2 hours ago, Michel Kohanim said:

@TrojanHorse,

Unfortunately yes since, with multi protocol scenes, it's rather difficult to apply the same login to nodes that are applied to scenes.

With kind regards,
Michel

Thank you.  I figured that might be the reason.  

[apostolakisl]

3 hours ago, Michel Kohanim said:

@TrojanHorse,

Unfortunately yes since, with multi protocol scenes, it's rather difficult to apply the same login to nodes that are applied to scenes.

With kind regards,
Michel

I very much miss this feature.  Are you sure there isn't a way to put it back?  Perhaps it just excludes nodes that are potentially inconsistent with it, or maybe it prompts you through each device in the scene with the settings it thinks are correct and you hit "apply" if all is good, or make changes and then hit "apply".  It can be very tedious when you have a scene with several controllers and a bunch of responders to do this manually one by one.  

[kevinvw]

Ouch.  Took the leap to 5.0.16 awhile back and just now trying to configure a fanlinc in my network.  the steps in the wiki include using copy scene attributes, but seems to be for V4 firmware.  Are there updated steps for adding a fanlinc and all the scenes using V5?  Right now, fan buttons aren't working, and they all seem to illuminate but not go off as buttons are pressed.

 

Oh, also noticed the option to replace a failed device is missing.

Thanks for the help.

 

Update... hmmm, looking back at each scenes controller, noticed the On Level pull down was high for all... Im sure I et those correctly earlier... .may be going bonkers... any reason those settings would all revert to high or am I just crazy.

 

 

[lilyoyo1]

7 hours ago, kevinvw said:

Ouch.  Took the leap to 5.0.16 awhile back and just now trying to configure a fanlinc in my network.  the steps in the wiki include using copy scene attributes, but seems to be for V4 firmware.  Are there updated steps for adding a fanlinc and all the scenes using V5?  Right now, fan buttons aren't working, and they all seem to illuminate but not go off as buttons are pressed.

 

Oh, also noticed the option to replace a failed device is missing.

Thanks for the help.

 

Update... hmmm, looking back at each scenes controller, noticed the On Level pull down was high for all... Im sure I et those correctly earlier... .may be going bonkers... any reason those settings would all revert to high or am I just crazy.

 

 

Setting up scenes now is similar as it was in the past. Instead of using sliders you have the drop the box. 

My fanlincs didn't change their settings when I upgraded. With that said, I've been on 5.0 since the beginning do I don't know if that has anything to do with it

[lilyoyo1]

21 hours ago, apostolakisl said:

I very much miss this feature.  Are you sure there isn't a way to put it back?  Perhaps it just excludes nodes that are potentially inconsistent with it, or maybe it prompts you through each device in the scene with the settings it thinks are correct and you hit "apply" if all is good, or make changes and then hit "apply".  It can be very tedious when you have a scene with several controllers and a bunch of responders to do this manually one by one.  

You can always add the responders to your scene first, configure them in the scene, and then add the controllers. This will transfer the settings to the controllers the way they are.

[kevinvw]

In cleaning up some of my programs since moving to v5, I am not able to command a scene or controller to a % on level.  Only on or off is listed.

If I want to turn on a light to 50% at night, how do I now do that?

 

Update:. I see in other programs that if the device is a switchlinc the option to set brightness is available.. but not for kpl.  Has this always been so?  I guess I can create a separate scene for the program?

 

Ok, maybe I'm getting a bit smarter.  When I select 'on', the brightness pop up was greyed out in the program line... But it works anyway if clicked.

Ok, one more question.  In a action statement, I can set a scene to on and set a brightness %.  But this can't work, correct?  Why is this even an option in the UI?

Don't meant to be critical... In fact I love my isy.... I think I'm just on the learning curve to v5 firmware

[apostolakisl]

On 11/19/2019 at 7:39 PM, kevinvw said:

In cleaning up some of my programs since moving to v5, I am not able to command a scene or controller to a % on level.  Only on or off is listed.

If I want to turn on a light to 50% at night, how do I now do that?

 

Update:. I see in other programs that if the device is a switchlinc the option to set brightness is available.. but not for kpl.  Has this always been so?  I guess I can create a separate scene for the program?

 

Ok, maybe I'm getting a bit smarter.  When I select 'on', the brightness pop up was greyed out in the program line... But it works anyway if clicked.

Ok, one more question.  In a action statement, I can set a scene to on and set a brightness %.  But this can't work, correct?  Why is this even an option in the UI?

Don't meant to be critical... In fact I love my isy.... I think I'm just on the learning curve to v5 firmware

what do you mean "action statement"

[kevinvw]

Sorry, referring to a then line in my program ..

Action - your devices - front kpl.1 on 85%

 

That line works, but the pull down includes scenes... I created a test scene with just the kpl.1 button as a responder.

That doesn't work... I don't think it ever has.  I am suggesting those items in the on/off/... Pull down have illogical items be removed.