clivee
clivee
About
- Username
- clivee
- Joined
- Visits
- 532
- Last Active
- Roles
- Member, Administrator, Moderator
Comments
-
Sorry - this was my bad - can you try now please
-
The app uses the same api - you have something else wrong somewhere.
-
please raise a ticket at support@glowmarkt.com
-
please email support@glowmarkt.com and I will look into it.
-
We can only display on the IHD what the supplier loads on the meter - often they don't. We can get it correct in bright - if you email support@glowmarkt.com and tell then your tariff and the effective date.
-
By default we set the DCC to send data once per 24 hours. Have a look at https://api.glowmarkt.com/api-docs/v0-1/resourcesys/#/Resource/resource_catchUpReadings You only should call that once per 30 minutes at that is the maximum granularity.
-
Sadly they will never match - the minute level data is calculated as the average of the ‘instant use’ readings taken 5/6 times in that minute. They are summed into the 30 minute slot. Overnight the real 30 minute reading comes from the DCC and corre…
-
I see no issues on the system. Please raise a ticket at support@glowmarkt.com if you still have problems.
-
'Here' is nothing to do with glow authentication. Please raise a ticket at support@glowmarkt.com
-
No we have changed nothing - please raise a ticket at support@glowmarkt.com
-
please raise a ticket at support@glowmarkt.com
-
Ok your data is not automatically updated unless you call the specific api call to trigger it - you should call it once per half hour "https://api.glowmarkt.com/api-docs/v0-1/resourcesys/#/Resource/resource_catchUpReadings" I am assuming …
-
We don't differentiate - can you raise a ticket at support@glowmarkt.com - thanks
-
You should be seeing half hour data now
-
@ackyaz - fabulous
-
As things stand we ignore all but the first request every half hour - BUT I would still prefer if those calls were not even made - they are just chewing bandwidth and cpu for exactly zero gain for you and us.
-
Oh yes - from my point of view that would be better - but I know people want their data asap ;-)
-
But I suspect that is not what the users actually NEED at the moment they get new data just after the half hour changes - if you just up the interval to 30 minutes it will, as you say, be on the 30 minute anniversary of startup.
-
Thank you @si458 very much I did look at the plugin and whilst it is trivial to change the interval that is not what you want I think. You need it to send once every 30 minutes, but soon after the actual :00 or :30 There should be a random delay add…
-
Now approved and in the app store.
-
As I said - we are awaiting approval from Apple - it was submitted last night.
-
Thanks - we have what amount to a clue. Will be following it up .
-
Can anyone tell me when this FIRST stopped - and did the api/app stop at the same time?
-
openssl s_client -servername mqtt.energyhive.com -connect mqtt.energyhive.com:8883 2>/dev/null | openssl x509 -noout -dates returns notBefore=Sep 13 07:29:14 2021 GMT notAfter=Dec 12 07:29:13 2021 GMT So that looks fine to me Are YOUR root ca ce…
-
It will be (probably) the change in root cert for letsencrypt 'https://scotthelme.co.uk/lets-encrypt-old-root-expiration/' Make sure your root ca store is up to date.
-
we send what we get - if 0702 00 01 is 0 thats what the CAD is receiving from the meter
-
a change of password will log everything out - but otherwise this should not happen. Please raise a ticket as soon as it happens again with support@glowmarkt.com - if you give enough details we should be able to find it in the logs (which are kept f…
-
Ok a few things Do you have our IHD/CAD or is it dcc data only? Either way please raise a support ticket at support@glowmarkt.com
-
At the moment yes - it is on the roadmap to support throughout the system but it awaits somebody wanting to pay for the development
-
mqtt is working fine it was down for a few hours weeks ago. I would suggest the issue is yours