It works the other way around an OSA Event does not cause a State change. Rather an OSA State Change should cause an Event to occur with the same State name.volfan6415 wrote:Ok so the state changing seems to be related to the method call not logging the event. When i changed ownership of the x10 object type to the cm15a plugin the corresponding events were logged and the state changed.
Is there something in the insteon code that would be blocking the logging of the corresponding events?
I have not looked at the Insteon plugin but usually the X10/Insteon Controller sends back a response that indicates the command was successfully executed by the remote device. When the plugin sees this response, it should execute an object state change with something like this:
OSAEObjectStateManager.ObjectStateSet("Object", "State", pluginName)