Python scripts are set to add progress messages to a log file which shows the script pauses at "Seeking Messages" - i.e. getting no response from server.
Hildebrand will be back in the office this morning and might just need to restart a stalled server.
I did miss one record at 10pm BST last night but that's a fairly normal occurrence (couple of times a week) which I suspect is down to one of my computers trying to upload something to my online record whilst another is downloading something. Since that almost always happens at a time when I've not imported anything it's easy to insert a record.
Hi Eric, wondering if you're having any issues with MQTT data at the moment?
Last update I had was 14:48 today.
I've got 3 green lights on my Glowstick and not done any config changes to my system, so I'm a bit loathed to go poking around and changing/rebooting stuff if it's not local to my system.
My fully automated meter reading system using Python started up at 8am (as noted above) but stopped again after the 9:30 reading.
I've just tried to start the first script in the sequence and received "error connecting : 5" but not sure what it means.
Have just rebooted the PC on which it runs which will have restarted task scheduler.
But Python suite still doing nothing and trying first script again still gives "error connecting : 5"
A quick Google suggests that means : "You simply do not have access to the folder you are writing in for the process that is currently running (python)." Which is bizarre as it's a process that has run without any issues (of its own) for a couple of years.
Will log out and back in with admin privileges.
Have done that but even the admin account is getting "error connecting : 5" !
Comments
I got a meter reading for 7pm BST on 10th. Nothing since. (next should have been 7:30pm)
My MQTT feed into Home Assistant has just started working again. 09:23 BST.
I didn't change or do anything, it just came back on its own!
Thanks Dave,
My 'task' kept running and seemed to burst back into life for the 09:30 reading and has since done a 10:00 one
Jane was looking into it for me yesterday; suspect she or a colleague have found the problem & fixed it this morning
I've accidentally posted message below in an older version of a similar page
My Python suite hasn’t produced any half-hourly readings since 16:30 BST today (Wed 7/8/24)
I’ve tried running just the collection script but that just freezes after launch. (but isn't showing an error message)
IHD seems to be working OK
Have reported to 'Support'
Hi Eric,
Yes, just checked mine and looks like the last MQTT data I got was approx. 17:17 yesterday (07/08/24).
Still not working this morning.
Python scripts are set to add progress messages to a log file which shows the script pauses at "Seeking Messages" - i.e. getting no response from server.
Hildebrand will be back in the office this morning and might just need to restart a stalled server.
It should be working I was up at 02:45 with the alerting
Thanks Clive but script still reporting that it's "Seeking Messages" (last checked at 9:33)
Can you check now please
No change I'm afraid
extract from log :-
07 Aug 16:59:58 : Seeking message
07 Aug 17:00:18 : Received message
FT: 2024-08-07 17:00:18.636299 ST:2024-08-07 16:59:58.862021T2G : 0:00:19.774278
07 Aug 17:00:18 : ExtractFromJson.py launched
07 Aug 17:00:18 : Calling webpage PostMdata.php
07 Aug 17:00:18 : rOPline https://khormaksarschool.org.uk/Electricity/Octopus/PostMdata.php?UTC=1723046420&Mread=24310.500&Source=Tiny&TV=BST
07 Aug 17:29:58 : Seeking message
07 Aug 17:59:58 : Seeking message
07 Aug 21:00:58 : Seeking message
07 Aug 21:27:49 : Seeking message
07 Aug 21:28:26 : Seeking message
08 Aug 09:09:43 : Seeking message
08 Aug 09:33:02 : Seeking message
08 Aug 10:41:48 : Seeking message
Results down to 07 Aug 17:00:18 have been generated from fully automated system
Later ones from running the collection script manually.
The Python suite resumed with the result for 15:30 BST and I've had all the half-hourly readings since then
Yes my MQTT values started updating in Home Assistant at 15:27 :)
Thank you @clivee
Still working this morning.
I did miss one record at 10pm BST last night but that's a fairly normal occurrence (couple of times a week) which I suspect is down to one of my computers trying to upload something to my online record whilst another is downloading something. Since that almost always happens at a time when I've not imported anything it's easy to insert a record.
Just noticed my MQTT Cloud data seems to have stopped reporting since ~15:09 on 13/09/24.
Have rebooted Glowstick and have 3 green lights. Before I go poking around in my setup I'm wondering if anyone else is seeing issues?
Sorry all - ssl cert expired and I was AFK.
Brilliant!
Thank you clivee for such a super quick response, very much appreciated. :)
Is there a server problem this morning ?
I've had no meter readings downloaded via mqtt since 4am today (Fri 6/12).
Python reports : "ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it"
Bright app is working OK
Looks like mosquitto died - (not seen that before)
Now restarted.
Thanks Clivee,
First part of my Python script now working OK although I'm getting something strange when next part tries to decode the json file.
Probably a local problem which I'll check out later (not urgent as my meter readings should stay pretty constant till 23:30)
My Python suite hasn’t produced any half-hourly readings since 16:00 today
Reports error "No connection made because target machine refuses it"
Yes, just spotted my MQTT feed stopped updating @ 16:20 14th Feb, but came back @ 09:55 this morning. 😊
Mine's back too. I check it every half hour for meter readings and 10am plus subsequent ones were OK
@KS_Eric
Hi Eric, wondering if you're having any issues with MQTT data at the moment?
Last update I had was 14:48 today.
I've got 3 green lights on my Glowstick and not done any config changes to my system, so I'm a bit loathed to go poking around and changing/rebooting stuff if it's not local to my system.
I can only apologise - entirely my fault - I broke the auth process doing some infrastructure upgrades.
Should all be working now.
Thanks Clivee, yes all back ~ 08:13 today.👍️
I spoke to soon!
MQTT data refresh seems to have stopped again around 09:42
I'm still getting live readings on the Bright app, so Glowstick/local network etc.. all OK.
I hadn't been checking my meter records for last couple of days but now that I have, I can see a gap between 2025-03-19 14:30 & 2025-03-21 08:00.
Also 09:30 this morning onwards are missing - hopefully situation will recover soon ?
I shall fill in my gaps by downloading data from Octopus or if todays gap is short from Bright record.
No issues on our side that I can see - data flowing as normal
My fully automated meter reading system using Python started up at 8am (as noted above) but stopped again after the 9:30 reading.
I've just tried to start the first script in the sequence and received "error connecting : 5" but not sure what it means.
Have just rebooted the PC on which it runs which will have restarted task scheduler.
But Python suite still doing nothing and trying first script again still gives "error connecting : 5"
A quick Google suggests that means : "You simply do not have access to the folder you are writing in for the process that is currently running (python)." Which is bizarre as it's a process that has run without any issues (of its own) for a couple of years.
Will log out and back in with admin privileges.
Have done that but even the admin account is getting "error connecting : 5" !
Any suggestions ?
Now tried running same script on a different PC (and still with admin privileges)
Result still the same. Trying to connect to MQTT server still gives "error connecting : 5" !