Belgian smart meter telegram causes crash of plugin #47
Labels
enhancement
New feature or request
Comments
|
As far as I can see this is related to the gas meter. I also found following quote of the Flemish grid operator: Let wel: In Nederland meet de meter 'temperatuur gecorrigeerde volume' die wordt ondergebracht in OBIS-code 0-1:24.2.1. In Belgie meet de meter bij wet 'niet-temperatuur gecorrigeerd volume' die wordt ondergebracht in OBIS-code 0-1:24.2.3. Dus voor gas verschijnt op de gebruikerspoort 0-1:24.2.3 als gaswaarde. Hierdoor moet een dergelijke applicatie wel worden aangepast aan de Vlaamse meter. For a reference the full list of used codes in Belgium.
Also another interesting fact is that the Flemish meter uses register 2 for low (offpeak) usage. In the Netherlands they use register 1. |
|
Next time, please quote the output; the Cool, I didn't know they used (more or less) the same scheme in Belgium (Flandres?). Does Homebridge P1 connect with the default settings, or did you have to set I think Homebridge P1 expects the serial number of the gas meter on 0-1:96:1.0 instead of on 0-1:96:1.1. The Belgium protocol looks similar enough to the Dutch protocol to support it in Homebridge P1. Not sure how to expose the switch positions or the max allowed power and current. The DSMR version (1-3:0.2.8) doesn't seem to be present in the telegram, maybe I can use that to identify a Belgium telegram? Not happy about the reversed high/low tariff; need to figure out how best to deal with that. |
|
Hi thanks for the quick reply. The max power/current is currently not used that often in Flanders. Today only used in prepaid meters which always gives you 6A when your prepaid card is empty. If you reload your prepaid card it will change back to 999A. It’s a fixed read only value that shouldn’t be exposed to homebridge in my opinion (for now). About low/high tariff: maybe you can just call it tariff 1 and 2? |
ebaauw
added a commit
that referenced
this issue
Mar 21, 2021
Add support for Belgium telegrams, see #47.
|
Could you try beta v1.2.1-0? |
|
Seems all okay now. Solar panels are delivering a little bit now: |
|
Maybe for your documentation… and our smart meter looks like this: |
|
Maybe 1 remark related to the solar panels. But the current consumption of 0W is not always updated. see movie: In the logs you dont see the update to 0W. if you update current consumption delivered, you should set the normal current consumption to 0W. Always 1 of both should be 0W. |
Are you sure it should be 0? I don't have solar panels, and cannot test this myself. I'm not doing anything special between consuming vs delivering power; my best guess would be that your meter still delivers telegrams with power delivered set. Could you set Log Level to 3 (ludicrous logging) next time this happens to see the (parsed) telegrams? |
|
Okay I’ll check it tomorrow. |
|
The meter is delivering the info correct. In below example some message around 08:57:45 are lost. |
|
I’ve never seen messages between Homebridge and HomeKit “getting lost”. Did you refresh the screen in Eve? Did you try another HomeKit app? I take it, Current Consumption does correctly display the non-zero values? |
|
non-zero values seems to be updated correctly, but it's hard to verify. I checked also in the HOME+ app. even weirder is that there I see a different consumption which is also not correct. same app 7 minutes later, values not changed: |
I also see different values for Last Updated, so they don't show data from the same telegram. Note that Last Updated lists the timestamp from electricity network, as listed in the telegram, not the system time. In my case, it's off by 32s. Checking my meter, by setting Log Level to 2 and running: It looks like my meter refreshes the power every 10 seconds (the value only changes at 10s intervals). Eve displays all the updates in real-time; Last Updated every second, and Total Consumption, Total Consumption Normal, and Current Consumption every 10 seconds. From what I can tell, there are no "missing messages". Even if the value would be refreshed every second, I would expect any issue: Eve shows the new Last Updated value every second. |
|
"Last updated" is updated each second. Same for power/total consumption/voltage/current, that also changes each second. I see that it changes each second in eve (So yet another difference between Belgium and the Netherlands). Sometimes it glitches and then I don’t see updates in Eve for some seconds. But in the homebridge logs each second an update was sent. When I’m consuming electricity each second I get the following updates:
Electricity Delivered:
That’s why you only see the last update change in above screenshots Attached a video demonstrating it (consumption_back fixed on 2019W (Eve) and 452W (Home+), and it stays on those values until sunrise tomorrow). WhatsApp.Video.2021-03-23.at.18.56.37.mp4 |
In that case, the notification from the HAP server to HomeKit went MIA somehow. Indeeed, no new notification will be sent, until the value changes. However, when you refresh the screen (pull down), HomeKit should re-read the value from the HAP server. Same when you force-quit and restart Eve. Do you see the same behaviour on multiple iDevices, or only on one? The notifications no HomeKit are handled by HAP-NodeJS; no Homebridge plugin sits in between that traffic. You can run Homebridge with |
Yeah you're right: pull down did the trick (strange because I thought that I tried that already, bit apparently not)
I saw it on my iPad and iPhone
I'l try that one later. But for me the issue is solved, now that I know I can refresh it in Eve. |
@thomas-svrts Do you have a link where you got this info? Cannot seem to find it on fluvius.be? |
|
See last 2 pages of Annex A1 (Belgium) + A2(Flemish specs) |
|
Thanks, doc provides some new insights.
|
True, but only going to happen in the case you don’t pay you bills. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Below the debug info for a Belgian DSMR meter.
For some reason the plugin crashes on the received telegrams.
The text was updated successfully, but these errors were encountered: