OK, so Vera has approved v1.4 of Virtual Sensor. The procedure would then be something like this:
Install Virtual Sensor 1.4 from the plugin marketplace;
Find your new “Virtual Sensor” device, go in to the control panel, and hit the “Add a XXX Sensor” for the type of sensor you want (generic, temp, humidity, etc.). That function creates a child device, so it causes a Luup reload.
While Luup is reloading, hard-refresh your browser (refresh with cache flush: CTRL-F5 for Chrome/Win, SHIFT-F5 for Firefox/Win, CMD+SHIFT+R for many Mac browsers).
Go back into the “Virtual Sensor” master device control panel.
Disable the device if it’s enabled–when enabled, the free-running function generates values for the master device, but you don’t need this feature, so spare your CPU a few cycles and just turn it off. The “Enable/Disable” affects only the function generator, not the data-copying of the child virtual sensors.
Go to the “Virtual Sensors” tab and choose the device and state variable that should be used as the data source for your virtual sensor.
Hit the Reload Luup button on that tab to make your changes take effect.
You can make as many child devices from the master device as you want, just repeat the above. You can use any device variable on any device as a data source. The child devices use purely the Vera-defined structures, UI and behaviors, together with all of their features and non-features; there are no additional or changed behaviors for these devices.
The rain sensor you are trying to access to display values as individual sensors actually saves rain values for each of the last 60 minutes, 24 hours, 52 weeks, 12 months, and 7 days. The plugin collecting this data updates it if necessary each time the sensor transmits its current rain count. If the new rain count has changed it recalculates all of the displayed values. Since it doesn’t store the calculated values (except for rain in the last 24Hrs) it will be difficult to do what you’d like.
[quote=“rigpapa, post:21, topic:200449”]OK, so Vera has approved v1.4 of Virtual Sensor. The procedure would then be something like this:
Install Virtual Sensor 1.4 from the plugin marketplace;
Find your new “Virtual Sensor” device, go in to the control panel, and hit the “Add a XXX Sensor” for the type of sensor you want (generic, temp, humidity, etc.). That function creates a child device, so it causes a Luup reload.
While Luup is reloading, hard-refresh your browser (refresh with cache flush: CTRL-F5 for Chrome/Win, SHIFT-F5 for Firefox/Win, CMD+SHIFT+R for many Mac browsers).
Go back into the “Virtual Sensor” master device control panel.
Disable the device if it’s enabled–when enabled, the free-running function generates values for the master device, but you don’t need this feature, so spare your CPU a few cycles and just turn it off. The “Enable/Disable” affects only the function generator, not the data-copying of the child virtual sensors.
Go to the “Virtual Sensors” tab and choose the device and state variable that should be used as the data source for your virtual sensor.
Hit the Reload Luup button on that tab to make your changes take effect.
You can make as many child devices from the master device as you want, just repeat the above. You can use any device variable on any device as a data source. The child devices use purely the Vera-defined structures, UI and behaviors, together with all of their features and non-features; there are no additional or changed behaviors for these devices.[/quote]
