Jump to content

Progam not updating device status in ISY after execution


jumz

Recommended Posts

Hi Guys,

 

I have written a program whereby once a motion sensor is triggered it turns a scene on that turns on all the lights in the house. The program executes correctly but the device statuses are not updated in the ISY Admin Console. When I query the scene it updates.

 

Is this expected behavior?

 

Link to comment

A couple things you can check...

 

In admin console

  • Help > About Firmware and UI version.
  • Right click on device Diagnostics > Show Device Links Table < then Compare

Firmware and UI should always be the same.

Your Device Links Table should be the same as ISY Links Table for all devices in Scene.

 

Is it possible you manually linked devices either before or after adding to scene?

 

 

Jon...

Link to comment

I have confirmed the firmware and UI versions are correct (4.3.26)

 

No I have not linked them outside the ISY.

 

I will look into the device link tables and compare what the ISY thinks it should be and what it actually is. What is strange is this behavior is only observed when executing the scene from the program. Execution of the scene via Smart Phone, Admin Console, etc all respond and report status information correctly.

Link to comment

" What is strange is this behavior is only observed when executing the scene from the program. Execution of the scene via Smart Phone, Admin Console, etc all respond and report status information correctly."

 

The same Insteon command is issued whether invoked from Admin Console or an ISY Program.  That would indicate some other Insteon traffic when run from an ISY Program is causing interference.

 

Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3.  Run the activity before and during ISY Program activity.  Post the event trace.

Link to comment

To follow on Lee's thought, what does the program do?

 

Does it perform any direct device commands right before the scene is called? Direct device commands will have acknowledgements coming back at the same time that scene is called in that case. Since scene commands are not acknowledged, some devices like powerline only might miss the command

 

I would put the direct commands after the scene, if this is the case

 

Paul

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...