What a difference a day makes for those endpoint results!
Interesting that the http ones now work - presumably will be because I allow redirects and presumably redirect to https. Should turn that off for endpoint checking.
Interesting about the jwt endpoint - that is apparently for checking token, and/or giving length of time it remains valid. Currently will leave the web token generation - particularly if lasts a year. But it is possible to do within plugin eventually.
I’ll look at the net consumption lifetime - at a guess will be coming from production.json/production. Where it does seem to exist. May be something else causing issue - I’ll have a look later today.
This is what is returned - would the total consumption be a better option?
(given net is 0 across the board)
- Code: Select all
"consumption": [
{
"type": "eim",
"activeCount": 1,
"measurementType": "total-consumption",
"readingTime": 1678639066,
"wNow": 805.972,
"whLifetime": 16960437.142,
"varhLeadLifetime": 4004248.586,
"varhLagLifetime": 1034968.231,
"vahLifetime": 20389408.396,
"rmsCurrent": 8.516,
"rmsVoltage": 244.379,
"reactPwr": -338.808,
"apprntPwr": 1040.156,
"pwrFactor": 0.78,
"whToday": 11053.142,
"whLastSevenDays": 167664.142,
"vahToday": 13398.396,
"varhLeadToday": 2793.586,
"varhLagToday": 454.231
},
{
"type": "eim",
"activeCount": 1,
"measurementType": "net-consumption",
"readingTime": 1678639066,
"wNow": -239.691,
"whLifetime": 0.0,
"varhLeadLifetime": 4004248.586,
"varhLagLifetime": -6557917.437,
"vahLifetime": 20389408.396,
"rmsCurrent": 0.998,
"rmsVoltage": 244.398,
"reactPwr": 134.528,
"apprntPwr": 244.008,
"pwrFactor": -0.98,
"whToday": 0,
"whLastSevenDays": 0,
"vahToday": 0,
"varhLeadToday": 0,
"varhLagToday": 0
}
],
Cheers
Glenn
Sent from my iPad using Tapatalk