Hello! 👋
Sorry to make another thread about this - I couldn't find a similar one that matched the issue I've been having 🙈
Since the morning of June 5th, neither my Chameleon IHD3-PPMID-V3 (provided by E.On Next) or my Hildebrand Glow SMETS2 CAD have been able to join the smart meter HAN.
I've spoken to E.On Next through Facebook Messenger - and to be fair, the people I've spoken to have been really helpful! Unfortunately though, they've passed me through to the smart meter team who have a backlog of multiple weeks so they've not responded yet.
It seems as though my comms hub has dropped off the network entirely; it doesn't seem as though E.On Next are able to grab a reading from what the advisors in chat have said.
Everything seems fine down on the meter as it's showing the readings if I check manually.
If anyone has any clues at all, it'd be hugely appreciated!
Have a great evening in the sun folks ☀️
Aaron
Sorry to make another thread about this - I couldn't find a similar one that matched the issue I've been having 🙈
Since the morning of June 5th, neither my Chameleon IHD3-PPMID-V3 (provided by E.On Next) or my Hildebrand Glow SMETS2 CAD have been able to join the smart meter HAN.
I've spoken to E.On Next through Facebook Messenger - and to be fair, the people I've spoken to have been really helpful! Unfortunately though, they've passed me through to the smart meter team who have a backlog of multiple weeks so they've not responded yet.
It seems as though my comms hub has dropped off the network entirely; it doesn't seem as though E.On Next are able to grab a reading from what the advisors in chat have said.
Everything seems fine down on the meter as it's showing the readings if I check manually.
Extra info:
- Meter: Landis+Gyr E470 (type 5424) with the green A and grey B to the right of the display.
- Comms hub: WNC UBC-TN6 on the Telefonica network (East Midlands)
MQTT data being returned by Hildebrand:
Code:
{
"elecMtr": {
"0702": {
"00": {}
}
},
"gasMtr": {
"0702": {
"00": {}
}
},
"ts": "2022-06-21 16:40:20",
"hversion": "GLOW-IHD-01-1v4-SMETS2",
"time": "62B1F474",
"zbSoftVer": "1.2.5",
"gmtime": 1655829620,
"pan": {
"rssi": "00",
"status": "rejoin_failed",
"nPAN": "00",
"join": "0",
"lqi": "FF"
},
"smetsVer": "SMETS2",
"gid": "[REDACTED]"
}
And from the new local MQTT feature:
Code:
{
"software": "v1.8.12",
"timestamp": "2022-06-21T16:55:00Z",
"hardware": "GLOW-IHD-01-1v4-SMETS2",
"ethmac": "[REDACTED]",
"smetsversion": "SMETS2",
"eui": "[REDACTED]",
"zigbee": "1.2.5",
"han": {
"rssi": 0,
"status": "not joined",
"lqi": 255
}
}
If anyone has any clues at all, it'd be hugely appreciated!
Have a great evening in the sun folks ☀️
Aaron
Last edited by aaroncarson; 22-06-22 at 10:48. Reason: Adding local MQTT data
