Inovelli notifications

#1

1) Give a description of the problem
When I use the inovelli dimmer the notification goes away and shows the level of the light

2) What is the expected behaviour?
I would like to have the notification show up again 5 min after I change the light status

3) What is happening/not happening?
notification will not appear again until the status of my door (locked/unlocked) or garage door (open/closed) also changes. I made a line to re-run the piston again but when I logged the piston it said since the status hadn’t changed it skipped this. I don’t want this piston in an endless loop, I would however like to no skip the notification one time only after 5 min the light switch is pressed.
**4) Post a Green Snapshot of the piston![image|45x37]

download
download.png1178×888 80.6 KB

5) Attach logs after turning logging level to Full
Skipped execution of physical command [TV Lights (Notification 3)].on([]) because it would make no change to the device.

REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.

#2

I would change your last block slightly:

IF RGB7's switch CHANGES    (I switched to a trigger & removed the 5 min part here)
Then
    With location  (TCP set to Never)
    Wait 5 minutes
    Execute piston Notifications
END IF

(notice the TCP is on the WITH block, not the IF block)

Upon closer inspection, changing that last block to a real trigger will remove your other lightning bolts…

Perhaps the cleanup code at 12:30 should be in a separate piston after all…
(although you may be able to cheat by force subscribing to the @globals)

#3

Thanks for your help, no change in effect. I’m still getting the log error:

“Skipped execution of physical command [TV Lights (Notification 2)].on([]) because it would make no change to the device.”

But the notification is not showing. The way the inovelli switch works the notification goes away when the switch is used. But it seems webcore still thinks the notification is showing.

#4

My apologies, I missed this line in your first post.

This means SmartThings and webCoRE did not become aware of the last change.
(IE: they think it is already on, so why bother sending the command again?)

When I am teaching a friend about this, I may use this silly example:

Why tell the kid to go to her room, if she is already there…
Of course, it’s possible that she may have snuck out without telling me.

or perhaps…

Why tell the (TvLights) to (TurnOn), when (TvLights) is already (On)…
Of course, it’s possible that (TvLights) may have (TurnedOff) without telling (the ST hub)

I know… Silly example, but some seem to like my analogies, and it does help to illustrate a bit what is going on behind the scenes.

You can force a particular piston to send a command regardless of outside circumstances by disabling “Command optimizations” in that piston’s settings.

Just be aware that changes here will impact all commands that this piston sends out.