Hello,
I now use TRuDi to read my metering data from the smart meter gateway. The gateway documentation mentioned a machine-2-machine interface (REST) for the HAN (home area network) side, but I could not find documentation for it. Is any other user of this hardware around with access to the M2M documentation?
Cheers
Did you manage to connect your TRuDi to Home Assistant? I’ve just learned that our Netzbetreiber offers this system too.
Cheers
hey you both. Did you find anything for integrating TRuDI or HAN into homeassisant?
Hello together,
Me too, I’m looking around for a way to convince my “intelligentes Messsystem” via TRuDi to my working Home Assistant.
Two years ago I read about TRuDi and I asked EON to send me username and password for to connect to the system.
I got no answer and no information about my electrical consumption.
Last week they send me two letters with the USER-ID and my pin.
I connected the HAN Port of the “intelligentes Messsystem” with a switch in my local network, but no new device appeared in the list of connected IP nodes.
Is there anyone who could give me some advice how to use the TRuDi software or an integration in Home Assistant ?
Here ist another thread with the same topic:
I found the manual on this page and in this PDF: CONEXA 3.0 AGD-LV v3.80.x.pdf.
On page 23 they write this (Translated with Deepl):
The devices and tools required by the end user to connect to the SMGW at the HAN interface are listed here:
- A PC or tablet with a freely configurable network interface (LAN), alternatively this can also be configured in advance
- IP address of the SMGW (this is provided to the end user by the operator/user)
- A standard web browser (e.g. Mozilla Firefox) for access via a web browser
- A REST client for accessing the M2M interface, such as Postman (https://getpostman.com)
- A standard LAN cable (Ethernet cable)
- A connection between the PC or tablet and SMGW must be established. To do this Plug the Ethernet cable into the free Ethernet socket on the PC and into the HAN interface on the SMGW
- The network connection on the PC must be configured as per E-3.
- As an alternative to a REST client, a reference implementation of an end consumer tool (TRuDI) can be obtained from the manufacturer or the Physikalisch-Technische Bundesanstalt (PTB) (see chapter A-10).
- The connection between the end consumer and the SMGW is protected by cryptographic mechanisms. Transport Layer Security (TLS) version 1.2 is used here,
- All programs used by the end consumer to communicate with the SMGW must support this protocol.
Hey all,
I was also looking into reading my smart meter data via HomeAssistant (also using the Conexa 3.0 communication module). Are you able to access the gateway through your browser? According to the documentation it provides a webserver, however Chrome tells me the device refused the connection when accessing through http(s).
I read an interesting part in the manual:
Der Letztverbraucher muss auf dem SMGW konfiguriert sein. Dies muss
durch den GWA im Auftrag des Betreibers/Verwenders konfiguriert werden. Ohne diese Konfiguration ist kein Verbindungsaufbau zum SMGW
möglich.
→ it seems the operating company needs to configure enduser access. I’m reaching out to mine to investigate options
Yes, I changed the the other topic an posted my solution there:
Hallo in die Runde,
auch ich habe Theben Conexa 3.0 als Smart Meter Gateway von meinem Netzbetreiber erhalten. Die Mitteilung von Benutzernamen und Password lief reibungslos - per Papier 
. Bei mir war als IP-Adresse der Bereich eingetragen, der in meinem Fritz!Box-Netzwerk bestand. Ich habe ha-ppc-smgw eingesetzt und es hat auf Anhieb geklappt. Mein Dashbord “Energy” sieht jetzt richtig schick aus.
So schön jetzt alles auch ist, so steinig war der Weg bis hierher.
Moin, was hast Du als URL eingegeben fĂĽr ein Theben Conexa 3.0
? Bist Du das auch aus diesem Chat, zeitlich verwirrt mich das etwas, bei Dir hat das ja anscheinend schon frĂĽher geklappt, also am 22 Februar 2022 und unten aufgefĂĽhrte Eintrag ist aus dem Jahr 2025
Danke!
Hallo in die Runde,
am 22.02.2025 habe ich mich blenden lassen von Demo-Daten. Der Zugriff auf mein SMGW funktioniert immer noch nicht.
Momentan versuche ich es mit dem Link https://192.168.XXX.XXX/smgw/m2m/{{Einspeisung-userid}}.sm/json
Problem ist derzeit der Austausch von Zertifikaten zwischen SMGW und HA. Ohne Zertifikate geht gar nichts, so meine bisherigen Erfahrungen.
Mit dem Browser komme ich auf die Startseite.
Hello everyone,
the problems with Conexa from Theben have not left me in peace in the last few days. A small note at the end of the LOGS gave me an idea. It said that the transfer of the attributes was limited to 255 characters and was therefore truncated. The idea now is to try as described in
Integration with Gardena Smart Sileno mowers, by using sensors
, i.e. with sensors and with template sensors in the configuration.yaml. Here is the code for the sensor:
sensor:
# Get Theben Conexa SMGW ID
- Name: theben_conexa_smgw_id
platform: rest
resource: https://192.168.XXX.XXX:443/smgw/m2m/<userID>.sm/json #Die UserID was fetched via TruDi
method: POST
scan_interval: 900 # query every 15 minutes
verify_ssl: false # SMGW uses a self-signed certificate
authentication: digest # Enable digest auth
username: "<username>" # as communicated by the carrier
password: "<Password>" # as communicated by the carrier
Header:
Content-Type: application/json
payload: '{"method": "smgw-info"}'
json_attributes:
- SMGW-Info
value_template: 'ok' # only this string is decisive here, no retrieval of values.
Now the template-sensor is used:
Template:
-sensor:
- name: "SMGW Firmware Version"
unique_id: smgw_firmware_version
state: "{{ states.sensor.theben_conexa_smgw_id.attributes.get('smgw-info', {}).get('firmware-info', {}).get('version', 'Unknown') }}"
Voila:
Uploading: image.png…
Uploading: Screenshot 2025-06-04 112242.jpg…
Do you think we can make progress on this path?
That’s how far I’ve come with my work:
Uploading: Scan 06 Juni 25 · 12·05·07 17492043070991.png…
Now fine-tuning is necessary.
Moin, die Bilder kann ich nicht öffnen, dass nur zur Info.
Name → muss name
und Header → muss headers
mit User ID meinst Du die ID des Kunden? dann inkl. han-user-cfbxxxx-xxx-xxx
einsetzen wo userID steht?
sensor:
# Get Theben Conexa SMGW ID
- name: theben_conexa_smgw_id
platform: rest
resource: https://192.168.XXX.XXX:443/smgw/m2m/<userID>.sm/json #Die UserID was fetched via TruDi
method: POST
scan_interval: 900 # query every 15 minutes
verify_ssl: false # SMGW uses a self-signed certificate
authentication: digest # Enable digest auth
username: "<username>" # as communicated by the carrier
password: "<Password>" # as communicated by the carrier
headers:
Content-Type: application/json
payload: '{"method": "smgw-info"}'
json_attributes:
- SMGW-Info
value_template: 'ok' # only this string is decisive here, no retrieval of values.