Device State in Device Panel Incorrect


#1

Hi, not sure if this is a Smartthings Issue or Webcore, but as I discovered it in Webcore I decided to raise it here.

I’ve noticed that occasionally my Hue Lights are being incorrectly shown as ‘on’ in the device panel when editing a piston, when they are actually ‘off’.
Turning them on and off via Smartthings app seems to have no effect in the switch state of the lights in the Webcore device panel.
I eventually wrote a quick piston to turn all the lights off, which when executed, displayed the switches in their correct ‘off’ state.

To add further detail, the lights can be controlled by the following devices : Hue Switch, Google Home Integration (with Hue), Smartthings


#2

The dashboard and the devices list to the right when editing pistons were an early version of what will eventually be ‘Visors’… it relies on web sockets (which take a lot of server power) and as far as I’m aware it’s currently disabled pending future updates. (It’s not been working for a while).

It’s still active in the minion developer environment but doesn’t have much function, so you’re not missing anything.

The pistons themselves know the state of the devices.


#3

Hi, thanks for getting back so quickly.

So the activity that I am seeing is not truly indicative of the state of the device environment? (because the device panel is possibly not static, and does not appear to be disabled).

Just trying to get some clarity here, because I do appear to have an issue with a very simple piston behaving erratically and not turning lights on when they should (based on movement/lux level/current switch state of the lights).

Having seen that light being ‘on’ in the device panel, but physically being ‘off’ would have possible pointed to a reason why it was not executing. Hohum…:confused:

(edited to add question mark)


#4

Maybe build a simple test piston…

IF
Problem light is on
then
Send push notification “on”
else
Send push notification “off”

If that doesent work we’ll go from there.

If it does work, it’s the piston, so post a green snapshot and I’ll see if anything obvious is going on.