Thanks for this. The correction has resolved the pricing mismatch via account display and vera variables
Currrently though the new “pricing” variable is displaying the same value, unsure if it has to run a cycle to be correct. Now i see:
Pricing Price now: 27.24, next=27.24p
As for the code launching, I now am deterred from using scenes. They disappear too easily if a device no longer exists and they sometimes mess things up if a reboot/luup reload happens mid scene.
I have created a trigger for ‘luup reloaded’ in Reactor with an activity of 120 second delay and then run lua and your code pasted in there. Seems to work perfectly.
In the same sensor I then define the expressions which are pulled from the virtual AgileMeter device.
This makes it then super easy to contain the code, when it runs, the data pulled and any actions or clever logic you may want to operate on devices and other expressions.
Really grateful for this integration, thanks!
One ‘customer comment’ might be in the help or description for the place where the virtual device # is inserted.
Its currently: “local AgileMeterId = TRV2[“AgileMeter”] – Insert Device ID of Agile Meter… Could make this autmatic one day”
TRV2[“AgileMeter”] is confusing. Really unsure what the TRV2 part is but I stripped all of that out and replaced with the device ID. More confusing if you (meaning when I) didn’t call the virtual device AgileMeter. I personally would have found something like this more intuitive (but maybe this is just me):
local AgileMeterId = [NewVirtualDeviceID] – Insert Device ID of Agile Meter…
I have one question though, what are the values displayed after the / in:
PeakStart 16:00 /14
P.S your text comment - autmatic