DSMR P1 Port Smartmeter Discovery not working on Openhab 3.4.2

Add-ons Bindings
1

Hi,
im using now a p1 adapter for reading my smartmeter because the optical port is blocking reading by power company.
Now i have the problem if im scanning for my meter im seeing the following in log - but no usable channels:

2023-04-09 16:07:20.872 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'P1_VERSION_OUTPUT' found in the data: Cosem Object(type:P1_VERSION_OUTPUT, cosemValues:{=50})

2023-04-09 16:07:20.874 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'P1_TIMESTAMP' found in the data: Cosem Object(type:P1_TIMESTAMP, cosemValues:{=2023-04-09T16:06:47.000+0200})

2023-04-09 16:07:20.875 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_EQUIPMENT_IDENTIFIER' found in the data: Cosem Object(type:EMETER_EQUIPMENT_IDENTIFIER, cosemValues:{=12345678})

2023-04-09 16:07:20.877 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_DELIVERY_TARIFF1' found in the data: Cosem Object(type:EMETER_DELIVERY_TARIFF1, cosemValues:{=10386.411 kWh})

2023-04-09 16:07:20.878 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_DELIVERY_TARIFF2' found in the data: Cosem Object(type:EMETER_DELIVERY_TARIFF2, cosemValues:{=7757.005 kWh})

2023-04-09 16:07:20.880 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_PRODUCTION_TARIFF1' found in the data: Cosem Object(type:EMETER_PRODUCTION_TARIFF1, cosemValues:{=0.14 kWh})

2023-04-09 16:07:20.881 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_PRODUCTION_TARIFF2' found in the data: Cosem Object(type:EMETER_PRODUCTION_TARIFF2, cosemValues:{=0 kWh})

2023-04-09 16:07:20.882 [INFO ] [.discovery.DSMRMeterDiscoveryService] - Unrecognized cosem object 'EMETER_ACTUAL_PRODUCTION' found in the data: Cosem Object(type:EMETER_ACTUAL_PRODUCTION, cosemValues:{=0 kW})

2023-04-09 16:07:20.883 [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: /ELS5\@V10.04

1-3:0.2.8(50)

0-0:1.0.0(123456789S)

0-0:96.1.1(3230343238363835)

1-0:1.8.1(010386.411*kWh)

1-0:1.8.2(007757.005*kWh)

1-0:2.8.1(000000.140*kWh)

1-0:2.8.2(000000.000*kWh)

1-0:2.7.0(00.000*kW)

1-0:1.7.0()

!35A4

Someone has an idea how to get the channels and read the values in?

2

ok, if someone has same problem - it was easy to solve myself. only create a file manually:

things/dsmr.things

Bridge dsmr:dsmrBridge:mysmartmeter [serialPort="/dev/ttyAMA0"] {
    Things:
        electricity_v4_0_4 electricityV5 [channel=0]
}

and after that the automaticly not created thing “Electricity Meter” appears with channels which are linkable. The only thing you have to do is linking in the channels (use advanced mode too). And all work is done.

3

Looks like your meter is reported less channels than the binding expects. What meter do you have? And from what country?

4

Hi,
country is Switzerland and the meter is semax as 3000 (maybe you know it under brand honeywell).
I tried several metertypes and with electricity_v4_0_4 it was the best because im able to link all tariff-items which device is sending (log) and i which i want to have (all 4 tariffs for delivery and production).
The meter itself has some more obiscodes on optical port (voltages, amperes and some powers and so on) but this im not able to use because my powercompany then cannot readout any more via am110 modem on top of the meter. and on p1 port only the 9 obiscodes are sent which i now able to read out with the manual configured things via thing-file.
as from all readings it seems possible that powercompany can make profiles like a mask which of all available obiscodes were send out by p1 interface which the enduser can not change and only consume.