There is a bug in the binding causing this. Please try the marketplace binding.
how long is it scanning?? There is no loading bar
ok it takes about 2 minutes til the loading bar appears but after the scan no result
Any information in the log?
no nothing
And if you manually add the bridge?
I see a port USB0 which I choose, add my req. key (I have no additional key) and status stays Unknown
(Assuming you run the marketplace binding). Can you run discovery with the bridge configured. Do you get any additional information in the log?
no sorry I get nothing
I have two Smart meters by Sagemcom. Unfortunately, the S210 is not recognized by the binding when scanning while the bridge is working.
This is the log:
2023-04-08 04:05:52.605 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'P1_VERSION_OUTPUT' found in the data: Cosem Object(type:P1_VERSION_OUTPUT, cosemValues:{=50})
2023-04-08 04:05:52.607 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'P1_TIMESTAMP' found in the data: Cosem Object(type:P1_TIMESTAMP, cosemValues:{=2023-04-08T04:12:38.000+0200})
2023-04-08 04:05:52.609 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_DELIVERY_TARIFF0' found in the data: Cosem Object(type:EMETER_DELIVERY_TARIFF0, cosemValues:{=3930.632 kWh})
2023-04-08 04:05:52.611 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_DELIVERY_TARIFF1' found in the data: Cosem Object(type:EMETER_DELIVERY_TARIFF1, cosemValues:{=2847.578 kWh})
2023-04-08 04:05:52.612 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_DELIVERY_TARIFF2' found in the data: Cosem Object(type:EMETER_DELIVERY_TARIFF2, cosemValues:{=1083.054 kWh})
2023-04-08 04:05:52.614 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_ACTUAL_DELIVERY' found in the data: Cosem Object(type:EMETER_ACTUAL_DELIVERY, cosemValues:{=2.391 kW})
2023-04-08 04:05:52.616 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_PRODUCTION_TARIFF0' found in the data: Cosem Object(type:EMETER_PRODUCTION_TARIFF0, cosemValues:{=78.266 kWh})
2023-04-08 04:05:52.617 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_PRODUCTION_TARIFF1' found in the data: Cosem Object(type:EMETER_PRODUCTION_TARIFF1, cosemValues:{=78.266 kWh})
2023-04-08 04:05:52.619 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_PRODUCTION_TARIFF2' found in the data: Cosem Object(type:EMETER_PRODUCTION_TARIFF2, cosemValues:{=0 kWh})
2023-04-08 04:05:52.621 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_ACTUAL_PRODUCTION' found in the data: Cosem Object(type:EMETER_ACTUAL_PRODUCTION, cosemValues:{=0 kW})
2023-04-08 04:05:52.623 [INFO ] [.discovery.DSMRMeterDiscoveryService] - There are unrecognized cosem values in the data received from the meter, which means some meters might not be detected. Please report your raw data as reference: /EST5\253740942_A
1-3:0.2.8(50)
0-0:1.0.0(230408041238S)
1-0:1.8.0(003930632*Wh)
1-0:1.8.1(002847578*Wh)
1-0:1.8.2(001083054*Wh)
1-0:1.7.0(000002391*W)
1-0:2.8.0(000078266*Wh)
1-0:2.8.1(000078266*Wh)
1-0:2.8.2(000000000*Wh)
1-0:2.7.0(000000000*W)
!DB85
@hilbrand can you help?
Thank you so much!
The meter seems to report less channels than the binding expects. I’ll update the binding. In the mean time you can manually add the meter in a text file. For the electricity meter you can use the thing electricity_smarty_v1_0_austria (I noticed this type is missing from the binding documentation, so I’ll add this too). Adding it manually should make it work, as the specific channel configuration is only an issue when trying to detect a meter, not when using the meter things.
Thank you, works great!
Fyi they say this year the ‘official adapter’ for Austria will be for sale as well. Data sheet already available:
I live in Tyrol and have a KaifaMA309MHALAT1 Smartmeter with M-Bus Adapter. I use a python script on a Pi3 with M-Bus-USB Adapter to read the data from the Smartmeter. The Pi3 send MQTT data which I read with my Openhab running on Pi4 and store it in the RRD4j database. Please sent a note if you are interested in the python3 script.
Hi, I’m also from Graz and bought this device: https://smartgateways.nl/product/slimme-meter-wifi-gateway/
My problem is that the Sagemcom has not voltage output between Pin 1 and 6.
Is this normal on a T210-D-r?
Thanks Thomas