Marcin
6 Wrzesień 2023 14:00
1
Cześć,
Pozdrawiam
1 polubienie
rafkan
6 Wrzesień 2023 17:07
2
Wmbusmeters masz zainstalowany jako dodatek w HA?, jeśli tak to jaką masz wersję tego dodatku.
Marcin
6 Wrzesień 2023 17:10
3
Tak mam jako dodatek.
rafkan
6 Wrzesień 2023 17:16
4
Z jakiego tunera/dongla korzystasz?
Mniejsza o to, zrób Sobie kopię ustawień liczników z których czytasz stany. W konfiguracji Wmbusmeters zostaw tylko pierwszą zakładkę “wmbusmeters configuration”, z zakładki " Meters" usuń liczniki które masz zdefiniowane.
w pozycji “device” na końcu Swojego dongla dopisz “c1”
json
/config/wmbusmeters/wmbusmeters.log
normal
true
/wmbusmeters/mosquitto_pub.sh "wmbusmeters/$METER_NAME" "$METER_JSON"
zapisz i uruchom ponownie dodatek.
/config/wmbusmeters/wmbusmeters.log
pojawią Ci się znalezione liczniki.
Jak już znajdziesz czego szukasz powróć do poprzednich ustawień i w pozycji “device” na końcu dopisz: c1,t1. W mojej konfiguracji to wygląda tak:
/dev/ttyUSB0:im871a[00103001]:c1,t1
Marcin
7 Wrzesień 2023 10:20
5
Cześć,
Dzięki za info udało się zebrać trochę danych.
Received telegram from: 10315468
manufacturer: (TCH) Techem Service (0x5068)
type: Heat Cost Allocator (0x08) encrypted
ver: 0x6a
device: rtlwmbus[00000001]
rssi: 158 dBm
driver: unknown!
telegram=|_1F446850685431106A087A8E0010253BD809A049B5E003711071E9C5BB23332F|+1515
rafkan
7 Wrzesień 2023 10:29
6
Dekodowałeś otrzymany telegram na https://wmbusmeters.org/ ?
to nie będzie ten?
Techem FHKV data II/III (fhkvdataiii)
lub ten
Heat meter Techem vario 4 (vario451) (non-standard protocol)
Ale jeśli masz podzielniki to ten pierwszy.
Marcin
7 Wrzesień 2023 10:42
7
Tak sprawdzałem, ale niestety żaden z tych driver-ów nie działa? Może są szyfrowane ?
rafkan
7 Wrzesień 2023 11:02
8
Poniżej masz wątek o tym podzielniku
opened 07:44AM - 06 Jan 21 UTC
closed 07:38PM - 24 Jan 21 UTC
Dear Fredrik,
I'm super happy with your Wireless M-Bus program, it performs g… reat on my raspberry pi. I got three Wireless M-Bus Meter from Techem to test:
- Heat cost allocator FHKV radio 4
- Water meter T30 with radio module 4
- Techem Kamstrup heat meter Multical 302
I realized that all meter types have unknown driver, therefore I went through the how to add new meters with the goal that I can add as many meters as Techem can send me :P
I show you my progress so far with the FHKV 4:
Here the message:
```
Received telegram from: 14542076
manufacturer: (TCH) Techem Service (0x5068)
type: Heat Cost Allocator (0x08)
ver: 0x94
device: im871a[00102489]
rssi: -65 dBm
driver: unknown!
```
with the telegram:
`telegram=||4E4468507620541494087AAD004005089D86B62A329B3439873999738F82461ABDE3C7AC78692B363F3B41EB68607F9C9160F550769B065B6EA00A2E44346E29FF5DC5CB86283C69324AD33D137F6F|`
key: FCF41938F63432975B52505F547FCEDF
I created the file simulation_mymeter.txt in documents and executed the following command:
`wmbusmeters --debug simulation_mymeter.txt HKVT fhkvdataiii 14542076 FCF41938F63432975B52505F547FCEDF`
with the following result:
```
(wmbusmeters) version: 1.0.3-20-gd8b6583
(config) using device: simulation_mymeter.txt:any
(config) number of meters: 1
(main) configured "HKVT" "fhkvdataiii" "14542076" encrypted
(lookup) with file "simulation_mymeter.txt"
(lookup) driver: simulation file
(main) opening simulation_mymeter.txt:any
Started config simulation on simulation_mymeter.txt listening on any
(simulation) in simulation_mymeter.txt
(main) regular reset of simulation on simulation_mymeter.txt will happen every 82800 seconds
(main) added simulation_mymeter.txt to files
(wmbus) no alarm (expected activity) for simulation
(main) simulation_mymeter.txt already configured as simulation
(serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds
(simulation) from file "4E4468507620541494087AAD004005089D86B62A329B3439873999738F82461ABDE3C7AC78692B363F3B41EB68607F9C9160F550769B065B6EA00A2E44346E29FF5DC5CB86283C69324AD33D137F6F"
(wmbus) parseDLL @0 79
(meter) HKVT: for me? 14542076
(meter) HKVT: meter detection did not match the selected driver fhkvdataiii! correct driver is: unknown!
(meter) please consider opening an issue at https://github.com/weetmuts/wmbusmeters/
(meter) to add support for this unknown mfct,media,version combination
(meter) HKVT: yes for me
(meter) HKVT fhkvdataiii handling telegram from 14542076
(meter) HKVT 14542076 "4E4468507620541494087AAD004005089D86B62A329B3439873999738F82461ABDE3C7AC78692B363F3B41EB68607F9C9160F550769B065B6EA00A2E44346E29FF5DC5CB86283C69324AD33D137F6F"
(wmbus) parseDLL @0 79
(telegram) DLL L=4e C=44 (from meter SND_NR) M=5068 (TCH) A=14542076 VER=94 TYPE=08 (Heat Cost Allocator) (driver unknown!) DEV= RSSI=0
(wmbus) parseELL @10 69
(wmbus) parseAFL @10 69
(wmbus) parseTPL @10 69
(TPL) decrypting "089D86B62A329B3439873999738F82461ABDE3C7AC78692B363F3B41EB68607F9C9160F550769B065B6EA00A2E44346E29FF5DC5CB86283C69324AD33D137F6F"
(TPL) num encrypted blocks 4 (64 bytes and remaining unencrypted 0 bytes)
(TPL) IV 6850762054149408ADADADADADADADAD
(TPL) decrypted "2F2F036E020000436E190000426C9F2C83046E00000082046C7F2A8D04EE1F1E72FE000000000000000000000000000000000000000000000000030016002F2F"
(dvparser) found new format "036E436E426C83046E82046C8D04EE1F" with hash 4628, remembering!
(telegram) TPL CI=7a ACC=ad STS=00 CFG=0540 (AES_CBC_IV nb=4 cntn=0 ra=0 hc=0)
telegram=|4E4468507620541494087AAD0040052F2F|036E020000436E190000426C9F2C83046E00000082046C7F2A8D04EE1F1E72FE000000000000000000000000000000000000000000000000030016002F2F|+0
(fhkvdataiii) 00: 4e length (78 bytes)
(fhkvdataiii) 01: 44 dll-c (from meter SND_NR)
(fhkvdataiii) 02: 6850 dll-mfct (TCH)
(fhkvdataiii) 04: 76205414 dll-id (14542076)
(fhkvdataiii) 08: 94 dll-version
(fhkvdataiii) 09: 08 dll-type (Heat Cost Allocator)
(fhkvdataiii) 0a: 7a tpl-ci-field (EN 13757-3 Application Layer (short tplh))
(fhkvdataiii) 0b: ad tpl-acc-field
(fhkvdataiii) 0c: 00 tpl-sts-field
(fhkvdataiii) 0d: 4005 tpl-cfg 0540 (AES_CBC_IV nb=4 cntn=0 ra=0 hc=0 )
(fhkvdataiii) 0f: 2f2f decrypt check bytes
(fhkvdataiii) 11: 03 dif (24 Bit Integer/Binary Instantaneous value)
(fhkvdataiii) 12: 6E vif (Units for H.C.A.)
(fhkvdataiii) 13: 020000
(fhkvdataiii) 16: 43 dif (24 Bit Integer/Binary Instantaneous value storagenr=1)
(fhkvdataiii) 17: 6E vif (Units for H.C.A.)
(fhkvdataiii) 18: 190000
(fhkvdataiii) 1b: 42 dif (16 Bit Integer/Binary Instantaneous value storagenr=1)
(fhkvdataiii) 1c: 6C vif (Date type G)
(fhkvdataiii) 1d: 9F2C
(fhkvdataiii) 1f: 83 dif (24 Bit Integer/Binary Instantaneous value)
(fhkvdataiii) 20: 04 dife (subunit=0 tariff=0 storagenr=8)
(fhkvdataiii) 21: 6E vif (Units for H.C.A.)
(fhkvdataiii) 22: 000000
(fhkvdataiii) 25: 82 dif (16 Bit Integer/Binary Instantaneous value)
(fhkvdataiii) 26: 04 dife (subunit=0 tariff=0 storagenr=8)
(fhkvdataiii) 27: 6C vif (Date type G)
(fhkvdataiii) 28: 7F2A
(fhkvdataiii) 2a: 8D dif (variable length Instantaneous value)
(fhkvdataiii) 2b: 04 dife (subunit=0 tariff=0 storagenr=8)
(fhkvdataiii) 2c: EE vif (Units for H.C.A.)
(fhkvdataiii) 2d: 1F vife (Compact profile without register)
(fhkvdataiii) 2e: 1E varlen=30
(fhkvdataiii) 2f: 72FE00000000000000000000000000000000000000000000000003001600
(fhkvdataiii) 4d: 2F skip
(fhkvdataiii) 4e: 2F skip
HKVT 14542076 0 hca 2021-12-06T02:00:00Z 1155 hca 2022-04-31T02:00:00Z 11.54 °C 326.2 °C 2021-01-05 14:26.51
(serial) stopping manager
(serial) waiting for stop
(serial) EVENT thread interrupted
(serial) event loop stopped!
(serial) TIMER thread interrupted
(wmbus) deleted simulation
```
Opened meters.h and added
` X(fhkvdataiv, T1_bit, HeatCostAllocationMeter, FHKVDATAIV, FHKVDataIV) \`
to LIST_OF_METERS and:
` X(FHKVDATAIV,MANUFACTURER_TCH, 0x08, 0x94) \`
to METER_DETECTION
I then added the line $(BUILD)/meter_fhkvdataiv.o \
to the Makefile.
Then I copied meter_fhkvdataiii.cc and renamed it to meter_fhkvdataiv.cc. I changed all the MeterFHKVDataIII to MeterFHKVDataIV as well as createFHKVDataIII to createFHKVDataIV in line 52. According to your manual, I have to adapt now the void MeterFHKVDataIV::processContent(Telegram *t), so I did the following:
```
void MeterFHKVDataIV::processContent(Telegram *t)
{
// Unfortunately, the Techem FHKV data ii/iii is mostly a proprieatary protocol
// simple wrapped inside a wmbus telegram since the ci-field is 0xa0.
// Which means that the entire payload is manufacturer specific.
vector<uchar> frame;
t->extractPayload(&frame);
}
```
after that, I change my directory to the place where I cloned the program and executed
`make DEBUG=TRUE HOST=arm`
which worked flawlessly.
Now is the point where I'm starting to get problems. When I try to execute the following:
```
pi@raspberrypi:~/Repos/********.Microservice.WMBus/wmbusmeters $ ./build_arm_debug/wmbusmeters simulation_mymeter.txt
==3776==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD.
```
I thought maybe I have to cd into build_arm_debug, so I tried the following:
```
pi@raspberrypi:~/Repos/********.Microservice.WMBus/wmbusmeters/build_arm_debug $ wmbusmeters /home/pi/Repos/********.Microservice.WMBus/wmbusmeters/simulation_mymeter.txt
No meters configured. Printing id:s of all telegrams heard!
Received telegram from: 14542076
manufacturer: (TCH) Techem Service (0x5068)
type: Heat Cost Allocator (0x08)
ver: 0x94
driver: unknown!
```
Still, the driver is unknown, what did I do wrong? Shouldn't it have changed now?
Thank you in advance for your help!
Best regards,
Oliver
Marcin
7 Wrzesień 2023 11:14
9
NIestety gość tylko wspomniał o podzielnikach ale nie rozwiązał problemu. Objawy podobne mam bo wyłapuje tylko jeden podzielnik z 4. Z powiązanych artykułów wynika że powinno to działać, ale może mam jakieś nowsze oprogramowanie. Chyba będę musiał tam zgłosić problem.
Zadzwoniłem do spółdzielni i okazało się że transmisja jest szyfrowana. Spróbuje jeszcze uderzyć do Techem ale raczej klucza nie będą chcieli podać.
