eBus Schaltung V2 in Betrieb nehmen

[john30]

Wie geh ich der Sache auf den Grund ?

mal im mosquitto log schauen, ob da was zu finden ist, bzw. dessen log level erhöhen

[pink99panther]

Hallo,

habe das gleiche Problem wie TommLee.
Hier mal ein Auszug aus meinem Log zum Zeitpunkt des Verbindungsverlustes.

Code Auswählen Erweitern

2019.10.12 15:24:12 4: MyBroker_192.168.115.55_49354 ESPClient_5C:CF:7F:80:58:E2_156 CONNECT V:4 keepAlive:10 LWT:/Kellersensor/status/LWT:Connection Lost usr:
2019.10.12 15:24:12 4: Connection closed for MyBroker_192.168.115.215_49155: EOF
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000DVES_E8A4F6\000tele/sonoffpow1/LWT\000offline
2019.10.12 15:24:13 4: Connection closed for MyBroker_192.168.115.221_20714: EOF
2019.10.12 15:24:13 4: Connection accepted from MyBroker_192.168.115.215_49157
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000ESPClient_2C_3A_E8_2E_A0_8E\000/ESP_Klingel/status/LWT\000Connection Lost
2019.10.12 15:24:13 4: Connection closed for MyBroker_192.168.115.214_49157: EOF
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000ESPClient_60_01_94_07_A1_AA\000/ESP_Hoflicht/status/LWT\000Connection Lost
2019.10.12 15:24:13 4: Connection closed for MyBroker_192.168.115.213_49155: EOF
2019.10.12 15:24:13 1: 127.0.0.1:1883 reappeared (MQBroker)
2019.10.12 15:24:13 5: PUBLISH: 0I(0)(31)wolf_ebus/betrd_bm2/temp_return{(10)     "0": {"name": "", "value": 23.9}}
2019.10.12 15:24:13 4: MyBroker_192.168.115.45_48562 wolf_ebus PUBLISH wolf_ebus/betrd_bm2/temp_return:{
     "0": {"name": "", "value": 23.9}}
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000wolf_ebus\000wolf_ebus/betrd_bm2/temp_return\000{\n     "0": {"name": "", "value": 23.9}}
2019.10.12 15:24:13 5: PUBLISH: 0(144)(2)(0)(25)wolf_ebus/broadcast/betrd{(10)     "betrd_status": {"value": 0},(10)     "zustand": {"value": "00"},(10)     "stellgrad": {"value": null},(10)     "kesseltemp": {"value": 24.0},(10)     "ruecklauftemp": {"value": 23},(10)     "boilertemp": {"value": 48},(10)     "aussentemp": {"value": 20}}
2019.10.12 15:24:13 4: MyBroker_192.168.115.45_48562 wolf_ebus PUBLISH wolf_ebus/broadcast/betrd:{
     "betrd_status": {"value": 0},
     "zustand": {"value": "00"},
     "stellgrad": {"value": null},
     "kesseltemp": {"value": 24.0},
     "ruecklauftemp": {"value": 23},
     "boilertemp": {"value": 48},
     "aussentemp": {"value": 20}}
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000wolf_ebus\000wolf_ebus/broadcast/betrd\000{\n     "betrd_status": {"value": 0},\n     "zustand": {"value": "00"},\n     "stellgrad": {"value": null},\n     "kesseltemp": {"value": 24.0},\n     "ruecklauftemp": {"value": 23},\n     "boilertemp": {"value": 48},\n     "aussentemp": {"value": 20}}
2019.10.12 15:24:13 5: PUBLISH: 0(30)(0)(23)wolf_ebus/global/uptime23279
2019.10.12 15:24:13 4: MyBroker_192.168.115.45_48562 wolf_ebus PUBLISH wolf_ebus/global/uptime:23279
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000wolf_ebus\000wolf_ebus/global/uptime\00023279
2019.10.12 15:24:13 5: PUBLISH: 0(142)(1)(0)(28)wolf_ebus/broadcast/datetime{(10)     "outsidetemp": {"value": null},(10)     "time": {"value": "15:27:10"},(10)     "date": {"value": "12.10.2019"}}
2019.10.12 15:24:13 4: MyBroker_192.168.115.45_48562 wolf_ebus PUBLISH wolf_ebus/broadcast/datetime:{
     "outsidetemp": {"value": null},
     "time": {"value": "15:27:10"},
     "date": {"value": "12.10.2019"}}
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000wolf_ebus\000wolf_ebus/broadcast/datetime\000{\n     "outsidetemp": {"value": null},\n     "time": {"value": "15:27:10"},\n     "date": {"value": "12.10.2019"}}
2019.10.12 15:24:13 5: PUBLISH: 0(30)(0)(23)wolf_ebus/global/uptime23295
2019.10.12 15:24:13 4: MyBroker_192.168.115.45_48562 wolf_ebus PUBLISH wolf_ebus/global/uptime:23295
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000wolf_ebus\000wolf_ebus/global/uptime\00023295
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000ESPClient_5C_CF_7F_80_58_E2_156\000/Kellersensor/status/LWT\000Connection Lost
2019.10.12 15:24:13 4: Connection closed for MyBroker_192.168.115.55_49354: EOF
2019.10.12 15:24:13 5: CONNECT: (16) (0)(4)MQTT(4)(2)(0)(10)(0)(20)ESP_Dachboden-Import
2019.10.12 15:24:13 4: MyBroker_192.168.115.215_49157 ESP_Dachboden-Import CONNECT V:4 keepAlive:10
2019.10.12 15:24:13 4: Connection accepted from MyBroker_192.168.115.58_49349
2019.10.12 15:24:13 4: Connection accepted from MyBroker_192.168.115.214_49158
2019.10.12 15:24:13 5: MyBroker: dispatch autocreate=no\000wolf_ebus\000wolf_ebus/global/running\000false
2019.10.12 15:24:14 4: Connection closed for MyBroker_192.168.115.45_48562: EOF
2019.10.12 15:24:14 5: CONNECT: (16)Y(0)(4)MQTT(4)(230)(0)(10)(0)(29)ESPClient_2C:3A:E8:2E:A0:91_4(0)(25)/Sonoff_Basic2/status/LWT(0)(15)Connection Lost(0)(0)(0)(0)
2019.10.12 15:24:14 4: MyBroker_192.168.115.58_49349 ESPClient_2C:3A:E8:2E:A0:91_4 CONNECT V:4 keepAlive:10 LWT:/Sonoff_Basic2/status/LWT:Connection Lost usr:
2019.10.12 15:24:14 4: Connection closed for MyBroker_192.168.115.215_49157: EOF
2019.10.12 15:24:14 4: Connection accepted from MyBroker_192.168.115.213_49156
2019.10.12 15:24:14 5: MyBroker: dispatch autocreate=no\000ESPClient_2C_3A_E8_2E_A0_91_4\000/Sonoff_Basic2/status/LWT\000Connection Lost
2019.10.12 15:24:14 4: Connection closed for MyBroker_192.168.115.58_49349: EOF
2019.10.12 15:24:14 5: CONNECT: (16)U(0)(4)MQTT(4)(230)(0)(10)(0)(27)ESPClient_2C:3A:E8:2E:A0:8E(0)(23)/ESP_Klingel/status/LWT(0)(15)Connection Lost(0)(0)(0)(0)
2019.10.12 15:24:14 4: MyBroker_192.168.115.214_49158 ESPClient_2C:3A:E8:2E:A0:8E CONNECT V:4 keepAlive:10 LWT:/ESP_Klingel/status/LWT:Connection Lost usr:
2019.10.12 15:24:14 5: MyBroker: dispatch autocreate=no\000ESPClient_2C_3A_E8_2E_A0_8E\000/ESP_Klingel/status/LWT\000Connection Lost
2019.10.12 15:24:14 4: Connection closed for MyBroker_192.168.115.214_49158: EOF
2019.10.12 15:24:14 5: CONNECT: (16)V(0)(4)MQTT(4)(230)(0)(10)(0)(27)ESPClient_60:01:94:07:A1:AA(0)(24)/ESP_Hoflicht/status/LWT(0)(15)Connection Lost(0)(0)(0)(0)
2019.10.12 15:24:14 4: MyBroker_192.168.115.213_49156 ESPClient_60:01:94:07:A1:AA CONNECT V:4 keepAlive:10 LWT:/ESP_Hoflicht/status/LWT:Connection Lost usr:
2019.10.12 15:24:14 4: Connection accepted from MyBroker_192.168.115.222_27900
2019.10.12 15:24:14 4: Connection accepted from MyBroker_192.168.115.54_63027
2019.10.12 15:24:14 5: MyBroker: dispatch autocreate=no\000ESPClient_60_01_94_07_A1_AA\000/ESP_Hoflicht/status/LWT\000Connection Lost
2019.10.12 15:24:14 4: Connection closed for MyBroker_192.168.115.213_49156: EOF
2019.10.12 15:24:15 5: CONNECT: (16)K(0)(4)MQTT(4)(238)(0)(15)(0)(11)DVES_E772DA(0)(19)tele/sonoffpow2/LWT(0)(7)offline(0)(9)DVES_USER(0)(9)DVES_PASS
2019.10.12 15:24:15 4: MyBroker_192.168.115.222_27900 DVES_E772DA CONNECT V:4 keepAlive:15 LWT:tele/sonoffpow2/LWT:offline usr:DVES_USER


Als Ergänzung noch ein List vom Broker und dem MQTT-Device

Code Auswählen Erweitern

Internals:
   CONNECTS   4112
   DEF        1884  192.168.115.88
   FD         14
   FUUID      5d4d7731-f33f-f73e-d44f-00b983811fd5a935
   NAME       MyBroker
   NR         133
   PORT       1884
   STATE      Initialized
   TYPE       MQTT2_SERVER
   READINGS:
     2019-10-12 23:17:33   RETAIN          {"/ESP_Dachboden/Schatten/Temperature":"13.9","/ESP_Dachboden/Sonne/Temperature":"13.7","/ESP_Dachboden/bmp/Pressure":"1013.01","/ESP_Dachboden/bmp/Temperature":"17.86","/ESP_Dachboden/status/LWT":"Connected","/ESP_Hoflicht/status/LWT":"Connected","/ESP_Klingel/status/LWT":"Connected","/Kellersensor/status/LWT":"Connected","/Sonoff_Basic2/status/LWT":"Connected","/VentusNdn1/Ventus/":"0","/VentusNdn1/Ventus/Average":"0.7","/VentusNdn1/Ventus/Battery":"0","/VentusNdn1/Ventus/Direction":"135.0","/VentusNdn1/Ventus/Distance":"32","/VentusNdn1/Ventus/Gust":"1.4","/VentusNdn1/Ventus/Humidity":"28","/VentusNdn1/Ventus/Rainpasthour":"5.0","/VentusNdn1/Ventus/Strikecounter":"0","/VentusNdn1/Ventus/Strikespast5":"0","/VentusNdn1/Ventus/Temperature":"8.4","/VentusNdn1/Ventus/Totalrain":"115.0","/VentusNdn1/Ventus/UV":"0.0","/VentusNdn1/status/LWT":"Connection Lost","home/BTGW_Keller/LWT":"online","home/BTGW_Keller/version":"0.9.2beta","tele/gosund2/LWT":"online","tele/sonoffpow1/LWT":"online","tele/sonoffpow2/LWT":"online","wolf_ebus/global/running":"false","wolf_ebus/global/updatecheck":"\u0022revision v3.3-40-gd9d1b9a available, broadcast.csv: different version available\u0022","wolf_ebus/global/version":"\u0022ebusd 3.3.v3.3\u0022"}
     2019-10-12 21:49:09   nrclients       13
     2019-10-06 20:00:02   state           Initialized
   clients:
     MyBroker_192.168.115.213_49166 1
     MyBroker_192.168.115.214_49160 1
     MyBroker_192.168.115.215_49188 1
     MyBroker_192.168.115.215_49190 1
     MyBroker_192.168.115.221_11938 1
     MyBroker_192.168.115.222_17702 1
     MyBroker_192.168.115.41_15263 1
     MyBroker_192.168.115.54_52275 1
     MyBroker_192.168.115.55_49362 1
     MyBroker_192.168.115.58_49361 1
   retain:
     /ESP_Dachboden/Schatten/Temperature:
       ts         1570915052.88664
       val        13.9
     /ESP_Dachboden/Sonne/Temperature:
       ts         1570915053.90434
       val        13.7
     /ESP_Dachboden/bmp/Pressure:
       ts         1570915051.92099
       val        1013.01
     /ESP_Dachboden/bmp/Temperature:
       ts         1570915051.85017
       val        17.86
     /ESP_Dachboden/status/LWT:
       ts         1570892524.27477
       val        Connected
     /ESP_Hoflicht/status/LWT:
       ts         1570886665.08741
       val        Connected
     /ESP_Klingel/status/LWT:
       ts         1570886668.01637
       val        Connected
     /Kellersensor/status/LWT:
       ts         1570886677.96836
       val        Connected
     /Sonoff_Basic2/status/LWT:
       ts         1570909749.83346
       val        Connected
     /VentusNdn1/Ventus/:
       ts         1570384803.06621
       val        0
     /VentusNdn1/Ventus/Average:
       ts         1570384803.06621
       val        0.7
     /VentusNdn1/Ventus/Battery:
       ts         1570384803.06621
       val        0
     /VentusNdn1/Ventus/Direction:
       ts         1570384803.06621
       val        135.0
     /VentusNdn1/Ventus/Distance:
       ts         1570384803.06621
       val        32
     /VentusNdn1/Ventus/Gust:
       ts         1570384803.06621
       val        1.4
     /VentusNdn1/Ventus/Humidity:
       ts         1570384803.06621
       val        28
     /VentusNdn1/Ventus/Rainpasthour:
       ts         1570384803.06621
       val        5.0
     /VentusNdn1/Ventus/Strikecounter:
       ts         1570384803.06621
       val        0
     /VentusNdn1/Ventus/Strikespast5:
       ts         1570384803.06621
       val        0
     /VentusNdn1/Ventus/Temperature:
       ts         1570384803.06621
       val        8.4
     /VentusNdn1/Ventus/Totalrain:
       ts         1570384803.06621
       val        115.0
     /VentusNdn1/Ventus/UV:
       ts         1570384803.06621
       val        0.0
     /VentusNdn1/status/LWT:
       ts         1570384803.06621
       val        Connection Lost
     home/BTGW_Keller/LWT:
       ts         1570886657.00163
       val        online
     home/BTGW_Keller/version:
       ts         1570886657.03364
       val        0.9.2beta
     tele/gosund2/LWT:
       ts         1570901649.32337
       val        online
     tele/sonoffpow1/LWT:
       ts         1570889687.71935
       val        online
     tele/sonoffpow2/LWT:
       ts         1570886658.56578
       val        online
     wolf_ebus/global/running:
       ts         1570886653.99234
       val        false
     wolf_ebus/global/updatecheck:
       ts         1570863433.2509
       val        "revision v3.3-40-gd9d1b9a available, broadcast.csv: different version available"
     wolf_ebus/global/version:
       ts         1570863248.33007
       val        "ebusd 3.3.v3.3"
Attributes:
   autocreate no
   disable    0
   keepaliveFactor 20
   room       MQTT2_DEVICE
   verbose    5

Code Auswählen Erweitern

Internals:
   CID        wolf_ebus
   DEF        wolf_ebus
   DEVICETOPIC MQTT2_ebusd
   FUUID      5d4ac903-f33f-f73e-6602-e92bd994124a2f05
   IODev      MyBroker
   LASTInputDev MyBroker
   MQTT_via_mosquitto_MSGCNT 27
   MQTT_via_mosquitto_TIME 2019-10-12 00:02:44
   MQTT_via_old_MSGCNT 66313
   MQTT_via_old_TIME 2019-10-12 00:02:48
   MSGCNT     86884
   MyBroker_MSGCNT 20544
   MyBroker_TIME 2019-10-12 15:24:14
   NAME       MQTT2_ebusd
   NR         132
   STATE      get_ebus_hg01r
   TYPE       MQTT2_DEVICE
   Helper:
     DBLOG:
       aussent_c:
         logdb:
           TIME       1570886654.0237
           VALUE      20.9
       aussent_gem_c:
         logdb:
           TIME       1570886654.0237
           VALUE      17.1
       performance_burner_0_value:
         logdb:
           TIME       1570877746.61346
           VALUE      0
       performance_pump_0_value:
         logdb:
           TIME       1570877626.53276
           VALUE      65
       raumtemp_0_value:
         logdb:
           TIME       1570886352.64191
           VALUE      23.6
       ruecklauf_ist_ruecklauf_ist_value:
         logdb:
           TIME       1570885736.86844
           VALUE      24.1
       vorlauf_ist_vorlauf_ist_value:
         logdb:
           TIME       1570885317.30335
           VALUE      24.6
       vorlauf_soll_vorlauf_soll_value:
         logdb:
           TIME       1570877215.7565
           VALUE      65.0
       warmwasser_ist_warmwasser_ist_value:
         logdb:
           TIME       1570883996.78462
           VALUE      48.9
   READINGS:
     2019-08-07 15:08:58   associatedWith  MQTT2_ebusd_3.3_441
     2019-10-12 15:24:14   aussent_c       20.9
     2019-10-12 15:24:14   aussent_gem_c   17.1
     2019-10-12 15:24:08   aussentemperatur_Aussentemperatur_value 20.9
     2019-10-12 15:19:12   aussentemperatur_gem_Aussentemperatur_gemittelt_value 17.1
     2019-10-12 15:24:13   betrd_aussentemp_value 20
     2019-10-12 15:24:13   betrd_betrd_status_value 0
     2019-10-12 15:24:13   betrd_boilertemp_value 48
     2019-10-12 15:24:13   betrd_kesseltemp_value 24.0
     2019-10-12 15:24:13   betrd_ruecklauftemp_value 23
     2019-10-12 15:24:13   betrd_zustand_value 00
     2019-10-12 12:56:01   bm2_aktion_value Verbraucheraus
     2019-10-12 12:56:01   bm2_bm2_status_value Brauchwasser
     2019-10-12 12:56:01   bm2_brauchwassersolltemp_value 50.0
     2019-10-12 12:56:01   bm2_brennstoff_value dc
     2019-10-12 12:56:01   bm2_kesselsolltemp_value 5.00
     2019-10-12 15:24:13   datetime_date_value 12.10.2019
     2019-10-12 15:24:13   datetime_time_value 15:27:10
     2019-10-12 15:11:57   error_error_value E000 15:17
     2019-10-12 08:54:11   fw_version_burner_0_name
     2019-10-12 08:54:11   fw_version_burner_0_value 2.00
     2019-10-12 00:02:47   hg01_hysterese_vorlauf_value 16.0
     2019-08-31 23:50:55   hg02_gebl_unten_value 25
     2019-08-31 23:50:55   hg03_gebl_oben_ww_value 100
     2019-08-31 23:50:56   hg04_gebl_oben_hz_value 75
     2019-08-31 23:50:56   hg07_pumpen_nachlauf_value 12
     2019-08-31 23:50:56   hg08_max_vorlauf_temp_value 75.0
     2019-08-31 23:50:56   hg09_taktsperre_value 10
     2019-08-31 23:50:56   hg15_hysterese_speicher_value 2.5
     2019-08-31 23:50:57   hg16_pumpenleistung_hk_min_value 65
     2019-08-31 23:50:57   hg17_pumpenleistung_hk_max_value 100
     2019-08-31 23:50:57   hg21_kessel_min_value 20.0
     2019-10-12 00:02:47   hg75_ww_durchsatz_value 0
     2019-10-12 10:24:59   hg90_betriebsstunden_brenner_value 3391
     2019-10-12 10:43:54   hg91_brennerstarts_value 16053
     2019-10-12 14:33:57   hg9x_betriebsstunden_netz_value 14235
     2019-10-12 08:55:11   ident_hardware_value 8080
     2019-10-12 08:55:11   ident_id_value   
     2019-10-12 08:55:11   ident_manufacturer_value Kromschröder
     2019-10-12 08:55:11   ident_software_value 0204
     2019-10-12 12:53:46   ionisation_0_name
     2019-10-12 12:53:46   ionisation_0_value 53
     2019-10-12 11:18:00   no_of_firing_0_name
     2019-10-12 11:18:00   no_of_firing_0_value 16054
     2019-10-12 00:02:46   no_of_power_on_0_name
     2019-10-12 00:02:46   no_of_power_on_0_value 56
     2019-10-12 10:25:09   op_hrs_heating_0_name
     2019-10-12 10:25:09   op_hrs_heating_0_value 3391
     2019-10-12 12:29:00   op_hrs_supply_0_name
     2019-10-12 12:29:00   op_hrs_supply_0_value 14233
     2019-10-12 12:55:46   performance_burner_0_name
     2019-10-12 12:55:46   performance_burner_0_value 0
     2019-10-12 12:53:46   performance_pump_0_name
     2019-10-12 12:53:46   performance_pump_0_value 65
     2019-10-12 14:30:37   pressure_0_name
     2019-10-12 14:30:37   pressure_0_value 1.95
     2019-10-12 15:19:12   raumtemp_0_name
     2019-10-12 15:19:12   raumtemp_0_value 23.6
     2019-10-12 15:08:56   ruecklauf_ist_ruecklauf_ist_value 24.1
     2019-10-12 15:24:14   running         false
     2019-09-27 09:09:58   scan.08_HW_value 0000
     2019-09-27 09:09:58   scan.08_ID_value !
     2019-09-27 09:09:58   scan.08_MF_value Wolf
     2019-09-27 09:09:58   scan.08_SW_value 0002
     2019-08-29 15:41:00   scan.35_HW_value 0100
     2019-08-29 15:41:00   scan.35_ID_value
     2019-08-29 15:41:00   scan.35_MF_value Wolf
     2019-08-29 15:41:00   scan.35_SW_value 0204
     2019-09-23 07:03:46   scan.50_HW_value 0000
     2019-09-23 07:03:46   scan.50_ID_value !
     2019-09-23 07:03:46   scan.50_MF_value Wolf
     2019-09-23 07:03:46   scan.50_SW_value 0002
     2019-10-12 08:55:11   scan.76_HW_value 8080
     2019-10-12 08:55:11   scan.76_ID_value   
     2019-10-12 08:55:11   scan.76_MF_value Kromschroeder
     2019-10-12 08:55:11   scan.76_SW_value 0204
     2019-10-12 08:54:08   signal          true
     2019-10-12 15:14:32   sollw_aussentemp_value 17.000
     2019-10-12 15:14:32   sollw_brauchwassersolltemp_value 50.000
     2019-10-12 15:14:32   sollw_kesselsolltemp_value 5.000
     2019-10-12 15:14:32   sollw_leistungszwang_value 0
     2019-10-12 15:14:32   sollw_sollw_status_value 00
     2019-10-03 11:20:47   state           get_ebus_hg01r
     2019-10-12 00:02:46   tagtemp_0_name 
     2019-10-12 00:02:46   tagtemp_0_value 23.0
     2019-10-12 15:17:56   temp_burner_0_name
     2019-10-12 15:17:56   temp_burner_0_value 24.2
     2019-10-12 14:36:22   temp_exhaust_0_name
     2019-10-12 14:36:22   temp_exhaust_0_value 26.0
     2019-10-12 15:24:13   temp_return_0_name
     2019-10-12 15:24:13   temp_return_0_value 23.9
     2019-10-12 12:55:51   uflags4_0_name 
     2019-10-12 12:55:51   uflags4_0_value 0
     2019-10-12 12:59:00   uflags5_0_name 
     2019-10-12 12:59:00   uflags5_0_value 13
     2019-10-12 08:57:13   updatecheck     "revision v3.3-40-gd9d1b9a available, broadcast.csv: different version available"
     2019-10-12 15:24:13   uptime          23295
     2019-10-12 08:54:08   version         "ebusd 3.3.v3.3"
     2019-10-12 15:01:57   vorlauf_ist_vorlauf_ist_value 24.6
     2019-10-12 12:46:55   vorlauf_soll_vorlauf_soll_value 65.0
     2019-10-12 14:39:56   warmwasser_ist_warmwasser_ist_value 48.9
     2019-10-12 00:02:47   warmwasser_soll_warmwasser_soll_value 50.0
Attributes:
   DbLogInclude vorlauf_ist_vorlauf_ist_value,vorlauf_soll_vorlauf_soll_value,ruecklauf_ist_ruecklauf_ist_value,aussent_c,aussent_gem_c,raumtemp_0_value,performance_pump_0_value,performance_burner_0_value,warmwasser_ist_warmwasser_ist_value
   IODev      MyBroker
   autocreate 0
   disable    0
   readingList wolf_ebus/broadcast/datetime:.* { json2nameValue($EVENT, 'datetime_', $JSONMAP) }
wolf_ebus/broadcast/betrd:.* { json2nameValue($EVENT, 'betrd_', $JSONMAP) }
wolf_ebus/global/uptime:.* uptime
wolf_ebus/broadcast/sollw:.* { json2nameValue($EVENT, 'sollw_', $JSONMAP) }
wolf_ebus/broadcast/ident:.* { json2nameValue($EVENT, 'ident_', $JSONMAP) }
wolf_ebus/scan\.08/:.* { json2nameValue($EVENT, 'scan.08_', $JSONMAP) }
wolf_ebus/scan\.76/:.* { json2nameValue($EVENT, 'scan.76_', $JSONMAP) }
wolf_ebus/global/running:.* running
wolf_ebus/global/signal:.* signal
wolf_ebus/global/version:.* version
wolf_ebus/broadcast/error:.* { json2nameValue($EVENT, 'error_', $JSONMAP) }
wolf_ebus/global/updatecheck:.* updatecheck
wolf_ebus/betrd_bm2/aussentemperatur_gem:.* { json2nameValue($EVENT, 'aussentemperatur_gem_', $JSONMAP) }
wolf_ebus/betrd_bm2/raumtemp:.* { json2nameValue($EVENT, 'raumtemp_', $JSONMAP) }
wolf_ebus/betrd_bm2/tagtemp:.* { json2nameValue($EVENT, 'tagtemp_', $JSONMAP) }
wolf_ebus/betrd_bm2/bm2:.* { json2nameValue($EVENT, 'bm2_', $JSONMAP) }
wolf_ebus/scan\.50/:.* { json2nameValue($EVENT, 'scan.50_', $JSONMAP) }
wolf_ebus/betrd_bm2/temp_burner:.* { json2nameValue($EVENT, 'temp_burner_', $JSONMAP) }
wolf_ebus/betrd_bm2/temp_return:.* { json2nameValue($EVENT, 'temp_return_', $JSONMAP) }
wolf_ebus/betrd_bm2/performance_burner:.* { json2nameValue($EVENT, 'performance_burner_', $JSONMAP) }
wolf_ebus/betrd_bm2/fw_version_burner:.* { json2nameValue($EVENT, 'fw_version_burner_', $JSONMAP) }
wolf_ebus/betrd_bm2/pressure:.* { json2nameValue($EVENT, 'pressure_', $JSONMAP) }
wolf_ebus/betrd_bm2/no_of_firing:.* { json2nameValue($EVENT, 'no_of_firing_', $JSONMAP) }
wolf_ebus/betrd_bm2/op_hrs_supply:.* { json2nameValue($EVENT, 'op_hrs_supply_', $JSONMAP) }
wolf_ebus/betrd_bm2/op_hrs_heating:.* { json2nameValue($EVENT, 'op_hrs_heating_', $JSONMAP) }
wolf_ebus/betrd_bm2/uflags5:.* { json2nameValue($EVENT, 'uflags5_', $JSONMAP) }
wolf_ebus/betrd_bm2/uflags4:.* { json2nameValue($EVENT, 'uflags4_', $JSONMAP) }
wolf_ebus/feuerung/warmwasser_ist:.* { json2nameValue($EVENT, 'warmwasser_ist_', $JSONMAP) }
wolf_ebus/betrd_bm2/temp_exhaust:.* { json2nameValue($EVENT, 'temp_exhaust_', $JSONMAP) }
wolf_ebus/betrd_bm2/ionisation:.* { json2nameValue($EVENT, 'ionisation_', $JSONMAP) }
wolf_ebus/betrd_bm2/performance_pump:.* { json2nameValue($EVENT, 'performance_pump_', $JSONMAP) }
wolf_ebus/betrd_bm2/no_of_power_on:.* { json2nameValue($EVENT, 'no_of_power_on_', $JSONMAP) }
wolf_ebus/feuerung/ruecklauf_ist:.* { json2nameValue($EVENT, 'ruecklauf_ist_', $JSONMAP) }
wolf_ebus/feuerung/vorlauf_ist:.* { json2nameValue($EVENT, 'vorlauf_ist_', $JSONMAP) }
wolf_ebus/feuerung/hg75:.* { json2nameValue($EVENT, 'hg75_', $JSONMAP) }
wolf_ebus/feuerung/aussentemperatur:.* { json2nameValue($EVENT, 'aussentemperatur_', $JSONMAP) }
wolf_ebus/feuerung/hg9x:.* { json2nameValue($EVENT, 'hg9x_', $JSONMAP) }
wolf_ebus/feuerung/hg91:.* { json2nameValue($EVENT, 'hg91_', $JSONMAP) }
wolf_ebus/feuerung/vorlauf_soll:.* { json2nameValue($EVENT, 'vorlauf_soll_', $JSONMAP) }
wolf_ebus/feuerung/hg90:.* { json2nameValue($EVENT, 'hg90_', $JSONMAP) }
wolf_ebus/feuerung/warmwasser_soll:.* { json2nameValue($EVENT, 'warmwasser_soll_', $JSONMAP) }
wolf_ebus/feuerung/hg01:.* { json2nameValue($EVENT, 'hg01_', $JSONMAP) }
ebusd:wolf_ebus/scan\.35/:.* { json2nameValue($EVENT, 'scan.35_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg02:.* { json2nameValue($EVENT, 'hg02_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg03:.* { json2nameValue($EVENT, 'hg03_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg04:.* { json2nameValue($EVENT, 'hg04_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg07:.* { json2nameValue($EVENT, 'hg07_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg08:.* { json2nameValue($EVENT, 'hg08_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg09:.* { json2nameValue($EVENT, 'hg09_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg15:.* { json2nameValue($EVENT, 'hg15_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg16:.* { json2nameValue($EVENT, 'hg16_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg17:.* { json2nameValue($EVENT, 'hg17_', $JSONMAP) }
wolf_ebus:wolf_ebus/feuerung/hg21:.* { json2nameValue($EVENT, 'hg21_', $JSONMAP) }
   room       Heizung->Devices,MQTT2_DEVICE
   setList    get_ebus_hg01r wolf_ebus/feuerung/hg01/get get
get_ebus_hg02r wolf_ebus/feuerung/hg02/get get
get_ebus_hg03r wolf_ebus/feuerung/hg03/get get
get_ebus_hg04r wolf_ebus/feuerung/hg04/get get
get_ebus_hg07r wolf_ebus/feuerung/hg07/get get
get_ebus_hg08r wolf_ebus/feuerung/hg08/get get
get_ebus_hg09r wolf_ebus/feuerung/hg09/get get
get_ebus_hg15r wolf_ebus/feuerung/hg15/get get
get_ebus_hg16r wolf_ebus/feuerung/hg16/get get
get_ebus_hg17r wolf_ebus/feuerung/hg17/get get
get_ebus_hg21r wolf_ebus/feuerung/hg21/get get
get_no_of_power_on wolf_ebus/betrd_bm2/no_of_power_on/get get
get_warmwasser_soll wolf_ebus/feuerung/warmwasser_soll/get get
   userReadings aussent_gem_c {if(ReadingsVal($name,"aussentemperatur_gem_Aussentemperatur_gemittelt_value","") > 3276)
{((ReadingsVal($name,"aussentemperatur_gem_Aussentemperatur_gemittelt_value","")*10) - 65535)/10}
else {ReadingsVal($name,"aussentemperatur_gem_Aussentemperatur_gemittelt_value","")}
}, aussent_c {if(ReadingsVal($name,"aussentemperatur_Aussentemperatur_value","") > 3276)
{((ReadingsVal($name,"aussentemperatur_Aussentemperatur_value","")*10) - 65535)/10}
else {ReadingsVal($name,"aussentemperatur_Aussentemperatur_value","")}
}

Im Keller werkelt ein Rpi Zerro W, an den der Adapter über USB angeschlossen ist.

Wenn noch Infos zur Lösung des Problems benötigt werden bitte sagen.

LG
Manfred

[goosst]

Hello

A few questions with soldering v2.2

1)
The partlist here, mentions two capacitors of 2.2 uF: https://ebus.github.io/adapter/partlist.en
The partlist in the reichelt basket only has two capacitors of 1.0 uF https://www.reichelt.de/?ACTION=20&AWKID=1518848

I assume it's ok to use the 1.0uF where the 2.2uF should be?

2) Mainly a remark:
Here the picture has a blue and yellow capacitor: https://ebus.github.io/adapter/images/base-final-v21.jpg
When if it comes with the reichelt components, the blue one should be where the yellow one is. It might be good to also add a picture for the 2.2 version.

Because I was confused with the capacitor values, I was following the picture on the site. Hence I had to start desoldering these capacitors and most likely already damaged the board / components ... .

[john30]

1)
The partlist here, mentions two capacitors of 2.2 uF: https://ebus.github.io/adapter/partlist.en
The partlist in the reichelt basket only has two capacitors of 1.0 uF https://www.reichelt.de/?ACTION=20&AWKID=1518848

I assume it's ok to use the 1.0uF where the 2.2uF should be?

yes, 1 uF is the one to pick for C3+4. Just added a hint to the partlist.

2) Mainly a remark:
Here the picture has a blue and yellow capacitor: https://ebus.github.io/adapter/images/base-final-v21.jpg
When if it comes with the reichelt components, the blue one should be where the yellow one is. It might be good to also add a picture for the 2.2 version.
Because I was confused with the capacitor values, I was following the picture on the site. Hence I had to start desoldering these capacitors and most likely already damaged the board / components ... .

just never follow a picture

[john30]

Wie geh ich der Sache auf den Grund ?

könntest du mit dem aktuellen git code nochmal versuchen bitte?

[goosst]

yes, 1 uF is the one to pick for C3+4. Just added a hint to the partlist.
just never follow a picture

Thanks .

I have issues if I make the following connection: base board - uart cp210- usb cable - raspberry pi 3b. If I connect this directly to a laptop instead of the raspberry pi everything works fine. The powersupply from the pi should have enough capacity (3A).
Even the led between the 5V and GND on the uart converter doesn't turn on when plugged in the pi (identical converter as this one in the middle https://ebus.github.io/adapter/images/uarts.jpg)

Looking at the amp requirement mentioned on the ebus website, it mentions 1-2 A. Which probably is something the pi cannot reliably provide on its usb-ports (although I read a bit of conflicting documentation). from the raspberry website:

While it is possible to plug a 500mA device into a Pi and have it work with a sufficiently powerful supply, reliable operation is not guaranteed.

So the questions:
- Is there any harm in directly wiring everything to the pins of the PI and skip the uart converter: I guess I need 5V, GND, RX, TX, and don't need the DTR pin?
- Does this still allow to use the ebusd -f --scanconfig commands in debian/raspbian or does it require adapting to a new way of programming?

Thanks!

[john30]

I have issues if I make the following connection: base board - uart cp210- usb cable - raspberry pi 3b. If I connect this directly to a laptop instead of the raspberry pi everything works fine. The powersupply from the pi should have enough capacity (3A).
Even the led between the 5V and GND on the uart converter doesn't turn on when plugged in the pi (identical converter as this one in the middle https://ebus.github.io/adapter/images/uarts.jpg)

are you sure that you have used the right socket on the base board (as there are three of them)? please check this first.

Looking at the amp requirement mentioned on the ebus website, it mentions 1-2 A. Which probably is something the pi cannot reliably provide on its usb-ports (although I read a bit of conflicting documentation). from the raspberry website:So the questions:

it certainly does not have anything to do with the power supplied by RPi through USB, only if your USB connection is bad which I doubt.

- Is there any harm in directly wiring everything to the pins of the PI and skip the uart converter: I guess I need 5V, GND, RX, TX, and don't need the DTR pin?

you definitely also need the 3V connection. Otherwise the adapter won't work. So you need 5 PINs connected.

- Does this still allow to use the ebusd -f --scanconfig commands in debian/raspbian or does it require adapting to a new way of programming?

this is completely independant.
Thanks!
[/quote]

[goosst]

are you sure that you have used the right socket on the base board (as there are three of them)? please check this first.

I'm pretty sure it's the right place, but here is a picture: http://users.telenet.be/goosst/ebusadapter.jpeg

it certainly does not have anything to do with the power supplied by RPi through USB, only if your USB connection is bad which I doubt.

I've tried the following setups:
- a raspberry pi running hassbian
- tinkerboard running armbian using a different powersupply and usb-cable
- old laptop running a debian variant

only the third setup works fine and I can read and write to the heater. First and second don't work, I cannot get my head around it beside something being wrong with the voltage level.
Both give an output similar to the one pasted below, on top the following is visible with the hardware:
-  the red led and a red uart led keep being turned on instead of blinking
- the red led between 0 and 5V on the uart chip goes out (the one turned on in the picture above)

Code Auswählen Erweitern


ebusd -f --scanconfig
2019-10-22 18:20:43.890 [main notice] ebusd 3.3.v3.3 started with auto scan
2019-10-22 18:20:44.229 [bus notice] bus started with own address 31/36
2019-10-22 18:20:44.243 [bus notice] signal acquired
2019-10-22 18:20:48.114 [bus notice] new master 10, master count 2
2019-10-22 18:20:48.143 [bus notice] new master 03, master count 3
2019-10-22 18:20:48.143 [update notice] received unknown MS cmd: 1008b5100900004dffffff04ff00 / 0101
2019-10-22 18:20:52.128 [update notice] received unknown MS cmd: 1008b5110101 / 0943430080575d0000ff
2019-10-22 18:20:54.367 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2019-10-22 18:20:54.367 [update notice] store 08 ident: done
2019-10-22 18:20:54.367 [update notice] sent scan-read scan.08  QQ=31: Vaillant;BAI00;0202;9602
2019-10-22 18:20:54.367 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2019-10-22 18:20:54.698 [main notice] read common config file vaillant/scan.csv
2019-10-22 18:20:54.777 [main notice] read common config file vaillant/general.csv
2019-10-22 18:20:54.855 [main notice] read common config file vaillant/broadcast.csv
2019-10-22 18:20:54.937 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0202, HW9602
2019-10-22 18:20:54.986 [bus error] send to 08: ERR: read timeout, retry
2019-10-22 18:20:54.987 [bus notice] device invalid
2019-10-22 18:20:59.987 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2019-10-22 18:20:59.987 [bus error] signal lost
2019-10-22 18:20:59.987 [bus error] send to 08: ERR: no signal, give up
2019-10-22 18:20:59.987 [bus error] send message part 0: ERR: no signal
2019-10-22 18:20:59.987 [bus notice] device invalid
2019-10-22 18:20:59.988 [main error] error reading message scan.08 id: ERR: no signal
2019-10-22 18:21:04.988 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2019-10-22 18:21:04.988 [bus notice] device invalid
2019-10-22 18:21:04.988 [bus error] send to 08: ERR: no signal, give up
2019-10-22 18:21:04.988 [bus error] send message part 0: ERR: no signal
2019-10-22 18:21:04.988 [main error] error reading message scan.08 id: ERR: no signal
2019-10-22 18:21:09.989 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2019-10-22 18:21:09.989 [bus notice] device invalid
2019-10-22 18:21:09.989 [bus error] send to 08: ERR: no signal, give up
2019-10-22 18:21:09.989 [bus error] send message part 0: ERR: no signal
2019-10-22 18:21:09.989 [main error] error reading message scan.08 id: ERR: no signal
2019-10-22 18:21:14.989 [bus error] unable to open /dev/ttyUSB0: ERR: element not found
2019-10-22 18:21:14.989 [bus notice] device invalid
2019-10-22 18:21:14.990 [bus error] send to 08: ERR: no signal, give up


you definitely also need the 3V connection. Otherwise the adapter won't work. So you need 5 PINs connected.
this is completely independant.
Thanks!

Thanks for all the support

[TomLee]

könntest du mit dem aktuellen git code nochmal versuchen bitte?

Sry, hab den Beitrag überlesen.

Würd ich gerne, aber keine Nerven dazu mich aktuell damit zu beschäftigen, das nehm ich mir im Winter (Dez/Jan) vor.

1-2 Tage nach meiner Frage hier hab ich mein Test-Fhem gestoppt (andere Gründe) seit dem gibt es keinen Verbindungsabbruch mehr. Meine Vermutung der dort definierte MQTT2_CLIENT.

Gruß

Thomas

[john30]

I'm pretty sure it's the right place, but here is a picture: http://users.telenet.be/goosst/ebusadapter.jpeg

yes looks good.

Both give an output similar to the one pasted below, on top the following is visible with the hardware:
-  the red led and a red uart led keep being turned on instead of blinking
- the red led between 0 and 5V on the uart chip goes out (the one turned on in the picture above)

did you use the right USB tty on the ebusd start parameters with each of the non-functioning setups?
and doy ou have any other tool active (such as fhem) that might use the USB tty?

[goosst]

yes looks good.
did you use the right USB tty on the ebusd start parameters with each of the non-functioning setups?
and doy ou have any other tool active (such as fhem) that might use the USB tty?

So I've checked all of that.
The only thing the two non-functioning setups had in common was the power socket. Plugged it in a different socket and now I'm  reading messages for 10 minutes without any error popping up  . That has cost me quite a bit of time and frustration to figure that out  .

Thanks again!

[goosst]

These base boards over usb with a single board computer are so unreliable I'm just going to give up on them. it works fine for a period of time, then it stops again, ... I just cannot put this on a heating system.

Code Auswählen Erweitern

ebusd -f --scanconfig
2019-10-30 22:36:09.771 [main notice] ebusd 3.3.v3.3 started with auto scan
2019-10-30 22:36:10.096 [bus notice] bus started with own address 31/36
2019-10-30 22:36:10.123 [bus notice] signal acquired
2019-10-30 22:36:10.371 [bus notice] new master 03, master count 2
2019-10-30 22:36:17.006 [bus notice] new master 10, master count 3
2019-10-30 22:36:17.006 [update notice] received unknown BC cmd: 10feb516080043352330100319
2019-10-30 22:36:17.275 [update notice] received unknown MS cmd: 1008b5110101 / 09615b008057640100ff
2019-10-30 22:36:20.247 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2019-10-30 22:36:20.247 [update notice] store 08 ident: done
2019-10-30 22:36:20.248 [update notice] sent scan-read scan.08  QQ=31: Vaillant;BAI00;0202;9602
2019-10-30 22:36:20.248 [bus notice] scan 08: ;Vaillant;BAI00;0202;9602
2019-10-30 22:36:20.596 [main notice] read common config file vaillant/scan.csv
2019-10-30 22:36:20.676 [main notice] read common config file vaillant/general.csv
2019-10-30 22:36:20.754 [main notice] read common config file vaillant/broadcast.csv
2019-10-30 22:36:20.843 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0202, HW9602
2019-10-30 22:36:20.989 [update notice] sent scan-read scan.08 id QQ=31:
2019-10-30 22:36:21.166 [bus notice] device invalid
2019-10-30 22:36:26.177 [bus notice] re-opened /dev/ttyUSB0
2019-10-30 22:36:26.204 [bus error] signal lost
2019-10-30 22:36:26.205 [bus error] send to 08: ERR: no signal, give up
2019-10-30 22:36:26.205 [bus error] send message part 1: ERR: no signal
2019-10-30 22:36:26.205 [main error] error reading message scan.08 id: ERR: no signal
2019-10-30 22:36:26.227 [bus notice] signal acquired
2019-10-30 22:36:26.436 [update notice] sent scan-read scan.08 id QQ=31:
2019-10-30 22:36:27.326 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:27.539 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:27.623 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:27.689 [bus error] send to 08: ERR: wrong symbol received
2019-10-30 22:36:27.689 [bus error] send message part 1: ERR: wrong symbol received
2019-10-30 22:36:27.689 [main error] error reading message scan.08 id: ERR: wrong symbol received
2019-10-30 22:36:27.746 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:29.001 [bus notice] max. symbols per second: 368
2019-10-30 22:36:31.926 [bus error] own master address 31 is used by another participant
2019-10-30 22:36:32.045 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:32.086 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:36.250 [bus error] send to 08: ERR: wrong symbol received
2019-10-30 22:36:36.250 [bus error] send message part 0: ERR: wrong symbol received
2019-10-30 22:36:36.250 [main error] error reading message scan.08 id: ERR: wrong symbol received
2019-10-30 22:36:36.294 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:36.360 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:36.412 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:36.452 [bus error] send to 08: ERR: wrong symbol received
2019-10-30 22:36:36.452 [bus error] send message part 0: ERR: wrong symbol received
2019-10-30 22:36:36.452 [main error] error reading message scan.08 id: ERR: wrong symbol received
2019-10-30 22:36:44.866 [bus error] send to 08: ERR: arbitration lost, retry
2019-10-30 22:36:44.917 [update notice] received unknown MS cmd: 1008b5110101 / 096a63008056630100ff
2019-10-30 22:36:45.123 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:49.453 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:36:53.780 [bus error] send to 08: ERR: wrong symbol received
2019-10-30 22:36:53.780 [bus error] send message part 0: ERR: wrong symbol received
2019-10-30 22:36:53.780 [main error] error reading message scan.08 id: ERR: wrong symbol received
2019-10-30 22:36:58.088 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:37:06.468 [bus error] send to 08: ERR: arbitration lost, retry
2019-10-30 22:37:06.717 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:37:10.994 [bus error] send to 08: ERR: wrong symbol received
2019-10-30 22:37:10.994 [bus error] send message part 0: ERR: wrong symbol received
2019-10-30 22:37:10.994 [main error] error reading message scan.08 id: ERR: wrong symbol received
2019-10-30 22:37:11.051 [bus error] send to 08: ERR: wrong symbol received, retry
2019-10-30 22:37:15.331 [bus error] send to 08: ERR: wrong symbol received, retry
^C2019-10-30 22:37:15.382 [main notice] SIGINT received
^C2019-10-30 22:37:16.107 [main notice] SIGINT received
^C2019-10-30 22:37:16.336 [main notice] SIGINT received
^C2019-10-30 22:37:16.550 [main notice] SIGINT received
^C2019-10-30 22:37:16.746 [main notice] SIGINT received
^C2019-10-30 22:37:16.956 [main notice] SIGINT received
^C2019-10-30 22:37:17.153 [main notice] SIGINT received


[john30]

These base boards over usb with a single board computer are so unreliable I'm just going to give up on them. it works fine for a period of time, then it stops again, ... I just cannot put this on a heating system.

do you mean the UART? which one are you using?

[goosst]

the setup was:
power supply + powerbank - raspberry pi or tinkerboard - uart using cp210 - base board.
It worked sometimes, but after a period of time it started to behave like disco lights where very repetitively all leds on the base board turn off for a moment (for about a second or so) before starting to blink at the normal high frequency again.

[john30]

power supply + powerbank - raspberry pi or tinkerboard - uart using cp210 - base board.
It worked sometimes, but after a period of time it started to behave like disco lights where very repetitively all leds on the base board turn off for a moment (for about a second or so) before starting to blink at the normal high frequency again.

if you mean the ebus adapter with the base board: I'm almost 100% sure that there is no issue with the adapter itself but instead with your setup or with the UART. I'm using the adapter in all versions for many years now with my heating system without any issue of the kind you're describing.