Note the IHD (Glow Display) is online and sends actual data to my broker no problem, it’s just the glowmqtt.energyhive.com that I’m unable to even connect to. Previous outages the connection itself usually worked, just the MQTT messages were not flowing.
It seems that clivee's comment from around 10am yesterday may have been a tad optimistic ?
I've just switched my PC that operates Python scripts back to its normal account (which is now an admin-enabled account). It's restarted the task scheduler OK but the logfile shows that it's still having problems in accessing server . A bit of digging around in script shows it wants to connect to "glowmqtt.energyhive.com" Just as reported by Phantomski
Sorry Clive, it could take me a very long time to find out ! But I'll email a copy of the relevant .py script to your support address. The connection details will be in there - somewhere.
I am having the same "error connecting : 5" problem, starting around 9:45 this morning. Was working OK until then. Restarting the connection my side fails with the same "error connecting : 5" problem. Thanks, David.
Could the script work for Clive because the device he is using is recognised as 'authorised' whereas DaveS & I are using devices that the glowmqtt server hasn't authorised ?
Using mqtts endpoint, various clients (Mosquitto, emqx, mqttx, MQTT Analyzer), internet ISPs and client IPs, protocol v5 and v3.1.1, but nothing can connect because "not authorized".
Both Bright app and Bright Display IHD stay connected and hum along no problem. Last MQTT message received and first Connection Refused: not authorised from mqtt.energyhive.com on 21/03/2025T17:12:48
Last time I've seen this in the logs was 13/06/2024T11:30:16
Is it possible there's a limit on simultaneous connections? Or something else limiting clients access?
Similar issue here: as of approx. 0945 today (23 March 2025) getting no response via Home Assistant Hildebrand Glow to MQTT add-on and on closer inspection this evening getting Connection refused: Not authorized when trying to connect to mqtt://glowmqtt.energyhive.com:1883 using Glowmarkt credentials. Bright app working fine.
Just checked and my original email from Jane just said to use Bright credentials, so my command line example a few posts back was wrong (using mqtt.energyhive.com).
I just reran it using glowmqtt.energyhive.com and got the same result;
I too had been successfully using the same Python script up to & including 2025-03-19 14:30 . It restarted 2025-03-21 08:00 but only lasted until 2025-03-21 09:30 and has never worked since.
I've had no email from Jane or anyone else at glowmarkt advising me to edit the connection method.
Mine alas didn't start at 12:29 but a reboot of the PC that I use to run Python just after 13:30 (when I thought I'd have missed the 13:30 reading has in fact produced a late report at 13:34 (which is normal behaviour for that script : "If at first you don't succeed . . . .") and a 14:00 result at 13:59:50 (again quite normal) . I'm reasonably confident that it will carry on now (mind you that's what I thought on Friday !)
Thanks Jane, Clive or whoever. Just for interest, what had happened ?
Have just downloaded Octopus data for 19-23 March and now need to wait until about this time tomorrow to get the MN-13:00 set.
Since installing home batteries, I tend not to use my locally stored results on a daily basis but still use them to cross check monthly bills. I find it a bit strange that although they broadly agree there's nearly always a few pence discrepancy (usually in my favour).
Sorry for all this mess - I am trying to update some infrastructure and also support peoplewho have more that one device - lets just say it was not 100% successful at a first attempt.
loosk like its fixed except for those people with multiple macs - I am still trying to find a solution for that.
when I’ve bought Glow Display IHD years ago, the only credentials I’ve been given were for glowmqtt.energyhive.com and they’re the same as the Bright iOS app.
I am basically connecting the IHD itself and 2 local brokers (for HA and redundancy) to it at the same time, with occasional client to test if problems occur. So call it 3-4 simultaneous connections via MQTTS TLS on port 8883, SMART/HILD/xxxx topic, but they’re almost always all from the same source IP.
If that’s a problem for some reason in your infrastructure, I am reasonably happy to reduce that to just 2 (IHD and local broker as a bridge), or potentially just one, using the Glow Display’s Glow Internal MQTT topic. In fact I was half way migrating there, but the issue just occurred almost exactly at the same time.
Not trying to give you extra work on a stressful enough day, but if you have a moment, would you mind doing a brief post mortem? Just so we know what to do/avoid in the future and additionally for us clients, what to do to make it easier for you in terms of using the endpoint and reporting issues.
Comments
Same issue here. Any client (and internet connection) I try to connect to the broker comes back with “not authorised “ (the credentials are correct).
The Bright app still shows everything ok and data flowing, but I’m afraid to log out of it to try if it logs back in.
Note the IHD (Glow Display) is online and sends actual data to my broker no problem, it’s just the glowmqtt.energyhive.com that I’m unable to even connect to. Previous outages the connection itself usually worked, just the MQTT messages were not flowing.
Thanks Phantomski
It seems that clivee's comment from around 10am yesterday may have been a tad optimistic ?
I've just switched my PC that operates Python scripts back to its normal account (which is now an admin-enabled account). It's restarted the task scheduler OK but the logfile shows that it's still having problems in accessing server . A bit of digging around in script shows it wants to connect to "glowmqtt.energyhive.com" Just as reported by Phantomski
Yes I'm still getting connection refused;
Which endpoint are you trying to connect to ? and mqtt or mqtts?
Sorry Clive, it could take me a very long time to find out ! But I'll email a copy of the relevant .py script to your support address. The connection details will be in there - somewhere.
Hi clivee, I'm using secure MQTT on port 8883.
This the data I am trying to access;
-----------------------------------------------------
"Elec Import Meter MQTT"
state_topic: "SMART/HILD/************D"
value_json['elecMtr']['0702']['00']['00']|int(base=16)
value_json['elecMtr']['0702']['03']['01']|int(base=16)
value_json['elecMtr']['0702']['03']['02']|int(base=16)
"Elec Export Meter MQTT"
state_topic: "SMART/HILD/************D"
value_json['elecMtr']['0702']['00']['01']|int(base=16)
"Instant Electricity MQTT"
state_topic: "SMART/HILD/************D"
value_json['elecMtr']['0702']['04']['00']|int(base=16)
"Gas Import Meter3 MQTT"
state_topic: "SMART/HILD/************D"
value_json['gasMtr']['0702']['00']['00']|int(base=16)
value_json['gasMtr']['0702']['03']['01']|int(base=16)
value_json['gasMtr']['0702']['03']['02']|int(base=16)
-------------------------------------------------------------------------
And this is my MQTT broker bridge configuration;
-------------------------------------------------------------
connection glowmqtt
address glowmqtt.energyhive.com:8883
remote_username ********@********.com
remote_password ***********
bridge_capath /etc/ssl/certs/
topic SMART/HILD/***********D in 0
try_private false
notifications true
start_type automatic
remote_clientid glow
keepalive_interval 300
cleansession true
bridge_protocol_version mqttv311
local_clientid homeassistant
---------------------------------------------------------------------------
works for me (btw you can user 443 or 8883 - same endpoint)
mosquitto_sub --cafile /etc/ssl/cert.pem -L 'mqtts://*user*:*maypass*@mqtt.energyhive.com/SMART/HILD/*mymac*'
{"SOURCE":"internet","elecMtr":{"0702":{"00":{}}},"gasMtr":{"0702":{"00":{}}},"gid":"MYEUII*","gmtime":1742745102,"hversion":"GLOW-IHD-01-1v4-SMETS2","pan":{"euis":[],"join":"0","lqi":"58","nPAN":"00","rssi":"B2","status":"rejoining"},"smetsVer":"SMETS2","time":"0067E02E0E","ts":"2025-03-23 15:51:42","upTime":"0007F5E1","zbSoftVer":"1.2.5"}
I am having the same "error connecting : 5" problem, starting around 9:45 this morning. Was working OK until then. Restarting the connection my side fails with the same "error connecting : 5" problem. Thanks, David.
Still getting connection refused..?
➜ / mosquitto_sub --cafile /etc/ssl/certs/cert.pem -u "myuser@gdomain.com" -P "mypass" -p "8883" -h "mqtt.energyhive.com" -t "/SMART/HILD/MyGlowMac" -d -v -V "mqttv311"
Client null sending CONNECT
Client null received CONNACK (5)
Connection error: Connection Refused: not authorised.
Client null sending DISCONNECT
Could the script work for Clive because the device he is using is recognised as 'authorised' whereas DaveS & I are using devices that the glowmqtt server hasn't authorised ?
And if so, how can we get authorised ?
Still no joy @clivee
Using mqtts endpoint, various clients (Mosquitto, emqx, mqttx, MQTT Analyzer), internet ISPs and client IPs, protocol v5 and v3.1.1, but nothing can connect because "not authorized".
Both Bright app and Bright Display IHD stay connected and hum along no problem. Last MQTT message received and first
Connection Refused: not authorisedfrom mqtt.energyhive.com on 21/03/2025T17:12:48Last time I've seen this in the logs was 13/06/2024T11:30:16
Is it possible there's a limit on simultaneous connections? Or something else limiting clients access?
Similar issue here: as of approx. 0945 today (23 March 2025) getting no response via Home Assistant Hildebrand Glow to MQTT add-on and on closer inspection this evening getting Connection refused: Not authorized when trying to connect to mqtt://glowmqtt.energyhive.com:1883 using Glowmarkt credentials. Bright app working fine.
Same issue with Cloud MQTT link here. It's also been out since 9.45am yesterday morning (23rd).
Ok can we be clear here there are two cloud mqtt (don't even ask)
1) the original where you were given a user and pass to use - mqtt.enegyhive.com
2) A later one where you use your bright/glow credentials glowmqtt.energyhive.com
where is the issue that you are seeing?
Oh, I didn't realise there were 2 clouds MQTTs !!
Just checked and my original email from Jane just said to use Bright credentials, so my command line example a few posts back was wrong (using mqtt.energyhive.com).
I just reran it using glowmqtt.energyhive.com and got the same result;
➜ / mosquitto_sub --cafile /etc/ssl/cert.pem -u "BrightuserID" -P "BrightPass" -p "8883" -h "glowmqtt.energyhive.com" -t "/SMART/HILD/Glowmac" -d -v -V "mqttv311"
Client null sending CONNECT
Client null received CONNACK (5)
Connection error: Connection Refused: not authorised.
Client null sending DISCONNECT
I had been succesfully using the Bright/glowmqtt one up until March 19th/21st.
I too had been successfully using the same Python script up to & including 2025-03-19 14:30 . It restarted 2025-03-21 08:00 but only lasted until 2025-03-21 09:30 and has never worked since.
I've had no email from Jane or anyone else at glowmarkt advising me to edit the connection method.
It is the glowmqtt.energyhive.com version I am using (via NodeRed which is preformatting the information before passing to Home Assistant).
It's all now resolved itself now though for me... thanks!
Ditto, mine looks like it restarted just now at ~ 12:29.
Thanks
Mine alas didn't start at 12:29 but a reboot of the PC that I use to run Python just after 13:30 (when I thought I'd have missed the 13:30 reading has in fact produced a late report at 13:34 (which is normal behaviour for that script : "If at first you don't succeed . . . .") and a 14:00 result at 13:59:50 (again quite normal) . I'm reasonably confident that it will carry on now (mind you that's what I thought on Friday !)
Thanks Jane, Clive or whoever. Just for interest, what had happened ?
Have just downloaded Octopus data for 19-23 March and now need to wait until about this time tomorrow to get the MN-13:00 set.
Since installing home batteries, I tend not to use my locally stored results on a daily basis but still use them to cross check monthly bills. I find it a bit strange that although they broadly agree there's nearly always a few pence discrepancy (usually in my favour).
Sorry for all this mess - I am trying to update some infrastructure and also support peoplewho have more that one device - lets just say it was not 100% successful at a first attempt.
loosk like its fixed except for those people with multiple macs - I am still trying to find a solution for that.
Hi @clivee. Unfortunately it's now down again for me since approx 1pm... Not sure if it's the same for others...
Hi @clivee
when I’ve bought Glow Display IHD years ago, the only credentials I’ve been given were for glowmqtt.energyhive.com and they’re the same as the Bright iOS app.
I am basically connecting the IHD itself and 2 local brokers (for HA and redundancy) to it at the same time, with occasional client to test if problems occur. So call it 3-4 simultaneous connections via MQTTS TLS on port 8883, SMART/HILD/xxxx topic, but they’re almost always all from the same source IP.
If that’s a problem for some reason in your infrastructure, I am reasonably happy to reduce that to just 2 (IHD and local broker as a bridge), or potentially just one, using the Glow Display’s Glow Internal MQTT topic. In fact I was half way migrating there, but the issue just occurred almost exactly at the same time.
@chris1 Mine is still up. Came back at 12:29, dropped out 12:41-12:44 but has been fine since.
Apart from one missing result at 16:00 my Python suite has been working OK (and the odd missing reading is fairly normal anyway)
Seems to be working OK now after a fresh attempt to log in. Many thanks, David.
Mine is back up again now thanks
Back in business now as well. Thanks @clivee !
Not trying to give you extra work on a stressful enough day, but if you have a moment, would you mind doing a brief post mortem? Just so we know what to do/avoid in the future and additionally for us clients, what to do to make it easier for you in terms of using the endpoint and reporting issues.
Cheers.
Yes, thanks from me too clivee.
I've learned some things; the fact that there are two cloud MQTT endpoints, that port 443 is available and the mosquitto_sub command!
As Phantomski said, if there's any info that would help with future troubleshooting (rather than just saying it's broken) just let us know.👍️