ISY responds to /rest/status command with old status

[spiderbot]

I have a 994i connected to about 15 devices in my home.  I use MobiLink for my remote control.  I can control everything.

 

Here's the problem.

 

* Start with all devices in off state.

* I turn on a device remotely using the app.

* I turn off the device manually.

* I go  to the app and it shows the light is still on.

* If I 'cycle' the device off, everything works from there until the next manual action again goes out of sync.

 

I have written a small app that saves off the results of a rest/status command over http.  As above, it shows the device is on when it isn't.  This is definitely an issue with the ISY.

 

Any suggestions?

 

Thanks

[kgividen]

I have a 994i connected to about 15 devices in my home.  I use MobiLink for my remote control.  I can control everything.

 

Here's the problem.

 

* Start with all devices in off state.

* I turn on a device remotely using the app.

* I turn off the device manually.

* I go  to the app and it shows the light is still on.

* If I 'cycle' the device off, everything works from there until the next manual action again goes out of sync.

 

I have written a small app that saves off the results of a rest/status command over http.  As above, it shows the device is on when it isn't.  This is definitely an issue with the ISY.

 

Any suggestions?

 

Thanks

I have seen something similar to this.  In my case it was because I send a command to turn off or on and then I immediately queried and the ISY didn't have the correct status.  I delayed a couple of seconds and then it would see the correct status.  I'm also not sure if it doesn't have something to do with the ramp rate.  I haven't looked into it past putting a small artificial delay there.

[spiderbot]

Thanks for your response.

 

I get the wrong data even if the *only* thing I do is query with https://.../rest/status.

 

I *really* don't want to have to reprogram everything.  I have a ton of home automation programs on the ISY.

[mwester]

Let's step back just a bit.

 

Repeat your test sequence - this time watch the device status in the ISY Admin console.  Does the console status update when you manually turn off the device?  If not, then you have a communication problem if the device is Insteon, or a zwave device with "instant status".