VEC Virtual Switch Auto Off

[cw-kid]

Hi

We have a newish dev on the Vera forum making a few new plugins, which is good to see as we have hardly any 3rd party devs left any more.

He's created a nice little plugin here, that pulls down your current WAN IP in to a plugin device in the Vera UI7 gui.

I was under the impression that Vera plugin device support had to be explicitly added by the MSR dev ?

However it seems that this particular plugin has just bounced in to my Vera Edge Entities list after a Reboot of MSR and is showing this output, so appears to be just working.

x_vera_device.configured=false
x_vera_device.device_number=162
x_vera_device.device_type="urn:nodecentral-net:device:ExternalIP:1"
x_vera_device.failed=null
x_vera_device.mapped_by="*"
x_vera_device.mapped_class="generic_device"
x_vera_device.parent_device=0
x_vera_device.room_id="0"
x_vera_svc_micasaverde_com_HaDevice1.Configured="0"
x_vera_svc_nodecentral_net_ExternalIP1.Current External IP="xx.xx.xx.xx"
x_vera_svc_nodecentral_net_ExternalIP1.Icon="0"
x_vera_svc_nodecentral_net_ExternalIP1.Last Changed="1641612887"
x_vera_svc_nodecentral_net_ExternalIP1.Last Changed HR="1641612887"
x_vera_svc_nodecentral_net_ExternalIP1.Last Checked="1641612887"
x_vera_svc_nodecentral_net_ExternalIP1.Last Checked HR="1641612887"
x_vera_svc_nodecentral_net_ExternalIP1.PluginStatus="Plugin variables being set up 2/2"
x_vera_svc_nodecentral_net_ExternalIP1.PluginVersion="0.2"
x_vera_svc_nodecentral_net_ExternalIP1.Previous External IP="0.0.0.0"
Capabilities: x_vera_device, x_vera_svc_micasaverde_com_HaDevice1, x_vera_svc_nodecentral_net_ExternalIP1
Actions: x_vera_device.set_variable, x_vera_svc_micasaverde_com_HaDevice1.AllowPairing, x_vera_svc_micasaverde_com_HaDevice1.Poll, x_vera_svc_micasaverde_com_HaDevice1.Reconfigure, x_vera_svc_micasaverde_com_HaDevice1.Remove, x_vera_svc_micasaverde_com_HaDevice1.SetPollFrequency, x_vera_svc_micasaverde_com_HaDevice1.StressTest, x_vera_svc_micasaverde_com_HaDevice1.ToggleState, x_vera_svc_nodecentral_net_ExternalIP1.refreshExternalIP

Thanks

[parkerc]

@cw-kid said in Vera plugin devices just appear in MSR?:

Hi

We have a newish dev on the Vera forum

That makes me feel young

[gwp1]

@cw-kid It's been my experience that anything I add on Vera would follow the integration path at the next reboot of MSR ( I could be mistaken, my Vera was taken completely offline a couple months ago ).

[therealdb]

every variable on you Vera is available in MSR. I have custom one I'm using to save intermediate status, and it's working very well since day 1. they're pushed to MQTT as well.

[toggledbits]

@gwp1 said in Vera plugin devices just appear in MSR?:

It's been my experience that anything I add on Vera would follow the integration path at the next reboot of MSR

This is correct. All plugins in Luup are represented by at least one device. Any such device will make an appearance when Reactor next restarts (currently).

What may or may not require further integration depends entirely on the nature of the plugin and the device it creates. Plugins like AutoVirtualThermostat and Switchboard use standard devices, so they are known types that are already mapping into Reactor's standard capabilities and typically don't require any additional work to be basically functional.

Plugins that implement only new services and behaviors not known to standard Luup devices may require some additional work, usually done only in data files, to describe those capabilities of the plugin and map them into standard Reactor capabilities. Reactor recognizes, for example, the Harmony plugin, and can provide special capabilities, attributes, and actions for that plugin's master device when present.

VeraController also knows how to publish all of the state variables on a device as extended attributes, and it can ask Luup what a device's available actions are and provide extended actions, without any additional intelligence in either code or data from Reactor. So even without standard device use, and without special data mapping, pretty much any plugin or device will have its states and actions accessible in Reactor.

So, no, it is not the case that every plugin has to be specifically integrated.

[cw-kid]

OK thanks guys for the information appreciate it.