Engelmann SensoStar 2U with MBus adress 0

[Skol6]

Hi,

I try to connect to my Engelmann SensoStar 2U but this device is using as standard adress 0. Does your adapter supports this adress? I do get allways following error:

M-Bus ID 0 err: Error: Error: Failed to send/receive M-Bus request frame[0].

Regards

[Apollon77]

Yes ID 0 is supported ... please enable debug log and show log

[Skol6]

2022-12-07 07:25:45.395 - info: mbus.0 (30326) Default Update Interval: 3600

2022-12-07 07:25:45.396 - info: mbus.0 (30326) Initialize M-Bus Serial to /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AB0LONWD-if00-port0 with 2400baud

2022-12-07 07:25:45.399 - info: mbus.0 (30326) Schedule initialization for M-Bus-ID 0 with update interval 3600

2022-12-07 07:25:45.426 - debug: mbus.0 (30326) connected set to true

2022-12-07 07:25:45.429 - debug: mbus.0 (30326) connected set to true

2022-12-07 07:25:45.900 - debug: mbus.0 (30326) Process: 0

2022-12-07 07:25:48.221 - warn: mbus.0 (30326) M-Bus ID 0 err: Error: Error: Failed to send/receive M-Bus request frame[0].

2022-12-07 07:25:48.222 - warn: mbus.0 (30326) M-Bus Devices with errors: 1 from 1

2022-12-07 07:25:48.223 - error: mbus.0 (30326) All M-Bus devices could not be read, reinitialize and start over

Die LEDs am MBUS Master blinken auch --> aber keine Antwort vom Engelmann Wärmemengenzähler…

Von: Ingo Fischer @.> Gesendet: Dienstag, 6. Dezember 2022 22:49 An: Apollon77/ioBroker.mbus @.> Cc: Skol6 @.>; Author @.> Betreff: Re: [Apollon77/ioBroker.mbus] Engelmann SensoStar 2U with MBus adress 0 (Issue #307)

Yes ID 0 is supported ... please enable debug log and show log

— Reply to this email directly, view it on GitHub https://github.com/Apollon77/ioBroker.mbus/issues/307#issuecomment-1340054904 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWO2F5KXFMU5WLSGIVCG4X3WL6YF5ANCNFSM6AAAAAASV6EV34 . You are receiving this because you authored the thread.Message ID: @.***>

[Apollon77]

What does the decvice asswer whenyou use admin to search for devices? Did oyou tried to read out with any other tool to make sure it works in general?

[dau0815]

I have the same issue:

mbus.0 | 2023-02-27 13:42:12.113 | error | M-Bus Connection failed. Please check configuration. -- | -- | -- | -- mbus.0 | 2023-02-27 13:42:12.111 | error | Error: No connection possible to MBus Serial port /dev/ttyUSB2 mbus.0 | 2023-02-27 13:42:12.109 | info | Initialize M-Bus Serial to /dev/ttyUSB2 with 2400baud

but command tool works fine: python3 mbus-serial-request-data.py -d -a 0 /dev/ttyUSB2 INFO:meterbus.serial:SEND (005) 10 40 FD 3D 16 INFO:meterbus.serial:SEND (005) 10 5B 00 5B 16 INFO:meterbus.serial:RECV (185) 68 B3 B3 68 08 00 72 19 81 55 30 C5 14 00 04 EC 00 00 00 04 78 A7 47 D2 01 04 06 A3 00 00 00 04 13 EF 57 01 00 04 2B F3 00 00 00 14 2B 81 40 00 00 04 3B 3A 03 00 00 14 3B B8 05 00 00 02 5B 1E 00 02 5F 1E 00 02 61 19 00 02 23 18 00 04 6D 38 28 FB 22 44 06 00 00 00 00 44 13 00 00 00 00 42 6C 00 00 01 FD 17 00 03 FD 0C 05 00 00 84 20 06 00 00 00 00 C4 20 06 00 00 00 00 84 30 06 00 00 00 00 C4 30 06 00 00 00 00 84 40 13 00 00 00 00 C4 40 13 00 00 00 00 84 80 40 13 00 00 00 00 C4 80 40 13 00 00 00 00 84 C0 40 13 00 00 00 00 C4 C0 40 13 00 00 00 00 FC 16 { "body": { "header": { "access_no": 236, "identification": "0x30, 0x55, 0x81, 0x19", "manufacturer": "EFE", "medium": "0x4", "sign": "0x0, 0x0", "status": "0x0", "type": "0x72", "version": "0x0" }, "records": [ { "function": "FunctionType.INSTANTANEOUS_VALUE", "storage_number": 0, "type": "VIFUnit.FABRICATION_NO", "unit": "MeasureUnit.NONE",

[Skol6]

Hi, I have used the Tool LorusFree and MBconfd to test general connection. Adress: 0 Baud Rate: 2400 Also not get any connection. I tried to contact the seller but did not get any feedback yet.. Will try it again.

Which USB MBUS Master are you using? I have measured the ouput of mine and maybe it is only a MBUS Slave.. Regards.

[dau0815]

https://www.ebay.de/itm/314230387195 this simple thing ;-)

and it works fine by: pip3 install pyMeterBus sudo git clone https://gitlab.com/ganehag/pyMeterBus cd pyMeterBus/tools python3 mbus-serial-request-data.py -d -a 0 /dev/ttyUSB2 ,but my plan was to use iobroker.

[Apollon77]

With the infos from that pything test above ... please set adapter to debug then you shpuldalso see the messages flowing - see https://github.com/Apollon77/ioBroker.mbus#how-to-report-issues-and-feature-requests

[dau0815]

Hi, I think that is all what I get: 2023-02-28 11:24:46.629 - debug: mbus.0 (24456) Redis Objects: Use Redis connection: 127.0.0.1:9002 2023-02-28 11:24:46.694 - debug: mbus.0 (24456) Objects client ready ... initialize now 2023-02-28 11:24:46.698 - debug: mbus.0 (24456) Objects create System PubSub Client 2023-02-28 11:24:46.700 - debug: mbus.0 (24456) Objects create User PubSub Client 2023-02-28 11:24:46.782 - debug: mbus.0 (24456) Objects client initialize lua scripts 2023-02-28 11:24:46.791 - debug: mbus.0 (24456) Objects connected to redis: 127.0.0.1:9002 2023-02-28 11:24:46.832 - debug: mbus.0 (24456) Redis States: Use Redis connection: 127.0.0.1:9000 2023-02-28 11:24:46.851 - debug: mbus.0 (24456) States create System PubSub Client 2023-02-28 11:24:46.854 - debug: mbus.0 (24456) States create User PubSub Client 2023-02-28 11:24:46.886 - debug: mbus.0 (24456) States connected to redis: 127.0.0.1:9000 2023-02-28 11:24:47.023 - debug: mbus.0 (24456) Plugin sentry Initialize Plugin (enabled=true) 2023-02-28 11:24:47.396 - info: mbus.0 (24456) starting. Version 2.4.0 in /opt/iobroker/node_modules/iobroker.mbus, node: v16.19.0, js-controller: 4.0.24 2023-02-28 11:24:47.441 - info: mbus.0 (24456) Default Update Interval: 60 2023-02-28 11:24:47.441 - info: mbus.0 (24456) Initialize M-Bus Serial to /dev/ttyUSB2 with 300baud 2023-02-28 11:24:47.444 - error: mbus.0 (24456) Error: No connection possible to MBus Serial port /dev/ttyUSB2 2023-02-28 11:24:47.445 - error: mbus.0 (24456) M-Bus Connection failed. Please check configuration. 2023-02-28 11:24:47.478 - debug: mbus.0 (24456) connected set to false

io-broker run into a docker container ... is that maybe an issue?

[Apollon77]

2023-02-28 11:24:47.444 - error: mbus.0 (24456) Error: No connection possible to MBus Serial port /dev/ttyUSB2

Yu need to stop other processes using this serial port... here no connection at all is possible. So we are net even at the protocol level

[Skol6]

I do get:

2023-02-28 19:17:50.790 - ^[[34mdebug^[[39m: mbus.0 (8648) Update request for device 1 is queued 2023-02-28 19:17:53.116 - ^[[33mwarn^[[39m: mbus.0 (8648) M-Bus ID 0 err: Error: Error: Failed to send/receive M-Bus reque> 2023-02-28 19:17:53.118 - ^[[33mwarn^[[39m: mbus.0 (8648) M-Bus Devices with errors: 2 from 2 2023-02-28 19:17:53.119 - ^[[31merror^[[39m: mbus.0 (8648) All M-Bus devices could not be read, reinitialize and start over 2023-02-28 19:17:53.120 - ^[[32minfo^[[39m: mbus.0 (8648) Default Update Interval: 3600 2023-02-28 19:17:53.121 - ^[[32minfo^[[39m: mbus.0 (8648) Initialize M-Bus Serial to /dev/serial/by-id/usb-FTDI_FT232R_USB> 2023-02-28 19:17:53.124 - ^[[32minfo^[[39m: mbus.0 (8648) Schedule initialization for M-Bus-ID 0 with update interval 3600 2023-02-28 19:17:53.125 - ^[[32minfo^[[39m: mbus.0 (8648) Schedule initialization for M-Bus-ID 1 with update interval 3600 2023-02-28 19:17:53.145 - ^[[34mdebug^[[39m: mbus.0 (8648) connected set to true 2023-02-28 19:17:53.147 - ^[[34mdebug^[[39m: mbus.0 (8648) connected set to true

[Apollon77]

hmm ... there should be more log.

Please try:

• stop adapter
• go into a SSH shell
• execute "iob debug mbus.0"
• is then more log on the com commandline?

[Skol6]

Log: Debugger listening on ws://127.0.0.1:9229/26ef41c6-021e-4bf5-919a-e6cd99458e80 For help, see: https://nodejs.org/en/docs/inspector 2023-02-28 21:38:05.883 - debug: mbus.0 (2566) Redis Objects: Use Redis connection: 127.0.0.1:9001 2023-02-28 21:38:05.979 - debug: mbus.0 (2566) Objects client ready ... initial ize now 2023-02-28 21:38:05.985 - debug: mbus.0 (2566) Objects create System PubSub Client 2023-02-28 21:38:05.989 - debug: mbus.0 (2566) Objects create User PubSub Client 2023-02-28 21:38:06.116 - debug: mbus.0 (2566) Objects client initialize lua scripts 2023-02-28 21:38:06.133 - debug: mbus.0 (2566) Objects connected to redis: 127. 0.0.1:9001 2023-02-28 21:38:06.222 - debug: mbus.0 (2566) Redis States: Use Redis connection: 127.0.0.1:9000 2023-02-28 21:38:06.271 - debug: mbus.0 (2566) States create System PubSub Client 2023-02-28 21:38:06.276 - debug: mbus.0 (2566) States create User PubSub Client 2023-02-28 21:38:06.409 - debug: mbus.0 (2566) States connected to redis: 127.0 .0.1:9000 2023-02-28 21:38:06.611 - debug: mbus.0 (2566) Plugin sentry Initialize Plugin (enabled=true) 2023-02-28 21:38:06.625 - info: mbus.0 (2566) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2023-02-28 21:38:06.650 - error: mbus.0 (2566) adapter disabled 2023-02-28 21:38:06.967 - info: mbus.0 (2566) starting. Version 2.4.0 in /opt/iobroker/node_modules/iobroker.mbus, node: v16.19.1, js-controller: 4.0.24 2023-02-28 21:38:07.053 - info: mbus.0 (2566) Default Update Interval: 3600 2023-02-28 21:38:07.055 - info: mbus.0 (2566) Initialize M-Bus Serial to /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AB0LONWD-if00-port0 with 2400baud 2023-02-28 21:38:07.063 - info: mbus.0 (2566) Schedule initialization for M-Bus-ID 0 with update interval 3600 2023-02-28 21:38:07.114 - debug: mbus.0 (2566) connected set to true 2023-02-28 21:38:07.123 - debug: mbus.0 (2566) connected set to true 2023-02-28 21:38:07.568 - debug: mbus.0 (2566) Process: 0 mbus_sendrecv_request: No M-Bus response frame received. mbus_sendrecv_request: No M-Bus response frame received. mbus_sendrecv_request: No M-Bus response frame received. mbus_sendrecv_request: No M-Bus response frame received. 2023-02-28 21:38:09.876 - warn: mbus.0 (2566) M-Bus ID 0 err: Error: Error: Failed to send/receive M-Bus request frame[0]. 2023-02-28 21:38:09.879 - warn: mbus.0 (2566) M-Bus Devices with errors: 1 from 1 2023-02-28 21:38:09.881 - error: mbus.0 (2566) All M-Bus devices could not be read, reinitialize and start over 2023-02-28 21:38:09.884 - info: mbus.0 (2566) Default Update Interval: 3600 2023-02-28 21:38:09.885 - info: mbus.0 (2566) Initialize M-Bus Serial to /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AB0LONWD-if00-port0 with 2400baud 2023-02-28 21:38:09.889 - info: mbus.0 (2566) Schedule initialization for M-Bus-ID 0 with update interval 3600 2023-02-28 21:38:09.910 - debug: mbus.0 (2566) connected set to true 2023-02-28 21:38:09.914 - debug: mbus.0 (2566) connected set to true

[Apollon77]

Ok, this log states that the mbus master do not even answered at all to the requests send out by the adapter/library

[Skol6]

I have now changed the MBUS adapter and now everything is working perfect. Seems to be a hardware issue. Thanks for your support!