Fibaro Dimmer SceneActivation on S2 - should this trigger associations? Under what conditions? Other association questions

[MrNoTip 2]

Eugh. Long post explaining the problem and asking for help is no longer relevant - me writing it all down prompted a couple paths of investigation and I narrowed down my 'scene turning on device it doesn't know about' problem to actually be  due to some old forgotten associations on the triggering device.

 

I still have a few questions about this problem and associations in general as it still doesn't quite make sense to me.

 

 

 

Fibaro Dimmer 2 capabilities:

• A Fibaro dimmer 2 can take act on associated devices when the either S1 or S2 is either switched or dimmed. 
• A Fibaro dimmer 2 can also send a sceneActivation command to listening scenes if that property is enabled. There 25 distinct sceneActivation IDs based on a combination of three factors: S1 or S2, the three types of switch hardware, and actions such as single, double, triple click, hold, and release.

 

So both are responding to the same real world action (touching a button connected to the dimmer), but it reads to me that they are responding to different system outcomes of that real world action - associations are looking for on/off/dim 'responses' to that real world action, but the scenes are looking for how the real world button is actually pressed. That might be splitting hairs because some of the real world actions that sceneactivation is looking for are the way to achieve the system responses that associations are looking for - like a single click being a switch on/of....but that doesn't apply to all of the scene activation types - that makes it hard to reasonably know how the two will intersect....that's certainly what has confused me.

 

So....should an association run when any scene activation is enabled and running, ...ie is it up to the user to avoid setting up both methods for touching other devices and getting confused like I have...or should the scene activation property being enabled stop the S2 switch being read as 'switch' or dim'? After all, we are now actually thinking about single, double and triple presses....not turning something on or off - that happens in a scene now (my thought process). 

 

If it is expected behaviour that enabling scene activation will not block any existing association behaviour - and I suppose this probably shouldn't be a huge surprise when associations run without the home centre's direct involvement - then how does an association, listening for either on/off or dimming, respond to something like a double or triple click? Those physical actions in particular are not relevant to switching or dimming - at best a double click might switch a device twice in quick succession....or go to full brightness via yet another separate property and function of the dimmer....but I still can't see how those associations could do anything predictable off a triple click.

 

I'm predicting that I will be told it is expected behaviour and that if I set up something (and worse lose track of that over time) that uses multiple, separate pieces of functionality to do things, I really shouldn't expect all those things to still be done to turn them off....I get that logic, but I am struggling to buy into it. To my brain the use of sceneActivation and association are two different ways a device (usually a devices spare S2) could be used....but it just doesn't make sense to let both those ways be configured and active at once!

 

Finally, I just wanted to understand what the numbers on the HC2 associations pages are - I always thought they were IDs, but looking closely now, those numbers are always super low double digits ,even for devices I've added in the high x00's, and those low numbers don't exist (anymore) as devices on my system. This is really confusing because IDs would be the logical thing to show here....I was so stumped by this problem and I had so many angles to check that I didn't initially scroll down to check the tickboxes - I just looked at the numbers on association lists for the devices that seemed to be part of the phantom switching I was tracing.....and it wasn't he ID I was looking for! 

Please login or register to see this attachment.

 

 

 

 

 

 

Suspect mods will want to move this somewhere else as its only partially about scenes now. 

Edited November 5, 2024 by MrNoTip
more observations, edited for readability

[MrNoTip 2]

Narrowed cause. Relevanr no longer relevant

Edited November 5, 2024 by MrNoTip