Seeting HS device value (SetIOMulti)

[alexbk66]

Setting HS device value (SetIOMulti)

In HS3 if you control HS device from HS (i.e from deviceutility page) i HS notifies the plugin which owns the device, but doesn't update the device value in HS. It's plugins responcibility to handle the request and update the HS device value when plugin is happy. Which makes sense.

But in HS4 I control the HS device - and the device value changes immidiately.

What's changed here?

[spud]

But in HS4 I control the HS device - and the device value changes immidiately.

I don't think that's true. For me it works just like in HS3.
Only virtual devices (=devices not own by any plugin) behave like this

[alexbk66]

I don't think that's true. For me it works just like in HS3.
Only virtual devices (=devices not own by any plugin) behave like this

Then I must be doing something wrong...

What's the definition of "Virtual" device then? If "Interface" property is empty?

[alexbk66]

I don't think that's true. For me it works just like in HS3.
Only virtual devices (=devices not own by any plugin) behave like this

If you create a sample switch device in your HomeSeerSamplePlugin - it behaves as I described. And I can't see any source code handling SetIOMulti.

I may be wrong spud

[spud]

If you create a sample switch device in your HomeSeerSamplePlugin - it behaves as I described. And I can't see any source code handling SetIOMulti.

I may be wrong spud

This is because the default behavior in AbstractPlugin.SetIOMulti is to set the device value. So, if the plugin does not override SetIOMulti, then yes it behaves as you describe.

 /// <inheritdoc cref="IPlugin.SetIOMulti" />
/// <remarks>
/// The default behavior is to clear the current status text and set the value on the target feature and then
/// let HomeSeer assign the status text based on the configured <see cref="StatusControl"/>s
/// and <see cref="StatusGraphic"/>s
/// </remarks>
public virtual void SetIOMulti(List<ControlEvent> colSend) {
foreach (var controlEvent in colSend) {
HomeSeerSystem.UpdateFeatureValueByRef(controlEvent.TargetRe f, controlEvent.ControlValue);
}
}

[alexbk66]

Thank you, that's what I suspected