New firmware (V1.12.0) Scene Triggers

MarkHenry · ‎2022-10-26

Was testing a project with the latest firmware.

Seems IndicatorKill is doing something inconsistent.

When groups are ramped to a level the IndicatorKill is sent straight after the scene has been initiated.

When groups are not ramped to a level the scene IndicatorKill is not triggered.

DarrenMullighan · ‎2022-10-26

Hi Mark,

I am trying to replicate this for you now, but it seems whenever I either ramp or directly control a group away from the scene level, my indicator works as expected? Do you have an exact step by step for replicating this?

MarkHenry · ‎2022-10-26

Hi Darren,

I created 4 scenes with different levels in the NAC.

100% (as 3)

75% (as 2)

25% (as 1)

0% (as 0)

Set only the 100% scene to instant on (no ramp)

Others have 4s and 8s ramp

Set scene 100% indicatorKill does not get sent after scene set (trigger stays at action selector 3)

Set any of the other scenes and IndicatorKill is sent straight after scene is set.

There is no other commands sent that changes any of the groups in the scenes after they are set.

My understanding is the trigger group will keep last action selector until the one of the groups doesn't match scene.

Hopefully this makes sense.

DarrenMullighan · ‎2022-10-26

Hi Mark,

Thanks for the clarification, I can confirm that I am able to replicate this. I will escalate as appropriate

DarrenMullighan · ‎2022-10-26

I just factory reset my NAC in an effort to create a demo project for this and have noticed that the issue no longer happens for me.

Was this NAC in question a project that had been updated from 1.11 to 1.12 or has a project only ever been created on it since the 1.12 firmware was installed onto it?

MarkHenry · ‎2022-10-26

Existing site, updated from .11 to .12

MarkHenry · ‎2022-10-26

So we have to do a full factory reset after any update ??

DarrenMullighan · ‎2022-10-26

After another hour of testing, I was able to semi recreate the fault on 1.11 as well, but after updating it to 1.12, the issue appears to have disappeared again.

I have noticed on my original test set up though that I took a backup of the current project, factory reset the NAC2 and then restored the project, only to find that the issue was no longer present.

For the mean time, this might be a suitable fix for the situation?

MarkHenry · ‎2022-10-26

This will work for now.

Will give it a test and see what happens.

MarkHenry · ‎2022-10-27

Ok so after factory reset and then restore the project confirm it works.

Lets say for some reason you create a new scene, then back to square one.....IndicatorKill is issued straight after scene. 😡

DarrenMullighan · ‎2022-10-30

I was able to replicate exactly that. I am still looking into this, and will report as appropriate

Cheers again.

nireshenb · ‎2022-11-14

To add to this post, running into the same IndicatorK1ll message being sent on SHAC running the v1.12.0 firmware.

Similar to the OP, scenes with different levels. Noticed that when scene has loads with ramp level, I get the IndicatorK1ll message - no ramp no IndicatorK1ll message sent.