Odd Behavior under v5.1.7

[bschollnick2]

Matt and Jay,

I'm noticing some real odd behavior here with a plugin. It appears that for some reason deviceStopComm and deviceStartComm are being called, and I don't see any reason for this.

Removing _Test Reader
Processing Device - _Test Reader

The Processing Device line is the first line in deviceStartComm...
The Removing line is in the StopComm...

Is there any reason that Indigo would be triggering these Removals and Adds? There is plenty of updateStateOnServer calls, but nothing that should be able to remove and add a device...

Okay, further investigation leads me to this function...

def update_device_property ( self, dev, propertyname, new_value = ""):
newProps = dev.pluginProps
newProps[propertyname] = new_value
dev.replacePluginPropsOnServer(newProps)
return None

I am assuming, that the dev.replacePluginPropsOnServer, does this? Effectively calling DeviceStartComm and DeviceStopComm?

Can you confirm this? And is there a way to work around that?

[matt (support)]

You need to override didDeviceCommPropertyChange(). Search on it on the plugin guide wiki for the details.

[bschollnick2]

You need to override didDeviceCommPropertyChange(). Search on it on the plugin guide wiki for the details.

I've never run into this before...( Interesting... )

Thanks for the quick response...

- Ben