clivee
clivee
About
- Username
- clivee
- Joined
- Visits
- 489
- Last Active
- Roles
- Member, Administrator, Moderator
Comments
-
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
-
This is a self help forum If you have an issue please raise a ticket at support@glowmarkt.com
-
Nope- nothing has changed here.
-
Hahahahahahahahah I have NEVER done anything like that - no siree ;-)
-
no I think that's just you - certainly working for me
-
'If so what does this mean to the end users? e.g. removal or delay on things like "instant power"?' There may be another second or so before you get the data
-
Sorry to say we have had another attack - I have disabled mqtt so I can get some sleep - I will revisit in the am.
-
Your IHD is losing connection with your meter due to range - signal strength is very low. Please move your IHD closer to the electricity meter and try again I have just rebooted it and it has rejoined but It will lose connectivity again.
-
Well we have no control over what readings are available from the meter. Something clearly changed during the update - finding anyone at Octopus who would both know what and how to fix it may be a challenge. In other news E&A into the DCC is not…
-
Secure S1 meters have to be explicitly told to record export. It looks like when the tariff was updated, that flag was removed. Are your export readings showing in the Octopus portal?
-
As for knowing which topic - no sadly there is no programmatic way of knowing . However just ask - we will tell you and it won't change. It is an historical accident which can't change without affecting other users.