search

robertsLando / node-red-contrib-m-bus

Node-Red node for M-Bus protocol
MIT License
10 stars 6 forks source link

Ethernet mbus Gateway ge20v Solvimus #16

Closed ManUtd9494 closed 1 year ago

ManUtd9494 commented 3 years ago

Dear robertsLando

The gateway recognises the meters perfectly with the M Tool software. However, with the node red m bus contribution only 1 meter is recognised. The Solvimus support thinks that this may be due to a small adjustment. Can we adjust this together in the source code? I have a gateway and can provide this data for diagnosis. Thank you very much.

https://www.solvimus.de/de/produkt/mbus-ge20v-mbus-ge80v/

robertsLando commented 3 years ago

try to update the mbus library dep

ManUtd9494 commented 3 years ago

node-mbus is already 1.2.1 node-red-contrib-m-bus is already 2.0.0 node red v 1.2.9 now also latest version.

reinstall npm, nodejs 14.15.5, nodered an then node-red-contrib-m-bus

Now I receive the Debug for each Device x/12 Error while reading device x : Error: Failed to send/receive M-Bus request frame[x].

Can I try anything else?

robertsLando commented 3 years ago

node-mbus is already 1.2.1

that's maybe the version on your package.json, but did you update it also inside deps of node-red-contrib-m-bus?

ManUtd9494 commented 3 years ago

I have carried out all updates again. now i still get errors, but it shows me the meters in the dashboard. however, only one is written to the the "known meters" file. This is also the only one for which the ID is displayed. for the others, only the primary ID is displayed. can it be related to the fact that it only writes this meter to the "known meters" file?

If you deploy again, all metres except one will be lost. Can I adjust this somewhere?

robertsLando commented 3 years ago

You could manually edit that file to make this automatically scan also that id