Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Adapter: ebus

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.1k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

Adapter: ebus

Scheduled Pinned Locked Moved ioBroker Allgemein
ebus adapter
708 Posts 71 Posters 253.6k Views 59 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • HiltexH Offline
    HiltexH Offline
    Hiltex
    wrote on last edited by
    #28

    Leider sendet meine Therme fast garkeine Daten von sich aus. Ich muss so gut wie alles selber abfragen.

    Es gibt 272 Datenpunkte, die ich aktiv abfragen <u>kann</u>, und bei denen auch Werte zurückgeliefert werden.

    In der ersten Instanz rufe ich 80 davon ab, und in der zweiten 25.

    ioBroker läuft unter Ubuntu 17 als Virtuelle Maschine auf XPEnology (Synology DiskStation-Fork) mit dem Virtual Machine Manager. Die Maschine hat 3 GB RAM und 2 i5-Kerne, die sich recht langweilen.

    Plattform: linux

    Die Architektur: x64

    CPUs: 2

    Geschwindigkeit: 2499 MHz

    Modell: Intel(R) Core(TM) i5-4690T CPU @ 2.50GHz

    RAM: 2.9 GB

    System uptime: 09:02:14

    Node.js: v8.11.3

    NPM: 4.6.1

    Adapter zählen: 222

    Uptime: 09:01:35

    Das Log ist sehr unauffällig, es sei denn, es kommt mal zu einem Timeout. Der Raspi, auf dem ebusd läuft, langweilt sich auch ziemlich. Auf dem laufen auch noch FHEM und der Unifi-Controller von Ubiquiti.

    Also alles in allem ein recht solides System, wie ich finde.

    Hier das Log von der ersten Instanz:

    host.srv-iobroker1	2019-01-27 20:46:00.378	info	instance system.adapter.ebus.0 terminated with code 0 (OK)
    ebus.0	2019-01-27 20:45:27.424	info	all http done
    ebus.0	2019-01-27 20:45:27.421	debug	no update since 25.1.2019 7:45:56 bai.messages.WaterpressureVariantSum.lastup
    ebus.0	2019-01-27 20:45:27.421	debug	no update since 25.1.2019 8:16:0 bai.messages.WaterpressureMeasureCounter.lastup
    ebus.0	2019-01-27 20:45:27.420	debug	no update since 25.1.2019 8:16:0 bai.messages.WaterpressureBranchControlOff.lastup
    ebus.0	2019-01-27 20:45:27.420	debug	no update since 25.1.2019 8:15:59 bai.messages.WarmstartDemand.lastup
    ebus.0	2019-01-27 20:45:27.420	debug	no update since 25.1.2019 8:15:59 bai.messages.VolatileLockoutIFCGV.lastup
    ebus.0	2019-01-27 20:45:27.420	debug	no update since 25.1.2019 8:31:0 bai.messages.VolatileLockout.lastup
    ebus.0	2019-01-27 20:45:27.420	debug	no update since 25.1.2019 8:30:57 bai.messages.Testbyte.lastup
    ebus.0	2019-01-27 20:45:27.418	debug	no update since 25.1.2019 8:30:57 bai.messages.TempMaxDiffExtTFT.lastup
    ebus.0	2019-01-27 20:45:27.418	debug	no update since 25.1.2019 8:30:57 bai.messages.TemplimiterWithNTC.lastup
    ebus.0	2019-01-27 20:45:27.418	debug	no update since 25.1.2019 8:30:57 bai.messages.Templimiter.lastup
    ebus.0	2019-01-27 20:45:27.418	debug	no update since 25.1.2019 8:30:57 bai.messages.TempGradientFailure.lastup
    ebus.0	2019-01-27 20:45:27.418	debug	no update since 25.1.2019 8:30:56 bai.messages.TempDiffFailure.lastup
    ebus.0	2019-01-27 20:45:27.418	debug	no update since 25.1.2019 8:30:56 bai.messages.TempDiffBlock.lastup
    ebus.0	2019-01-27 20:45:27.416	debug	no update since 25.1.2019 8:30:48 bai.messages.Status.lastup
    ebus.0	2019-01-27 20:45:27.416	debug	no update since 25.1.2019 8:30:47 bai.messages.Status16.lastup
    ebus.0	2019-01-27 20:45:27.415	debug	no update since 25.1.2019 8:30:47 bai.messages.SHEMaxFlowTemp.lastup
    ebus.0	2019-01-27 20:45:27.415	debug	no update since 25.1.2019 8:30:46 bai.messages.SHEMaxDeltaHwcFlow.lastup
    ebus.0	2019-01-27 20:45:27.415	debug	no update since 25.1.2019 8:30:46 bai.messages.SetFactoryValues.lastup
    ebus.0	2019-01-27 20:45:27.414	debug	no update since 25.1.2019 8:30:46 bai.messages.SerialNumber.lastup
    ebus.0	2019-01-27 20:45:27.413	debug	no update since 25.1.2019 8:30:46 bai.messages.ReturnTempExternal.lastup
    ebus.0	2019-01-27 20:45:27.413	debug	no update since 25.1.2019 8:30:45 bai.messages.PumpHwcFlowSum.lastup
    ebus.0	2019-01-27 20:45:27.413	debug	no update since 25.1.2019 8:30:44 bai.messages.PumpHwcFlowNumber.lastup
    ebus.0	2019-01-27 20:45:27.412	debug	no update since 25.1.2019 8:30:44 bai.messages.ProductionByte.lastup
    ebus.0	2019-01-27 20:45:27.412	debug	no update since 25.1.2019 8:30:44 bai.messages.PrEnergySumHwc3.lastup
    ebus.0	2019-01-27 20:45:27.412	debug	no update since 25.1.2019 8:30:43 bai.messages.PrEnergySumHwc2.lastup
    ebus.0	2019-01-27 20:45:27.412	debug	no update since 25.1.2019 8:30:43 bai.messages.PrEnergySumHc3.lastup
    ebus.0	2019-01-27 20:45:27.412	debug	no update since 25.1.2019 8:30:42 bai.messages.PrEnergySumHc2.lastup
    ebus.0	2019-01-27 20:45:27.411	debug	no update since 25.1.2019 8:30:40 bai.messages.PrEnergyCountHwc3.lastup
    ebus.0	2019-01-27 20:45:27.411	debug	no update since 25.1.2019 8:30:40 bai.messages.PrEnergyCountHwc2.lastup
    ebus.0	2019-01-27 20:45:27.411	debug	no update since 25.1.2019 8:30:38 bai.messages.PrEnergyCountHc3.lastup
    ebus.0	2019-01-27 20:45:27.411	debug	no update since 25.1.2019 8:30:38 bai.messages.PrEnergyCountHc2.lastup
    ebus.0	2019-01-27 20:45:27.410	debug	no update since 25.1.2019 8:30:37 bai.messages.PrAPSSum.lastup
    ebus.0	2019-01-27 20:45:27.410	debug	no update since 25.1.2019 8:30:37 bai.messages.PrAPSCounter.lastup
    ebus.0	2019-01-27 20:45:27.409	debug	no update since 25.1.2019 8:30:36 bai.messages.PartnumberBox.lastup
    ebus.0	2019-01-27 20:45:27.409	debug	no update since 25.1.2019 8:30:34 bai.messages.ParamToken.lastup
    ebus.0	2019-01-27 20:45:27.409	debug	no update since 25.1.2019 8:30:33 bai.messages.OverflowCounter.lastup
    ebus.0	2019-01-27 20:45:27.409	debug	no update since 25.1.2019 8:30:31 bai.messages.OptionalRelais.lastup
    ebus.0	2019-01-27 20:45:27.408	debug	no update since 25.1.2019 8:30:26 bai.messages.InitialisationEEPROM.lastup
    ebus.0	2019-01-27 20:45:27.407	debug	no update since 25.1.2019 8:30:19 bai.messages.HoursTillService.lastup
    ebus.0	2019-01-27 20:45:27.406	debug	no update since 25.1.2019 8:30:16 bai.messages.FlowTempMax.lastup
    ebus.0	2019-01-27 20:45:27.405	debug	no update since 25.1.2019 8:30:14 bai.messages.FanStarts.lastup
    ebus.0	2019-01-27 20:45:27.405	debug	no update since 25.1.2019 8:30:13 bai.messages.FanSpeedOffsetMin.lastup
    ebus.0	2019-01-27 20:45:27.405	debug	no update since 25.1.2019 8:30:13 bai.messages.FanSpeedOffsetMax.lastup
    ebus.0	2019-01-27 20:45:27.405	debug	no update since 25.1.2019 8:30:13 bai.messages.FanPWMTest.lastup
    ebus.0	2019-01-27 20:45:27.405	debug	no update since 25.1.2019 8:30:13 bai.messages.FanPWMSum.lastup
    ebus.0	2019-01-27 20:45:27.404	debug	no update since 25.1.2019 8:30:8 bai.messages.ExtStorageModulCon.lastup
    ebus.0	2019-01-27 20:45:27.404	debug	no update since 25.1.2019 8:30:7 bai.messages.externalHwcSwitch.lastup
    ebus.0	2019-01-27 20:45:27.404	debug	no update since 25.1.2019 8:30:7 bai.messages.ExternalFaultmessage.lastup
    ebus.0	2019-01-27 20:45:27.403	debug	no update since 25.1.2019 8:30:7 bai.messages.EbusVoltage.lastup
    ebus.0	2019-01-27 20:45:27.403	debug	no update since 25.1.2019 8:30:7 bai.messages.EbusSourceOn.lastup
    ebus.0	2019-01-27 20:45:27.402	debug	no update since 25.1.2019 8:30:6 bai.messages.DSNStart.lastup
    ebus.0	2019-01-27 20:45:27.402	debug	no update since 25.1.2019 8:30:6 bai.messages.DSNOffset.lastup
    ebus.0	2019-01-27 20:45:27.402	debug	no update since 25.1.2019 8:30:6 bai.messages.DSN.lastup
    ebus.0	2019-01-27 20:45:27.402	debug	no update since 25.1.2019 8:30:6 bai.messages.DisplayMode.lastup
    ebus.0	2019-01-27 20:45:27.402	debug	no update since 25.1.2019 8:30:5 bai.messages.DeactivationsTemplimiter.lastup
    ebus.0	2019-01-27 20:45:27.402	debug	no update since 25.1.2019 8:30:5 bai.messages.DeactivationsIFC.lastup
    ebus.0	2019-01-27 20:45:27.402	debug	no update since 25.1.2019 8:30:5 bai.messages.DCRoomthermostat.lastup
    ebus.0	2019-01-27 20:45:27.401	debug	no update since 25.1.2019 8:30:5 bai.messages.DCFTimeDate.lastup
    ebus.0	2019-01-27 20:45:27.401	debug	no update since 25.1.2019 8:30:5 bai.messages.dcfState.lastup
    ebus.0	2019-01-27 20:45:27.401	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartAttempts4.lastup
    ebus.0	2019-01-27 20:45:27.401	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartAttempts3.lastup
    ebus.0	2019-01-27 20:45:27.401	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartattempts2.lastup
    ebus.0	2019-01-27 20:45:27.401	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartattempts1.lastup
    ebus.0	2019-01-27 20:45:27.400	debug	no update since 25.1.2019 8:30:3 bai.messages.CodingResistor.lastup
    ebus.0	2019-01-27 20:45:27.400	debug	no update since 25.1.2019 8:30:3 bai.messages.ChangesDSN.lastup
    ebus.0	2019-01-27 20:45:27.400	debug	no update since 25.1.2019 8:30:3 bai.messages.BoilerType.lastup
    ebus.0	2019-01-27 20:45:27.400	debug	no update since 25.1.2019 8:30:2 bai.messages.BlockTimeHcMax.lastup
    ebus.0	2019-01-27 20:45:27.399	debug	no update since 25.1.2019 8:30:1 bai.messages.averageIgnitiontime.lastup
    ebus.0	2019-01-27 20:45:27.399	debug	no update since 25.1.2019 8:30:0 bai.messages.AntiCondensValue.lastup
    ebus.0	2019-01-27 20:45:27.398	debug	no update since 25.1.2019 8:30:0 bai.messages.AccessoriesTwo.lastup
    ebus.0	2019-01-27 20:45:27.398	debug	no update since 25.1.2019 8:30:0 bai.messages.AccessoriesOne.lastup
    ebus.0	2019-01-27 20:45:27.398	debug	no update since 25.1.2019 9:7:49 700.messages.z2Shortname.lastup
    ebus.0	2019-01-27 20:45:27.398	debug	no update since 25.1.2019 9:7:40 700.messages.z2RoomTemp.lastup
    ebus.0	2019-01-27 20:45:27.397	debug	no update since 25.1.2019 9:7:40 700.messages.z2QuickVetoTemp.lastup
    ebus.0	2019-01-27 20:45:27.397	debug	no update since 25.1.2019 9:7:39 700.messages.z2OpMode.lastup
    ebus.0	2019-01-27 20:45:27.397	debug	no update since 25.1.2019 9:7:38 700.messages.z2NightTemp.lastup
    ebus.0	2019-01-27 20:45:27.397	debug	no update since 25.1.2019 9:7:37 700.messages.z2Name2.lastup
    ebus.0	2019-01-27 20:45:27.397	debug	no update since 25.1.2019 9:7:36 700.messages.z2Name1.lastup
    ebus.0	2019-01-27 20:45:27.397	debug	no update since 25.1.2019 9:7:31 700.messages.z2HolidayStartPeriod.lastup
    ebus.0	2019-01-27 20:45:27.397	debug	no update since 25.1.2019 9:7:30 700.messages.z2HolidayEndPeriod.lastup
    ebus.0	2019-01-27 20:45:27.396	debug	no update since 25.1.2019 9:7:29 700.messages.z2DayTemp.lastup
    ebus.0	2019-01-27 20:45:27.389	debug	no update since 25.1.2019 9:7:22 700.messages.z2BankHolidayStartPeriod.lastup
    ebus.0	2019-01-27 20:45:27.389	debug	no update since 25.1.2019 9:7:21 700.messages.z2BankHolidayEndPeriod.lastup
    ebus.0	2019-01-27 20:45:27.389	debug	no update since 25.1.2019 9:7:20 700.messages.z2ActualRoomTempDesired.lastup
    ebus.0	2019-01-27 20:45:27.387	debug	no update since 25.1.2019 9:2:46 700.messages.z1Shortname.lastup
    ebus.0	2019-01-27 20:45:27.387	debug	no update since 25.1.2019 8:52:54 700.messages.z1SFMode.lastup
    ebus.0	2019-01-27 20:45:27.387	debug	no update since 25.1.2019 9:2:43 700.messages.z1RoomZoneMapping.lastup
    ebus.0	2019-01-27 20:45:27.387	debug	no update since 25.1.2019 9:2:42 700.messages.z1RoomTemp.lastup
    ebus.0	2019-01-27 20:45:27.386	debug	no update since 25.1.2019 9:2:39 700.messages.z1OpMode.lastup
    ebus.0	2019-01-27 20:45:27.386	debug	no update since 25.1.2019 9:2:38 700.messages.z1Name2.lastup
    ebus.0	2019-01-27 20:45:27.386	debug	no update since 25.1.2019 9:2:36 700.messages.z1Name1.lastup
    ebus.0	2019-01-27 20:45:27.386	debug	no update since 25.1.2019 9:2:34 700.messages.z1BankHolidayStartPeriod.lastup
    ebus.0	2019-01-27 20:45:27.386	debug	no update since 25.1.2019 9:2:33 700.messages.z1BankHolidayEndPeriod.lastup
    ebus.0	2019-01-27 20:45:27.385	debug	no update since 25.1.2019 9:2:27 700.messages.Time.lastup
    ebus.0	2019-01-27 20:45:27.385	debug	no update since 25.1.2019 9:2:26 700.messages.SystemFlowTemp.lastup
    ebus.0	2019-01-27 20:45:27.385	debug	no update since 25.1.2019 8:52:25 700.messages.SFMode.lastup
    ebus.0	2019-01-27 20:45:27.385	debug	no update since 25.1.2019 9:2:20 700.messages.PumpAdditionalTime.lastup
    ebus.0	2019-01-27 20:45:27.384	debug	no update since 25.1.2019 9:2:19 700.messages.PrEnergySumHwcThisMonth.lastup
    ebus.0	2019-01-27 20:45:27.384	debug	no update since 25.1.2019 9:2:17 700.messages.PrEnergySumHwcLastMonth.lastup
    ebus.0	2019-01-27 20:45:27.384	debug	no update since 25.1.2019 9:2:16 700.messages.PrEnergySumHwc.lastup
    ebus.0	2019-01-27 20:45:27.384	debug	no update since 25.1.2019 9:2:15 700.messages.PrEnergySumHcThisMonth.lastup
    ebus.0	2019-01-27 20:45:27.384	debug	no update since 25.1.2019 9:2:14 700.messages.PrEnergySumHcLastMonth.lastup
    ebus.0	2019-01-27 20:45:27.384	debug	no update since 25.1.2019 9:2:13 700.messages.PrEnergySumHc.lastup
    ebus.0	2019-01-27 20:45:27.383	debug	no update since 25.1.2019 9:2:12 700.messages.PrEnergySum.lastup
    ebus.0	2019-01-27 20:45:27.383	debug	no update since 25.1.2019 9:2:11 700.messages.OpModeEffect.lastup
    ebus.0	2019-01-27 20:45:27.383	debug	no update since 25.1.2019 8:52:6 700.messages.MultiRelaySetting.lastup
    ebus.0	2019-01-27 20:45:27.382	debug	no update since 25.1.2019 8:57:3 700.messages.MaxRoomHumidity.lastup
    ebus.0	2019-01-27 20:45:27.382	debug	no update since 24.1.2019 21:58:56 700.messages.MaxCylinderChargeTime.lastup
    ebus.0	2019-01-27 20:45:27.382	debug	no update since 25.1.2019 8:48:0 700.messages.MaintenanceDue.lastup
    ebus.0	2019-01-27 20:45:27.382	debug	no update since 24.1.2019 21:54:57 700.messages.MaintenanceDate.lastup
    ebus.0	2019-01-27 20:45:27.382	debug	no update since 25.1.2019 8:47:55 700.messages.KeyCodeforConfigMenu.lastup
    ebus.0	2019-01-27 20:45:27.382	debug	no update since 25.1.2019 8:47:55 700.messages.Installer2.lastup
    ebus.0	2019-01-27 20:45:27.382	debug	no update since 25.1.2019 8:47:54 700.messages.Installer1.lastup
    ebus.0	2019-01-27 20:45:27.381	debug	no update since 25.1.2019 8:42:44 700.messages.HydraulicScheme.lastup
    ebus.0	2019-01-27 20:45:27.381	debug	no update since 25.1.2019 8:47:47 700.messages.HwcStorageTempTop.lastup
    ebus.0	2019-01-27 20:45:27.381	debug	no update since 25.1.2019 8:47:46 700.messages.HwcStorageTempBottom.lastup
    ebus.0	2019-01-27 20:45:27.381	debug	no update since 25.1.2019 8:47:44 700.messages.HwcSFMode.lastup
    ebus.0	2019-01-27 20:45:27.381	debug	no update since 25.1.2019 8:47:43 700.messages.HwcParallelLoading.lastup
    ebus.0	2019-01-27 20:45:27.381	debug	no update since 25.1.2019 8:47:42 700.messages.HwcOpMode.lastup
    ebus.0	2019-01-27 20:45:27.380	debug	no update since 25.1.2019 8:47:40 700.messages.HwcLockTime.lastup
    ebus.0	2019-01-27 20:45:27.380	debug	no update since 24.1.2019 21:43:53 700.messages.HwcHolidayStartPeriod.lastup
    ebus.0	2019-01-27 20:45:27.380	debug	no update since 25.1.2019 8:47:40 700.messages.HwcFlowTemp.lastup
    ebus.0	2019-01-27 20:45:27.380	debug	no update since 24.1.2019 21:43:39 700.messages.HolidayTemp.lastup
    ebus.0	2019-01-27 20:45:27.380	debug	no update since 24.1.2019 21:43:33 700.messages.HolidayEndPeriod.lastup
    ebus.0	2019-01-27 20:45:27.380	debug	no update since 25.1.2019 8:47:39 700.messages.HcStorageTempTop.lastup
    ebus.0	2019-01-27 20:45:27.380	debug	no update since 25.1.2019 8:47:36 700.messages.HcStorageTempBottom.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:41:1 700.messages.Hc2SummerTempLimit.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:18:59 700.messages.Hc2Status.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:18:58 700.messages.Hc2RoomTempSwitchOn.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:18:57 700.messages.Hc2PumpStatus.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:40:47 700.messages.Hc2MixerMovement.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:40:46 700.messages.Hc2MinFlowTempDesired.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:40:45 700.messages.Hc2MaxFlowTempDesired.lastup
    ebus.0	2019-01-27 20:45:27.378	debug	no update since 24.1.2019 21:40:43 700.messages.Hc2HeatCurveAdaption.lastup
    ebus.0	2019-01-27 20:45:27.377	debug	no update since 24.1.2019 21:40:42 700.messages.Hc2HeatCurve.lastup
    ebus.0	2019-01-27 20:45:27.377	debug	no update since 24.1.2019 21:40:41 700.messages.Hc2FlowTemp.lastup
    ebus.0	2019-01-27 20:45:27.377	debug	no update since 24.1.2019 21:18:43 700.messages.Hc2ExcessTemp.lastup
    ebus.0	2019-01-27 20:45:27.377	debug	no update since 24.1.2019 21:18:43 700.messages.Hc2CircuitType.lastup
    ebus.0	2019-01-27 20:45:27.377	debug	no update since 24.1.2019 21:33:0 700.messages.Hc2AutoOffMode.lastup
    ebus.0	2019-01-27 20:45:27.377	debug	no update since 24.1.2019 21:40:28 700.messages.Hc2ActualFlowTempDesired.lastup
    ebus.0	2019-01-27 20:45:27.377	debug	no update since 24.1.2019 21:40:25 700.messages.Hc1RoomTempSwitchOn.lastup
    ebus.0	2019-01-27 20:45:27.376	debug	no update since 25.1.2019 8:47:24 700.messages.Hc1HeatCurveAdaption.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 25.1.2019 8:47:21 700.messages.Hc1ExcessTemp.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 24.1.2019 21:58:16 700.messages.Hc1CircuitType.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 24.1.2019 21:58:15 700.messages.Hc1AutoOffMode.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 25.1.2019 8:47:12 700.messages.FrostOverRideTime.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 25.1.2019 8:47:10 700.messages.Date.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 25.1.2019 8:47:9 700.messages.CylinderChargeOffset.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 25.1.2019 8:47:8 700.messages.CylinderChargeHyst.lastup
    ebus.0	2019-01-27 20:45:27.373	debug	no update since 25.1.2019 8:42:1 700.messages.currenterror.lastup
    ebus.0	2019-01-27 20:45:27.371	debug	no update since 24.1.2019 21:32:7 700.messages.BankHolidayStartPeriod.lastup
    ebus.0	2019-01-27 20:45:27.371	debug	no update since 25.1.2019 8:42:0 700.messages.AdaptHeatCurve.lastup
    ebus.0	2019-01-27 20:45:27.335	debug	request data from http://192.168.243.41:8889/data
    ebus.0	2019-01-27 20:45:27.335	debug	all telnet done
    ebus.0	2019-01-27 20:45:27.335	debug	for WPSecondStage
    ebus.0	2019-01-27 20:45:27.335	debug	received on
    ebus.0	2019-01-27 20:45:27.163	debug	for WPPostrunTime
    ebus.0	2019-01-27 20:45:27.163	debug	received 20
    ebus.0	2019-01-27 20:45:26.990	debug	for WP
    ebus.0	2019-01-27 20:45:26.990	debug	received on
    ebus.0	2019-01-27 20:45:26.819	debug	for WaterPressure
    ebus.0	2019-01-27 20:45:26.819	debug	received 1.6
    ebus.0	2019-01-27 20:45:26.532	debug	for WaterHcFlowMax
    ebus.0	2019-01-27 20:45:26.532	debug	received 1938
    ebus.0	2019-01-27 20:45:26.355	debug	for ValveStarts
    ebus.0	2019-01-27 20:45:26.355	debug	received 4497
    ebus.0	2019-01-27 20:45:26.179	debug	for TimerInputHc
    ebus.0	2019-01-27 20:45:26.179	debug	received on
    ebus.0	2019-01-27 20:45:26.006	debug	for TargetFanSpeedOutput
    ebus.0	2019-01-27 20:45:26.006	debug	received 0
    ebus.0	2019-01-27 20:45:25.167	debug	for TargetFanSpeed
    ebus.0	2019-01-27 20:45:25.167	debug	received 0
    ebus.0	2019-01-27 20:45:24.329	debug	for StorageTempMax
    ebus.0	2019-01-27 20:45:24.329	debug	received 80.44
    ebus.0	2019-01-27 20:45:23.489	debug	for StorageTempDesired
    ebus.0	2019-01-27 20:45:23.489	debug	received 55.00
    ebus.0	2019-01-27 20:45:22.642	debug	for StorageTemp
    ebus.0	2019-01-27 20:45:22.642	debug	received 50.19;ok
    ebus.0	2019-01-27 20:45:21.790	debug	for StorageLoadTimeMax
    ebus.0	2019-01-27 20:45:21.790	debug	received 45
    ebus.0	2019-01-27 20:45:20.947	debug	for StorageloadPumpStarts
    ebus.0	2019-01-27 20:45:20.947	debug	received 2001
    ebus.0	2019-01-27 20:45:20.068	debug	for StorageLoadPumpHours
    ebus.0	2019-01-27 20:45:20.068	debug	received 109
    ebus.0	2019-01-27 20:45:19.148	debug	for Storageloadpump
    ebus.0	2019-01-27 20:45:19.148	debug	received 0
    ebus.0	2019-01-27 20:45:18.278	debug	for StorageExitTemp
    ebus.0	2019-01-27 20:45:18.278	debug	received 48.75;ok
    ebus.0	2019-01-27 20:45:18.096	debug	for StorageDelay
    ebus.0	2019-01-27 20:45:18.096	debug	received 0
    ebus.0	2019-01-27 20:45:17.873	debug	for Status02
    ebus.0	2019-01-27 20:45:17.873	debug	received auto;60;75.0;70;65.0
    ebus.0	2019-01-27 20:45:17.700	debug	for Status01
    ebus.0	2019-01-27 20:45:17.700	debug	received 37.5;35.5;5.812;41.5;50.0;off
    ebus.0	2019-01-27 20:45:17.514	debug	for Statenumber
    ebus.0	2019-01-27 20:45:17.514	debug	received 7
    ebus.0	2019-01-27 20:45:17.341	debug	for ReturnTempMax
    ebus.0	2019-01-27 20:45:17.341	debug	received 60.44
    ebus.0	2019-01-27 20:45:17.165	debug	for ReturnTemp
    ebus.0	2019-01-27 20:45:17.165	debug	received 35.62;64965;ok
    ebus.0	2019-01-27 20:45:16.976	debug	for ReturnRegulation
    ebus.0	2019-01-27 20:45:16.976	debug	received on
    ebus.0	2019-01-27 20:45:16.803	debug	for RemainingBoilerblocktime
    ebus.0	2019-01-27 20:45:16.803	debug	received 5
    ebus.0	2019-01-27 20:45:16.630	debug	for PumpPowerDesired
    ebus.0	2019-01-27 20:45:16.630	debug	received 100
    ebus.0	2019-01-27 20:45:16.460	debug	for PumpPower
    ebus.0	2019-01-27 20:45:16.460	debug	received 70
    ebus.0	2019-01-27 20:45:16.263	debug	for PumpHours
    ebus.0	2019-01-27 20:45:16.263	debug	received 8766
    ebus.0	2019-01-27 20:45:16.090	debug	for PrVortexFlowSensorValue
    ebus.0	2019-01-27 20:45:16.090	debug	received 0
    ebus.0	2019-01-27 20:45:15.916	debug	for PrimaryCircuitFlowrate
    ebus.0	2019-01-27 20:45:15.916	debug	received 10.44
    ebus.0	2019-01-27 20:45:15.739	debug	for PrEnergySumHwc1
    ebus.0	2019-01-27 20:45:15.739	debug	received 112983426
    ebus.0	2019-01-27 20:45:15.555	debug	for PrEnergySumHc1
    ebus.0	2019-01-27 20:45:15.555	debug	received 2211222675
    ebus.0	2019-01-27 20:45:15.371	debug	for PrEnergyCountHwc1
    ebus.0	2019-01-27 20:45:15.371	debug	received 411790
    ebus.0	2019-01-27 20:45:15.186	debug	for PrEnergyCountHc1
    ebus.0	2019-01-27 20:45:15.186	debug	received 16065305
    ebus.0	2019-01-27 20:45:15.001	debug	for PowerValue
    ebus.0	2019-01-27 20:45:15.001	debug	received 13 03 58 0e 64 10
    ebus.0	2019-01-27 20:45:14.800	debug	for PositionValveSet
    ebus.0	2019-01-27 20:45:14.800	debug	received 0
    ebus.0	2019-01-27 20:45:14.627	debug	for PartloadHcKW
    ebus.0	2019-01-27 20:45:14.627	debug	received 8
    ebus.0	2019-01-27 20:45:14.455	debug	for OutdoorstempSensor
    ebus.0	2019-01-27 20:45:14.455	debug	received 5.81;ok
    ebus.0	2019-01-27 20:45:14.274	debug	for ModulationTempDesired
    ebus.0	2019-01-27 20:45:14.274	debug	received 19.0
    ebus.0	2019-01-27 20:45:14.096	debug	for minIgnitiontime
    ebus.0	2019-01-27 20:45:14.096	debug	received 0.2
    ebus.0	2019-01-27 20:45:13.925	debug	for maxIgnitiontime
    ebus.0	2019-01-27 20:45:13.925	debug	received 2.0
    ebus.0	2019-01-27 20:45:13.752	debug	for maintenancedata_HwcTempMax
    ebus.0	2019-01-27 20:45:13.752	debug	received 113.56
    ebus.0	2019-01-27 20:45:13.575	debug	for IonisationVoltageLevel
    ebus.0	2019-01-27 20:45:13.575	debug	received 80.9
    ebus.0	2019-01-27 20:45:13.399	debug	for Ignitor
    ebus.0	2019-01-27 20:45:13.399	debug	received off
    ebus.0	2019-01-27 20:45:12.555	debug	for HwcUnderHundredStarts
    ebus.0	2019-01-27 20:45:12.555	debug	received 83
    ebus.0	2019-01-27 20:45:11.712	debug	for HwcTypes
    ebus.0	2019-01-27 20:45:11.712	debug	received 1
    ebus.0	2019-01-27 20:45:10.873	debug	for HwcTempMax
    ebus.0	2019-01-27 20:45:10.873	debug	received 65.00
    ebus.0	2019-01-27 20:45:09.953	debug	for HwcTemp
    ebus.0	2019-01-27 20:45:09.953	debug	received 41.81;ok
    ebus.0	2019-01-27 20:45:09.076	debug	for HwcSwitch
    ebus.0	2019-01-27 20:45:09.076	debug	received on
    ebus.0	2019-01-27 20:45:08.199	debug	for HwcStarts
    ebus.0	2019-01-27 20:45:08.199	debug	received 900
    ebus.0	2019-01-27 20:45:08.021	debug	for HwcImpellorSwitch
    ebus.0	2019-01-27 20:45:08.021	debug	received no
    ebus.0	2019-01-27 20:45:07.797	debug	for HwcHours
    ebus.0	2019-01-27 20:45:07.797	debug	received 122
    ebus.0	2019-01-27 20:45:07.621	debug	for HwcDemand
    ebus.0	2019-01-27 20:45:07.621	debug	received no
    ebus.0	2019-01-27 20:45:07.449	debug	for HeatingSwitch
    ebus.0	2019-01-27 20:45:07.449	debug	received on
    ebus.0	2019-01-27 20:45:07.271	debug	for HcUnderHundredStarts
    ebus.0	2019-01-27 20:45:07.271	debug	received 12
    ebus.0	2019-01-27 20:45:07.099	debug	for HcStarts
    ebus.0	2019-01-27 20:45:07.099	debug	received 45400
    ebus.0	2019-01-27 20:45:06.924	debug	for HcPumpStarts
    ebus.0	2019-01-27 20:45:06.924	debug	received 6542
    ebus.0	2019-01-27 20:45:06.751	debug	for HcPumpMode
    ebus.0	2019-01-27 20:45:06.751	debug	received 3
    ebus.0	2019-01-27 20:45:06.582	debug	for HcHours
    ebus.0	2019-01-27 20:45:06.582	debug	received 4450
    ebus.0	2019-01-27 20:45:06.409	debug	for GasvalveUCFeedback
    ebus.0	2019-01-27 20:45:06.409	debug	received off
    ebus.0	2019-01-27 20:45:05.544	debug	for GasvalveUC
    ebus.0	2019-01-27 20:45:05.544	debug	received off
    ebus.0	2019-01-27 20:45:04.703	debug	for GasvalveASICFeedback
    ebus.0	2019-01-27 20:45:04.703	debug	received off
    ebus.0	2019-01-27 20:45:03.792	debug	for Gasvalve3UC
    ebus.0	2019-01-27 20:45:03.792	debug	received off
    ebus.0	2019-01-27 20:45:03.623	debug	for FluegasvalveOpen
    ebus.0	2019-01-27 20:45:03.623	debug	received on
    ebus.0	2019-01-27 20:45:03.453	debug	for Fluegasvalve
    ebus.0	2019-01-27 20:45:03.453	debug	received off
    ebus.0	2019-01-27 20:45:03.281	debug	for FlowTempDesired
    ebus.0	2019-01-27 20:45:03.281	debug	received 35.75
    ebus.0	2019-01-27 20:45:03.107	debug	for FlowTemp
    ebus.0	2019-01-27 20:45:03.107	debug	received 38.44;ok
    ebus.0	2019-01-27 20:45:02.929	debug	for FlowsetHcMax
    ebus.0	2019-01-27 20:45:02.929	debug	received 75.00
    ebus.0	2019-01-27 20:45:02.748	debug	for FloorHeatingContact
    ebus.0	2019-01-27 20:45:02.748	debug	received off
    ebus.0	2019-01-27 20:45:02.579	debug	for FlameSensingASIC
    ebus.0	2019-01-27 20:45:02.579	debug	received 572
    ebus.0	2019-01-27 20:45:02.399	debug	for Flame
    ebus.0	2019-01-27 20:45:02.399	debug	received off
    ebus.0	2019-01-27 20:45:02.230	debug	for FanSpeed
    ebus.0	2019-01-27 20:45:02.230	debug	received 0
    ebus.0	2019-01-27 20:45:02.049	debug	for FanMinSpeedOperation
    ebus.0	2019-01-27 20:45:02.049	debug	received 750
    ebus.0	2019-01-27 20:45:01.877	debug	for FanMaxSpeedOperation
    ebus.0	2019-01-27 20:45:01.877	debug	received 4200
    ebus.0	2019-01-27 20:45:01.704	debug	for FanHours
    ebus.0	2019-01-27 20:45:01.704	debug	received 4656
    ebus.0	2019-01-27 20:45:01.531	debug	for extWP
    ebus.0	2019-01-27 20:45:01.531	debug	received on
    ebus.0	2019-01-27 20:45:01.360	debug	for ExtFlowTempDesiredMin
    ebus.0	2019-01-27 20:45:01.360	debug	received 40.00
    ebus.0	2019-01-27 20:45:01.182	debug	for ExternGasvalve
    ebus.0	2019-01-27 20:45:01.182	debug	received 240
    ebus.0	2019-01-27 20:45:01.010	debug	for DeltaFlowReturnMax
    ebus.0	2019-01-27 20:45:01.010	debug	received 14.06
    ebus.0	2019-01-27 20:45:00.837	debug	for CirPump
    ebus.0	2019-01-27 20:45:00.837	debug	received on
    ebus.0	2019-01-27 20:45:00.412	debug	telnet connected
    ebus.0	2019-01-27 20:45:00.410	debug	connect telnet to IP 192.168.243.41 port 8888
    ebus.0	2019-01-27 20:45:00.410	debug	to poll ctr 80 vals: CirPump, DeltaFlowReturnMax, ExternGasvalve, ExtFlowTempDesiredMin, extWP, FanHours, FanMaxSpeedOperation, FanMinSpeedOperation, FanSpeed, Flame, FlameSensingASIC, FloorHeatingC
    ebus.0	2019-01-27 20:45:00.370	debug	init common variables
    ebus.0	2019-01-27 20:45:00.370	debug	init variables
    ebus.0	2019-01-27 20:45:00.370	debug	start with interface ebusd
    ebus.0	2019-01-27 20:45:00.369	info	starting. Version 0.5.5 in /opt/iobroker/node_modules/iobroker.ebus, node: v8.11.3
    ebus.0	2019-01-27 20:45:00.263	debug	statesDB connected
    ebus.0	2019-01-27 20:45:00.252	debug	objectDB connected
    host.srv-iobroker1	2019-01-27 20:45:00.007	info	instance system.adapter.ebus.0 started with pid 21497
    

    Und hier das von der zweiten:

    host.srv-iobroker1	2019-01-27 20:48:00.382	info	instance system.adapter.ebus.1 terminated with code 0 (OK)
    ebus.1	2019-01-27 20:47:31.282	info	all http done
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 7:45:56 bai.messages.WaterpressureVariantSum.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:16:0 bai.messages.WaterpressureMeasureCounter.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:16:0 bai.messages.WaterpressureBranchControlOff.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:15:59 bai.messages.WarmstartDemand.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:15:59 bai.messages.VolatileLockoutIFCGV.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:31:0 bai.messages.VolatileLockout.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:57 bai.messages.Testbyte.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:57 bai.messages.TempMaxDiffExtTFT.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:57 bai.messages.TemplimiterWithNTC.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:57 bai.messages.Templimiter.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:57 bai.messages.TempGradientFailure.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:56 bai.messages.TempDiffFailure.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:56 bai.messages.TempDiffBlock.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:48 bai.messages.Status.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:47 bai.messages.Status16.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:47 bai.messages.SHEMaxFlowTemp.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:46 bai.messages.SHEMaxDeltaHwcFlow.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:46 bai.messages.SetFactoryValues.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:46 bai.messages.SerialNumber.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:46 bai.messages.ReturnTempExternal.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:45 bai.messages.PumpHwcFlowSum.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:44 bai.messages.PumpHwcFlowNumber.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:44 bai.messages.ProductionByte.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:44 bai.messages.PrEnergySumHwc3.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:43 bai.messages.PrEnergySumHwc2.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:43 bai.messages.PrEnergySumHc3.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:42 bai.messages.PrEnergySumHc2.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:40 bai.messages.PrEnergyCountHwc3.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:40 bai.messages.PrEnergyCountHwc2.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:38 bai.messages.PrEnergyCountHc3.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:38 bai.messages.PrEnergyCountHc2.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:37 bai.messages.PrAPSSum.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:37 bai.messages.PrAPSCounter.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:36 bai.messages.PartnumberBox.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:34 bai.messages.ParamToken.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:33 bai.messages.OverflowCounter.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:31 bai.messages.OptionalRelais.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:26 bai.messages.InitialisationEEPROM.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:19 bai.messages.HoursTillService.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:16 bai.messages.FlowTempMax.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:14 bai.messages.FanStarts.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:13 bai.messages.FanSpeedOffsetMin.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:13 bai.messages.FanSpeedOffsetMax.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:13 bai.messages.FanPWMTest.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:13 bai.messages.FanPWMSum.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:8 bai.messages.ExtStorageModulCon.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:7 bai.messages.externalHwcSwitch.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:7 bai.messages.ExternalFaultmessage.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:7 bai.messages.EbusVoltage.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:7 bai.messages.EbusSourceOn.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:6 bai.messages.DSNStart.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:6 bai.messages.DSNOffset.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:6 bai.messages.DSN.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:6 bai.messages.DisplayMode.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:5 bai.messages.DeactivationsTemplimiter.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:5 bai.messages.DeactivationsIFC.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:5 bai.messages.DCRoomthermostat.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:5 bai.messages.DCFTimeDate.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:5 bai.messages.dcfState.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartAttempts4.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartAttempts3.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartattempts2.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartattempts1.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:3 bai.messages.CodingResistor.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:3 bai.messages.ChangesDSN.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:3 bai.messages.BoilerType.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:2 bai.messages.BlockTimeHcMax.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:1 bai.messages.averageIgnitiontime.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:0 bai.messages.AntiCondensValue.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:0 bai.messages.AccessoriesTwo.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 8:30:0 bai.messages.AccessoriesOne.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:49 700.messages.z2Shortname.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:40 700.messages.z2RoomTemp.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:40 700.messages.z2QuickVetoTemp.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:39 700.messages.z2OpMode.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:38 700.messages.z2NightTemp.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:37 700.messages.z2Name2.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:36 700.messages.z2Name1.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:31 700.messages.z2HolidayStartPeriod.lastup
    ebus.1	2019-01-27 20:47:31.282	debug	no update since 25.1.2019 9:7:30 700.messages.z2HolidayEndPeriod.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:7:29 700.messages.z2DayTemp.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:7:22 700.messages.z2BankHolidayStartPeriod.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:7:21 700.messages.z2BankHolidayEndPeriod.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:7:20 700.messages.z2ActualRoomTempDesired.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:46 700.messages.z1Shortname.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 8:52:54 700.messages.z1SFMode.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:43 700.messages.z1RoomZoneMapping.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:42 700.messages.z1RoomTemp.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:39 700.messages.z1OpMode.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:38 700.messages.z1Name2.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:36 700.messages.z1Name1.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:34 700.messages.z1BankHolidayStartPeriod.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:33 700.messages.z1BankHolidayEndPeriod.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:27 700.messages.Time.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:26 700.messages.SystemFlowTemp.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 8:52:25 700.messages.SFMode.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:20 700.messages.PumpAdditionalTime.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:19 700.messages.PrEnergySumHwcThisMonth.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:17 700.messages.PrEnergySumHwcLastMonth.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:16 700.messages.PrEnergySumHwc.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:15 700.messages.PrEnergySumHcThisMonth.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:14 700.messages.PrEnergySumHcLastMonth.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:13 700.messages.PrEnergySumHc.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:12 700.messages.PrEnergySum.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 9:2:11 700.messages.OpModeEffect.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 8:52:6 700.messages.MultiRelaySetting.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 25.1.2019 8:57:3 700.messages.MaxRoomHumidity.lastup
    ebus.1	2019-01-27 20:47:31.279	debug	no update since 24.1.2019 21:58:56 700.messages.MaxCylinderChargeTime.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:48:0 700.messages.MaintenanceDue.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:54:57 700.messages.MaintenanceDate.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:55 700.messages.KeyCodeforConfigMenu.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:55 700.messages.Installer2.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:54 700.messages.Installer1.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:42:44 700.messages.HydraulicScheme.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:47 700.messages.HwcStorageTempTop.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:46 700.messages.HwcStorageTempBottom.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:44 700.messages.HwcSFMode.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:43 700.messages.HwcParallelLoading.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:42 700.messages.HwcOpMode.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:40 700.messages.HwcLockTime.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:43:53 700.messages.HwcHolidayStartPeriod.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:40 700.messages.HwcFlowTemp.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:43:39 700.messages.HolidayTemp.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:43:33 700.messages.HolidayEndPeriod.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:39 700.messages.HcStorageTempTop.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:36 700.messages.HcStorageTempBottom.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:41:1 700.messages.Hc2SummerTempLimit.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:18:59 700.messages.Hc2Status.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:18:58 700.messages.Hc2RoomTempSwitchOn.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:18:57 700.messages.Hc2PumpStatus.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:47 700.messages.Hc2MixerMovement.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:46 700.messages.Hc2MinFlowTempDesired.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:45 700.messages.Hc2MaxFlowTempDesired.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:43 700.messages.Hc2HeatCurveAdaption.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:42 700.messages.Hc2HeatCurve.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:41 700.messages.Hc2FlowTemp.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:18:43 700.messages.Hc2ExcessTemp.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:18:43 700.messages.Hc2CircuitType.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:33:0 700.messages.Hc2AutoOffMode.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:28 700.messages.Hc2ActualFlowTempDesired.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:40:25 700.messages.Hc1RoomTempSwitchOn.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:24 700.messages.Hc1HeatCurveAdaption.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:21 700.messages.Hc1ExcessTemp.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:58:16 700.messages.Hc1CircuitType.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:58:15 700.messages.Hc1AutoOffMode.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:12 700.messages.FrostOverRideTime.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:10 700.messages.Date.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:9 700.messages.CylinderChargeOffset.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:47:8 700.messages.CylinderChargeHyst.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:42:1 700.messages.currenterror.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 24.1.2019 21:32:7 700.messages.BankHolidayStartPeriod.lastup
    ebus.1	2019-01-27 20:47:31.278	debug	no update since 25.1.2019 8:42:0 700.messages.AdaptHeatCurve.lastup
    ebus.1	2019-01-27 20:47:31.021	debug	request data from http://192.168.243.41:8889/data
    ebus.1	2019-01-27 20:47:31.021	debug	all telnet done
    ebus.1	2019-01-27 20:47:31.021	error	received ERR: read timeout for z1ValveStatus
    ebus.1	2019-01-27 20:47:27.170	debug	received 21 for z1QuickVetoTemp
    ebus.1	2019-01-27 20:47:26.246	debug	received 18 for z1NightTemp
    ebus.1	2019-01-27 20:47:25.323	debug	received 15 for z1HolidayTemp
    ebus.1	2019-01-27 20:47:24.399	debug	received 23 for z1DayTemp
    ebus.1	2019-01-27 20:47:23.476	debug	received 23 for z1ActualRoomTempDesired
    ebus.1	2019-01-27 20:47:22.553	debug	received 0 for YieldTotal
    ebus.1	2019-01-27 20:47:21.527	debug	received 1.6 for WaterPressure
    ebus.1	2019-01-27 20:47:20.501	debug	received 1120 for SolarYieldTotal
    ebus.1	2019-01-27 20:47:19.268	debug	received 5.66016 for OutsideTempAvg
    ebus.1	2019-01-27 20:47:18.037	debug	received 55 for HwcTempDesired
    ebus.1	2019-01-27 20:47:17.730	debug	received 50 for HwcStorageTemp
    ebus.1	2019-01-27 20:47:17.421	debug	received 80 for HwcMaxFlowTempDesired
    ebus.1	2019-01-27 20:47:16.398	debug	received 21 for Hc1SummerTempLimit
    ebus.1	2019-01-27 20:47:14.898	error	received ERR: read timeout for Hc1Status
    ebus.1	2019-01-27 20:47:12.029	error	received ERR: read timeout for Hc1PumpStatus
    ebus.1	2019-01-27 20:47:08.909	debug	received 0.0 for Hc1MixerMovement
    ebus.1	2019-01-27 20:47:08.601	debug	received 15 for Hc1MinFlowTempDesired
    ebus.1	2019-01-27 20:47:08.088	debug	received 58 for Hc1MaxFlowTempDesired
    ebus.1	2019-01-27 20:47:05.626	debug	received 1.3 for Hc1HeatCurve
    ebus.1	2019-01-27 20:47:04.600	debug	received 35.5 for Hc1FlowTemp
    ebus.1	2019-01-27 20:47:03.373	debug	received usage: read [-f] [-m SECONDS] [-s QQ] [-d ZZ] [-c CIRCUIT] [-p PRIO] [-v|-V] [-n|-N] [-i VALUE[;VALUE]*] NAME [FIELD[.N]] or: read [-f] [-m SECONDS] [-s QQ] [-d ZZ] [-v|-V] [-n|-N] [-i VAL
    ebus.1	2019-01-27 20:47:03.369	debug	received 51.6717 for Hc1ActualFlowTempDesired
    ebus.1	2019-01-27 20:47:00.906	debug	received 5.8125 for DisplayedOutsideTemp
    ebus.1	2019-01-27 20:47:00.603	debug	received -26 for ContinuosHeating
    ebus.1	2019-01-27 20:47:00.414	debug	telnet connected
    ebus.1	2019-01-27 20:47:00.414	debug	connect telnet to IP 192.168.243.41 port 8888
    ebus.1	2019-01-27 20:47:00.414	debug	to poll ctr 25 vals: ContinuosHeating,DisplayedOutsideTemp,Hc1ActualFlowTempDesired,,Hc1FlowTemp,Hc1HeatCurve,Hc1MaxFlowTempDesired,Hc1MinFlowTempDesired,Hc1MixerMovement,Hc1PumpStatus,Hc1Status,Hc1S
    ebus.1	2019-01-27 20:47:00.375	debug	init common variables
    ebus.1	2019-01-27 20:47:00.375	debug	init variables
    ebus.1	2019-01-27 20:47:00.375	debug	start with interface ebusd
    ebus.1	2019-01-27 20:47:00.375	info	starting. Version 0.5.5 in /opt/iobroker/node_modules/iobroker.ebus, node: v8.11.3
    host.srv-iobroker1	2019-01-27 20:47:00.007	info	instance system.adapter.ebus.1 started with pid 21563
    

    Das sind nun ausgerechnet zwei Musterbeispiele, was die Gesamtzeit betrifft, aber TimeOuts sind trotzdem dabei.

    Blog: indibit.de

    1 Reply Last reply
    0
    • Rene_HMR Offline
      Rene_HMR Offline
      Rene_HM
      Developer
      wrote on last edited by
      #29

      dann ist das klar, das Polling der Daten über telnet braucht bei dir hier im log ca. 30 Sekunden. Vielleicht sind die Antwortzeiten über den Bus auch recht unterschiedlich, dann kann es in Summe zu Zeiten über 60 Sekunden kommen.

      Ich baue das Timeout in die admin-Einstellungen ein und schau mir auch die telnet-Abfragen noch mal an…

      1 Reply Last reply
      0
      • HiltexH Offline
        HiltexH Offline
        Hiltex
        wrote on last edited by
        #30

        Danke.

        Kannst du mir noch sagen, wie ich Datenpunkte wieder los werde, die ich nicht mehr sehen will?

        Ich hatte anfangs wirklich mal alle geladen um zu sehen, was da so kommt. Jetzt werde ich die unnötigen aber nicht mehr los. Selbst wenn ich alle lösche werden die nach einem Durchlauf wieder angelegt - mit dem Datum der letzten Aktualisierung von vor 3 Tagen.

        Ich hab auch ebusd schon gestoppt und neu gestartet, aber das hilft irgendwie nicht.

        Blog: indibit.de

        1 Reply Last reply
        0
        • Rene_HMR Offline
          Rene_HMR Offline
          Rene_HM
          Developer
          wrote on last edited by
          #31

          Unter https://github.com/rg-engineering/ioBroker.ebus habe ich die Version 0.7.0 gelegt. Dort ist der timeout im admin unter /ebusd einstellbar.

          Die Datenpunkte werden vom ebusd geholt. Also alles, was der ebusd hat, wird übertragen und in Datenpunkte überführt. Damit sollte es reichen, den ebusd auf dem Raspi neu zu starten und danach die Datenpunkte aus dem Objektbaum in iobroker löschen.

          HiltexH 1 Reply Last reply
          0
          • HiltexH Offline
            HiltexH Offline
            Hiltex
            wrote on last edited by
            #32

            Probiere ich morgen aus. Danke.

            Blog: indibit.de

            1 Reply Last reply
            0
            • HiltexH Offline
              HiltexH Offline
              Hiltex
              wrote on last edited by
              #33

              Ich habe gerade Version 0.7.0 getestet. Läuft schon besser mit dem Timeout, aber wenn ich alle Datenpunkte reinpacke, kommt nach einer Weile ein Telnet-Timeout. Auch sind einige Datenpunkte noch immer nicht lesbar wegen Timeout, obwohl vergleichbare Datenpunkte einwandfrei laufen. Beispiel:

              ebus.0	2019-01-30 18:35:22.336	debug	received 06:00;22:00;-:-;-:-;-:-;-:- for ccTimer.Wednesday
              ebus.0	2019-01-30 18:35:21.205	debug	received 06:00;22:00;-:-;-:-;-:-;-:- for ccTimer.Tuesday
              ebus.0	2019-01-30 18:35:20.223	error	received ERR: read timeout for ccTimer.Thursday
              ebus.0	2019-01-30 18:35:17.142	error	received ERR: read timeout for ccTimer.Sunday
              ebus.0	2019-01-30 18:35:12.487	debug	received 07:30;23:30;-:-;-:-;-:-;-:- for ccTimer.Saturday
              ebus.0	2019-01-30 18:35:11.358	debug	received 06:00;22:00;-:-;-:-;-:-;-:- for ccTimer.Monday
              ebus.0	2019-01-30 18:35:10.370	error	received ERR: read timeout for ccTimer.Friday
              

              Das wundert mich sehr. Allerdings kommt bei einigen auch ein Timeout, wenn ich die manuell abrufe. Hc1Status jedoch liefert sofort eine Antwort, obwohl hier im Log ein Timeout erscheint.

              Nachfolgend das gesamte Log:

              host.srv-iobroker-dev	2019-01-30 18:37:20.526	info	instance system.adapter.ebus.0 terminated with code 0 (OK)
              ebus.0	2019-01-30 18:37:20.415	info	all http done
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 7:45:56 bai.messages.WaterpressureVariantSum.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:16:0 bai.messages.WaterpressureMeasureCounter.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:16:0 bai.messages.WaterpressureBranchControlOff.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:15:59 bai.messages.WarmstartDemand.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:15:59 bai.messages.VolatileLockoutIFCGV.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:31:0 bai.messages.VolatileLockout.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:57 bai.messages.Testbyte.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:57 bai.messages.TempMaxDiffExtTFT.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:57 bai.messages.TemplimiterWithNTC.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:57 bai.messages.Templimiter.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:57 bai.messages.TempGradientFailure.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:56 bai.messages.TempDiffFailure.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:56 bai.messages.TempDiffBlock.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:48 bai.messages.Status.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:47 bai.messages.Status16.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:47 bai.messages.SHEMaxFlowTemp.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:46 bai.messages.SHEMaxDeltaHwcFlow.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:46 bai.messages.SetFactoryValues.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:46 bai.messages.SerialNumber.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:46 bai.messages.ReturnTempExternal.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:45 bai.messages.PumpHwcFlowSum.lastup
              ebus.0	2019-01-30 18:37:20.415	debug	no update since 25.1.2019 8:30:44 bai.messages.PumpHwcFlowNumber.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:44 bai.messages.ProductionByte.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:44 bai.messages.PrEnergySumHwc3.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:43 bai.messages.PrEnergySumHwc2.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:43 bai.messages.PrEnergySumHc3.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:42 bai.messages.PrEnergySumHc2.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:40 bai.messages.PrEnergyCountHwc3.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:40 bai.messages.PrEnergyCountHwc2.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:38 bai.messages.PrEnergyCountHc3.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:38 bai.messages.PrEnergyCountHc2.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:37 bai.messages.PrAPSSum.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:37 bai.messages.PrAPSCounter.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:36 bai.messages.PartnumberBox.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:34 bai.messages.ParamToken.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:33 bai.messages.OverflowCounter.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:31 bai.messages.OptionalRelais.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:26 bai.messages.InitialisationEEPROM.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:19 bai.messages.HoursTillService.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:16 bai.messages.FlowTempMax.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:14 bai.messages.FanStarts.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:13 bai.messages.FanSpeedOffsetMin.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:13 bai.messages.FanSpeedOffsetMax.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:13 bai.messages.FanPWMTest.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:13 bai.messages.FanPWMSum.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:8 bai.messages.ExtStorageModulCon.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:7 bai.messages.externalHwcSwitch.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:7 bai.messages.ExternalFaultmessage.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:7 bai.messages.EbusVoltage.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:7 bai.messages.EbusSourceOn.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:6 bai.messages.DSNStart.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:6 bai.messages.DSNOffset.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:6 bai.messages.DSN.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:6 bai.messages.DisplayMode.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:5 bai.messages.DeactivationsTemplimiter.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:5 bai.messages.DeactivationsIFC.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:5 bai.messages.DCRoomthermostat.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:5 bai.messages.DCFTimeDate.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:5 bai.messages.dcfState.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartAttempts4.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartAttempts3.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartattempts2.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:4 bai.messages.CounterStartattempts1.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:3 bai.messages.CodingResistor.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:3 bai.messages.ChangesDSN.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:3 bai.messages.BoilerType.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:2 bai.messages.BlockTimeHcMax.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:1 bai.messages.averageIgnitiontime.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:0 bai.messages.AntiCondensValue.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:0 bai.messages.AccessoriesTwo.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:30:0 bai.messages.AccessoriesOne.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:49 700.messages.z2Shortname.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:40 700.messages.z2RoomTemp.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:40 700.messages.z2QuickVetoTemp.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:39 700.messages.z2OpMode.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:38 700.messages.z2NightTemp.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:37 700.messages.z2Name2.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:36 700.messages.z2Name1.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:31 700.messages.z2HolidayStartPeriod.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:30 700.messages.z2HolidayEndPeriod.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:29 700.messages.z2DayTemp.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:22 700.messages.z2BankHolidayStartPeriod.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:21 700.messages.z2BankHolidayEndPeriod.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:7:20 700.messages.z2ActualRoomTempDesired.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:46 700.messages.z1Shortname.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:52:54 700.messages.z1SFMode.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:43 700.messages.z1RoomZoneMapping.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:42 700.messages.z1RoomTemp.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:39 700.messages.z1OpMode.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:38 700.messages.z1Name2.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:36 700.messages.z1Name1.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:34 700.messages.z1BankHolidayStartPeriod.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:33 700.messages.z1BankHolidayEndPeriod.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:27 700.messages.Time.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 9:2:26 700.messages.SystemFlowTemp.lastup
              ebus.0	2019-01-30 18:37:20.408	debug	no update since 25.1.2019 8:52:25 700.messages.SFMode.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:20 700.messages.PumpAdditionalTime.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:19 700.messages.PrEnergySumHwcThisMonth.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:17 700.messages.PrEnergySumHwcLastMonth.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:16 700.messages.PrEnergySumHwc.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:15 700.messages.PrEnergySumHcThisMonth.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:14 700.messages.PrEnergySumHcLastMonth.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:13 700.messages.PrEnergySumHc.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:12 700.messages.PrEnergySum.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 9:2:11 700.messages.OpModeEffect.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:52:6 700.messages.MultiRelaySetting.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:57:3 700.messages.MaxRoomHumidity.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 24.1.2019 21:58:56 700.messages.MaxCylinderChargeTime.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:48:0 700.messages.MaintenanceDue.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 24.1.2019 21:54:57 700.messages.MaintenanceDate.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:47:55 700.messages.KeyCodeforConfigMenu.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:47:55 700.messages.Installer2.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:47:54 700.messages.Installer1.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:42:44 700.messages.HydraulicScheme.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:47:40 700.messages.HwcLockTime.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 24.1.2019 21:43:53 700.messages.HwcHolidayStartPeriod.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 24.1.2019 21:18:59 700.messages.Hc2Status.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 24.1.2019 21:18:58 700.messages.Hc2RoomTempSwitchOn.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:47:12 700.messages.FrostOverRideTime.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 24.1.2019 21:32:7 700.messages.BankHolidayStartPeriod.lastup
              ebus.0	2019-01-30 18:37:20.407	debug	no update since 25.1.2019 8:42:0 700.messages.AdaptHeatCurve.lastup
              ebus.0	2019-01-30 18:37:17.582	debug	request data from http://192.168.243.41:8889/data
              ebus.0	2019-01-30 18:37:17.582	error	Telnet Server timeout
              ebus.0	2019-01-30 18:37:12.575	error	received ERR: read timeout for hwcTimer.Sunday
              ebus.0	2019-01-30 18:37:09.866	debug	received 07:00;23:30;-:-;-:-;-:-;-:- for hwcTimer.Saturday
              ebus.0	2019-01-30 18:37:08.532	debug	received 05:30;22:00;-:-;-:-;-:-;-:- for hwcTimer.Monday
              ebus.0	2019-01-30 18:37:07.608	debug	received 05:30;22:00;-:-;-:-;-:-;-:- for hwcTimer.Friday
              ebus.0	2019-01-30 18:37:05.765	debug	received 55 for HwcTempDesired
              ebus.0	2019-01-30 18:37:02.378	debug	received - for HwcStorageTempTop
              ebus.0	2019-01-30 18:37:00.533	debug	received - for HwcStorageTempBottom
              ebus.0	2019-01-30 18:36:59.605	debug	received 45.5 for HwcStorageTemp
              ebus.0	2019-01-30 18:36:58.671	debug	received auto for HwcSFMode
              ebus.0	2019-01-30 18:36:57.748	debug	received off for HwcParallelLoading
              ebus.0	2019-01-30 18:36:56.829	debug	received day for HwcOpMode
              ebus.0	2019-01-30 18:36:55.914	debug	received 80 for HwcMaxFlowTempDesired
              ebus.0	2019-01-30 18:36:52.982	error	received ERR: read timeout for HwcLockTime
              ebus.0	2019-01-30 18:36:50.113	error	received ERR: read timeout for HwcHolidayStartPeriod
              ebus.0	2019-01-30 18:36:47.702	debug	received 01.01.2015 for HwcHolidayEndPeriod
              ebus.0	2019-01-30 18:36:44.523	debug	received 0.0 for HwcFlowTemp
              ebus.0	2019-01-30 18:36:43.596	debug	received 01.01.2015 for HwcBankHolidayStartPeriod
              ebus.0	2019-01-30 18:36:42.673	debug	received 01.01.2015 for HwcBankHolidayEndPeriod
              ebus.0	2019-01-30 18:36:41.753	debug	received 15 for HolidayTemp
              ebus.0	2019-01-30 18:36:40.826	debug	received 01.01.2015 for HolidayStartPeriod
              ebus.0	2019-01-30 18:36:39.905	debug	received 01.01.2015 for HolidayEndPeriod
              ebus.0	2019-01-30 18:36:38.985	debug	received - for HcStorageTempTop
              ebus.0	2019-01-30 18:36:38.059	debug	received - for HcStorageTempBottom
              ebus.0	2019-01-30 18:36:37.139	debug	received 21 for Hc3SummerTempLimit
              ebus.0	2019-01-30 18:36:35.382	debug	received 0 for Hc3Status
              ebus.0	2019-01-30 18:36:34.463	debug	received off for Hc3RoomTempSwitchOn
              ebus.0	2019-01-30 18:36:33.537	debug	received 0 for Hc3PumpStatus
              ebus.0	2019-01-30 18:36:32.624	debug	received 0.0 for Hc3MixerMovement
              ebus.0	2019-01-30 18:36:31.701	debug	received 15 for Hc3MinFlowTempDesired
              ebus.0	2019-01-30 18:36:30.778	debug	received 90 for Hc3MaxFlowTempDesired
              ebus.0	2019-01-30 18:36:29.854	debug	received 0.0 for Hc3HeatCurveAdaption
              ebus.0	2019-01-30 18:36:28.931	debug	received 1.2 for Hc3HeatCurve
              ebus.0	2019-01-30 18:36:28.007	debug	received - for Hc3FlowTemp
              ebus.0	2019-01-30 18:36:26.979	debug	received 0.0 for Hc3ExcessTemp
              ebus.0	2019-01-30 18:36:25.486	error	received ERR: read timeout for Hc3CircuitType
              ebus.0	2019-01-30 18:36:21.893	error	received ERR: read timeout for Hc3AutoOffMode
              ebus.0	2019-01-30 18:36:19.491	debug	received 0.0 for Hc3ActualFlowTempDesired
              ebus.0	2019-01-30 18:36:19.184	debug	received 21 for Hc2SummerTempLimit
              ebus.0	2019-01-30 18:36:16.157	error	received ERR: read timeout for Hc2Status
              ebus.0	2019-01-30 18:36:11.842	error	received ERR: read timeout for Hc2RoomTempSwitchOn
              ebus.0	2019-01-30 18:36:09.428	debug	received 0 for Hc2PumpStatus
              ebus.0	2019-01-30 18:36:09.128	debug	received 0.0 for Hc2MixerMovement
              ebus.0	2019-01-30 18:36:08.102	debug	received 15 for Hc2MinFlowTempDesired
              ebus.0	2019-01-30 18:36:04.924	debug	received 90 for Hc2MaxFlowTempDesired
              ebus.0	2019-01-30 18:36:04.001	debug	received 0.0 for Hc2HeatCurveAdaption
              ebus.0	2019-01-30 18:36:03.078	debug	received 1.2 for Hc2HeatCurve
              ebus.0	2019-01-30 18:36:02.155	debug	received - for Hc2FlowTemp
              ebus.0	2019-01-30 18:36:00.921	debug	received 0.0 for Hc2ExcessTemp
              ebus.0	2019-01-30 18:35:58.863	debug	received mixer for Hc2CircuitType
              ebus.0	2019-01-30 18:35:57.119	debug	received eco for Hc2AutoOffMode
              ebus.0	2019-01-30 18:35:56.614	debug	received 0.0 for Hc2ActualFlowTempDesired
              ebus.0	2019-01-30 18:35:54.768	debug	received 21 for Hc1SummerTempLimit
              ebus.0	2019-01-30 18:35:51.625	error	received ERR: read timeout for Hc1Status
              ebus.0	2019-01-30 18:35:49.013	debug	received off for Hc1RoomTempSwitchOn
              ebus.0	2019-01-30 18:35:48.603	debug	received 1 for Hc1PumpStatus
              ebus.0	2019-01-30 18:35:48.201	debug	received 0.0 for Hc1MixerMovement
              ebus.0	2019-01-30 18:35:47.791	debug	received 15 for Hc1MinFlowTempDesired
              ebus.0	2019-01-30 18:35:47.380	debug	received 58 for Hc1MaxFlowTempDesired
              ebus.0	2019-01-30 18:35:46.970	debug	received 0.0 for Hc1HeatCurveAdaption
              ebus.0	2019-01-30 18:35:46.559	debug	received 1.3 for Hc1HeatCurve
              ebus.0	2019-01-30 18:35:45.428	debug	received 44 for Hc1FlowTemp
              ebus.0	2019-01-30 18:35:45.018	debug	received 0.0 for Hc1ExcessTemp
              ebus.0	2019-01-30 18:35:43.883	debug	received mixer for Hc1CircuitType
              ebus.0	2019-01-30 18:35:42.036	debug	received night for Hc1AutoOffMode
              ebus.0	2019-01-30 18:35:40.300	debug	received 57.0535 for Hc1ActualFlowTempDesired
              ebus.0	2019-01-30 18:35:38.700	error	received ERR: read timeout for FrostOverRideTime
              ebus.0	2019-01-30 18:35:34.719	error	received ERR: end of input reached for errorhistory
              ebus.0	2019-01-30 18:35:33.832	debug	received 1.5625 for DisplayedOutsideTemp
              ebus.0	2019-01-30 18:35:31.262	debug	received 30.01.2019 for Date
              ebus.0	2019-01-30 18:35:29.523	debug	received 25 for CylinderChargeOffset
              ebus.0	2019-01-30 18:35:27.777	debug	received 5 for CylinderChargeHyst
              ebus.0	2019-01-30 18:35:25.941	debug	received -;-;-;-;- for currenterror
              ebus.0	2019-01-30 18:35:24.192	debug	received -26 for ContinuosHeating
              ebus.0	2019-01-30 18:35:22.336	debug	received 06:00;22:00;-:-;-:-;-:-;-:- for ccTimer.Wednesday
              ebus.0	2019-01-30 18:35:21.205	debug	received 06:00;22:00;-:-;-:-;-:-;-:- for ccTimer.Tuesday
              ebus.0	2019-01-30 18:35:20.223	error	received ERR: read timeout for ccTimer.Thursday
              ebus.0	2019-01-30 18:35:17.142	error	received ERR: read timeout for ccTimer.Sunday
              ebus.0	2019-01-30 18:35:12.487	debug	received 07:30;23:30;-:-;-:-;-:-;-:- for ccTimer.Saturday
              ebus.0	2019-01-30 18:35:11.358	debug	received 06:00;22:00;-:-;-:-;-:-;-:- for ccTimer.Monday
              ebus.0	2019-01-30 18:35:10.370	error	received ERR: read timeout for ccTimer.Friday
              ebus.0	2019-01-30 18:35:07.302	error	received ERR: read timeout for BankHolidayStartPeriod
              ebus.0	2019-01-30 18:35:03.507	error	received ERR: read timeout for BankHolidayEndPeriod
              ebus.0	2019-01-30 18:35:00.415	debug	received usage: read [-f] [-m SECONDS] [-s QQ] [-d ZZ] [-c CIRCUIT] [-p PRIO] [-v|-V] [-n|-N] [-i VALUE[;VALUE]*] NAME [FIELD[.N]] or: read [-f] [-m SECONDS] [-s QQ] [-d ZZ] [-v|-V] [-n|-N] [-i VAL
              ebus.0	2019-01-30 18:35:00.412	debug	telnet connected
              ebus.0	2019-01-30 18:35:00.412	debug	connect telnet to IP 192.168.243.41 port 8888
              ebus.0	2019-01-30 18:35:00.411	debug	to poll ctr 377 vals: ,BankHolidayEndPeriod,BankHolidayStartPeriod,ccTimer.Friday,ccTimer.Monday,ccTimer.Saturday,ccTimer.Sunday,ccTimer.Thursday,ccTimer.Tuesday,ccTimer.Wednesday,ContinuosHeating,cu
              ebus.0	2019-01-30 18:35:00.405	debug	init common variables
              ebus.0	2019-01-30 18:35:00.405	debug	init variables
              ebus.0	2019-01-30 18:35:00.405	debug	start with interface ebusd
              ebus.0	2019-01-30 18:35:00.405	debug	set timeout to 360 sec
              ebus.0	2019-01-30 18:35:00.405	info	starting. Version 0.7.0 in /opt/iobroker/node_modules/iobroker.ebus, node: v8.15.0
              host.srv-iobroker-dev	2019-01-30 18:35:00.008	info	instance system.adapter.ebus.0 started with pid 3940
              

              Blog: indibit.de

              1 Reply Last reply
              0
              • M Offline
                M Offline
                MGK
                wrote on last edited by
                #34

                Hallo zusammen,

                ich habe seit 2 Tagen nun auch den eBus Adapter am laufen, leider aber scheinbar nicht richtig.

                Auf der eBusd http Seite > [http://10.1.10.12:8889/data](http://10.1.10.12:8889/data) bekomme ich alle Daten angezeigt.
                19128_data.png

                Im ioBroker kommen aber nicht alle angezeigten Daten an bzw. nicht auf einmal oder immer noch nicht.

                In den letzten 2 Tagen kommen immer nach und nach mehr Daten an, aber bis jetzt leider immer noch nicht alle.
                19128_objekte.png

                Im Log sehe ich das der http Aufruf eigentlich immer ganz schnell beendet bzw. ab und zu auch gar nicht beendet wird.
                19128_log4.png

                Habt Ihr eine Idee woran das liegen kann?

                Grüße Matthias

                1 Reply Last reply
                0
                • N Offline
                  N Offline
                  NemoN
                  wrote on last edited by
                  #35

                  probiere doch einmal Version 0.4.2, mit den neueren Versionen habe ich auch Probleme…

                  1 Reply Last reply
                  0
                  • HiltexH Offline
                    HiltexH Offline
                    Hiltex
                    wrote on last edited by
                    #36

                    In der Github-Doku steht:
                    > All fields with data, lastup and from global section are parsed. All others are ignored at the moment.

                    Dein Screenshot von ebusd zeigt nur Datenpunkte, die noch nie aktualisiert wurden (lastup: 0 = Letztes Update: nie), daher werden die auch in ioBroker nicht angezeigt.

                    Wenn Du beispielsweise bai.messages.AATemp sehen willst, musst du diesen Datenpunkt in den Adaptereinstellungen hinterlegen. Dann wird der aktiv abgerufen und erscheint somit auch in ioBroker, wenn ein Ergebnis geliefert wird. Eintragen müsstest du einfach nur AATemp.

                    9433_bildschirmfoto_2019-02-08_um_16.22.40.png

                    Mir ist auch schon aufgefallen, dass andere (wahrscheinlich ältere) Anlagen viel mehr Datenpunkte broadcasten. Zumindest schlussfolgere ich das daraus, dass in älteren Beiträgen in diversen Foren selten ein Wort darüber verloren wird, dass man Datenpunkte aktiv abfragen muss. Bei meiner Therme kommt kaum etwas von alleine. Daher ist aktives polling gefragt.

                    Ich hab die Datenpunkte übrigens so ermittelt, dass ich mir die gesamten Datenpunkte von ebusd in eine Exceltabelle kopiert, mir dann vernünftige Listen daraus gebaut und sie immer blockweise abgefragt habe. Anschließend habe ich alle Datenpunkte entfernt, die statisch sind (z.B. AccessoriesOne und AccessoriesTwo), sowie alle, die für mich nicht zutreffen (z.B. Hc2 und Hc3 - ich habe nur einen Heizkreis). So kam ich dann zu meinem Set von den derzeitigen Datenpunkten.

                    Blog: indibit.de

                    1 Reply Last reply
                    0
                    • N Offline
                      N Offline
                      NemoN
                      wrote on last edited by
                      #37

                      Welche e-bus Komponenten (Brenner, Solar, etc) hast du bei deiner Anlage?

                      1 Reply Last reply
                      0
                      • HiltexH Offline
                        HiltexH Offline
                        Hiltex
                        wrote on last edited by
                        #38

                        Den Brenner und den Regler (VRC700). An die Solardaten komme ich irgendwie nicht ran, obwohl mir der Regler auch einen Ertrag anzeigt.

                        Blog: indibit.de

                        J 1 Reply Last reply
                        0
                        • N Offline
                          N Offline
                          NemoN
                          wrote on last edited by
                          #39

                          steht eigentlich im json ganz als letztes:

                             },
                             "YieldLastYear": {
                              "name": "YieldLastYear",
                              "passive": false,
                              "write": false,
                              "lastup": 0
                             },
                             "YieldThisYear": {
                              "name": "YieldThisYear",
                              "passive": false,
                              "write": false,
                              "lastup": 1549645270,
                              "zz": 21,
                              "fields": {
                               "0": {"name": "energy", "value": 0},
                               "1": {"name": "energy", "value": 0},
                               "2": {"name": "energy", "value": 0},
                               "3": {"name": "energy", "value": 0},
                               "4": {"name": "energy", "value": 0},
                               "5": {"name": "energy", "value": 0},
                               "6": {"name": "energy", "value": 0},
                               "7": {"name": "energy", "value": 0},
                               "8": {"name": "energy", "value": 0},
                               "9": {"name": "energy", "value": 0},
                               "10": {"name": "energy", "value": 0},
                               "11": {"name": "energy", "value": 0}
                              }
                          
                          

                          bei mir = 0 weil ich (noch) keinen ertragssensor angeschlossen habe…

                          1 Reply Last reply
                          0
                          • HiltexH Offline
                            HiltexH Offline
                            Hiltex
                            wrote on last edited by
                            #40

                            Die verfügbaren Datenpunkte variieren teils stark von Modell zu Modell.

                            Diese Datenpunkte gibt es bei mir garnicht, stattdessen nur SolarYieldTotal. Aber das meinte ich ja, den Ertrag bekomme ich angezeigt, aber die zugehörigen Messwerte nicht, beispielsweise den Volumenstrom oder den Wert des Temperaturfühlers, der da oben montiert ist.

                            Aber solange im ebusd-Log noch unbekannte Nachrichten auftauchen, ist auch klar, dass da durchaus noch Informationen da sind, die nur geparst werden müssten.

                            Blog: indibit.de

                            1 Reply Last reply
                            0
                            • M Offline
                              M Offline
                              MGK
                              wrote on last edited by
                              #41

                              @NemoN:

                              Bingo mit der Version 0.4.2 funktioniert der Import aller Daten auf Anhieb!

                              @Hiltex:

                              Die Github Doku hatte ich mir durch gelesen und es auch mit separaten Werten probiert, z.B. SensorData, welche aber auch dann nicht importiert worden.
                              19128_sensordata.png
                              Nun mit der Version 0.4.2 wird auch SensorData automatisch importiert, ohne separaten Aufruf.

                              Wie hast du damals bei deiner Suche nach Werte die möglichen Datenblöcken separat abgefragt, im ioBroker oder oder mit ebusd auf der Konsole?

                              Meine Anlage besteht aus, Gastherme (Ecotec Exclusive), VRC700, VR90, VR920, Solar und RecoVair 260.

                              Ich werde nun von der Version 0.4.2 nach oben durch testen, bis zu welcher Version der Import funktioniert.

                              L 1 Reply Last reply
                              0
                              • C Offline
                                C Offline
                                cactus-online
                                wrote on last edited by
                                #42

                                Hallo,

                                ich bin dankbar für diesen tollen Adapter (0.7.0). Ich habe jedoch noch "Probleme" mit dem Widget:

                                Das Auslesen der Rücklauftemperatur "ReturnTemp" meiner Vaillant Heizung liefert 3 Werte zurück 49.12;64749;ok (Rücklauftemperatur;tempmirror;Fühlerstatus). Leider entscheidet sich das Plugin für den letzten Zahlenwert als Wert für eine history-Variable. Stelle ich statt "ReturnTemp" "ReturnTemp temp.0" in der Konfiguration ein, dann kommt in der history-Variable nichts an. Alle Werte stehen in der Liste der Abzufragenden Datenpunkte und werden auch korrekt ausgelesen.

                                Log-Einträge:
                                ebus.0 2019-02-13 12:07:03.795 debug received 37.50 for ReturnTemp temp.0
                                ebus.0 2019-02-13 12:07:03.103 debug received 37.50;65002;ok for ReturnTemp

                                History Variablen:
                                value1 state
                                ebus history value 5 as JSON "ReturnTemp":"65002"

                                value2 state
                                ebus history value 6 as JSON

                                Was kann ich tun ?

                                Eine weitere Frage beschäftigt mich. Wofür steht in der Widget-Konfiguration "Zeitintervall:"? Egal was ich einstelle, es scheint sich nichts zu ändern.

                                VG,

                                TF

                                1 Reply Last reply
                                0
                                • Rene_HMR Rene_HM

                                  Unter https://github.com/rg-engineering/ioBroker.ebus habe ich die Version 0.7.0 gelegt. Dort ist der timeout im admin unter /ebusd einstellbar.

                                  Die Datenpunkte werden vom ebusd geholt. Also alles, was der ebusd hat, wird übertragen und in Datenpunkte überführt. Damit sollte es reichen, den ebusd auf dem Raspi neu zu starten und danach die Datenpunkte aus dem Objektbaum in iobroker löschen.

                                  HiltexH Offline
                                  HiltexH Offline
                                  Hiltex
                                  wrote on last edited by
                                  #43

                                  @Rene_HM Wäre es vielleicht möglich, das Loglevel von fehlgeschlagenen Leseversuchen von Error auf Warn zu setzen? Sporadisch sind bei immernoch bestimmte Werte nicht lesbar. Gern jedoch ein Error, wenn garnichts gelesen werden konnte 😉

                                  Blog: indibit.de

                                  1 Reply Last reply
                                  0
                                  • M Offline
                                    M Offline
                                    mameier1234
                                    wrote on last edited by
                                    #44

                                    ich merke gerade, dass ich wohl ein Problem habe...

                                    Adapter Version war 0.7.0

                                    system.adapter.ebus.0 2019-03-15 20:55:08.327 error schedule attribute missing
                                    system.adapter.ebus.0 2019-03-15 20:54:54.759 error schedule attribute missing

                                    Dann habe ich auf die 0.8.0 aktualisiert... gleiche Meldung ...

                                    any ideas ?

                                    Grüße,

                                    Martin

                                    1 Reply Last reply
                                    0
                                    • M Offline
                                      M Offline
                                      mameier1234
                                      wrote on last edited by
                                      #45

                                      Ok... selbst gefunden..

                                      In der Adapter Konfig hatte ich bei Zeitplanung nichts mehr drinn....

                                      Ich hatte das rausgenommen, da im Log immer drin stand "terminated" und dachte, dass das ein harter Abbruch wäre und nicht gut wäre, da man ja jetzt im Adapter einen Timeout setzen kann...

                                      Grüße,

                                      Martin

                                      O 1 Reply Last reply
                                      0
                                      • M mameier1234

                                        Ok... selbst gefunden..

                                        In der Adapter Konfig hatte ich bei Zeitplanung nichts mehr drinn....

                                        Ich hatte das rausgenommen, da im Log immer drin stand "terminated" und dachte, dass das ein harter Abbruch wäre und nicht gut wäre, da man ja jetzt im Adapter einen Timeout setzen kann...

                                        O Offline
                                        O Offline
                                        onkel-ede
                                        wrote on last edited by
                                        #46

                                        Hallo,
                                        was braucht es, um an die Daten eines Vaillant-Gerätes heranzukommen?
                                        Das zweipolige ebus-Kabel kommt aus meiner Wärmepumpe.
                                        Dieses würde ich auf einen eBus-Koppler-Ethernet (z.B. von esera) klemmen.
                                        Dann muss ich z.B. auf einem Raspi einen ebusd installieren (gibt es hierzu eine Anleitung?).
                                        Im iobroker installiere ich den ebus-Adapter und sprechen den ebusd mit der IP des Raspi an, auf dem der ebusd läuft.
                                        Oder kann ich beides auf einem Raspi laufen lassen?

                                        HiltexH 1 Reply Last reply
                                        0
                                        • O onkel-ede

                                          Hallo,
                                          was braucht es, um an die Daten eines Vaillant-Gerätes heranzukommen?
                                          Das zweipolige ebus-Kabel kommt aus meiner Wärmepumpe.
                                          Dieses würde ich auf einen eBus-Koppler-Ethernet (z.B. von esera) klemmen.
                                          Dann muss ich z.B. auf einem Raspi einen ebusd installieren (gibt es hierzu eine Anleitung?).
                                          Im iobroker installiere ich den ebus-Adapter und sprechen den ebusd mit der IP des Raspi an, auf dem der ebusd läuft.
                                          Oder kann ich beides auf einem Raspi laufen lassen?

                                          HiltexH Offline
                                          HiltexH Offline
                                          Hiltex
                                          wrote on last edited by
                                          #47

                                          @onkel-ede
                                          Das Prinzip hast du schon richtig erkannt. Eine Anleitung zu ebusd findest du im entsprechenden Github-Repository
                                          Grundsätzlich spricht nichts dagegen, ioBroker und ebusd auf einem Pi kaufen zu lassen, außer vielleicht die Performance.

                                          Blog: indibit.de

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          753

                                          Online

                                          32.4k

                                          Users

                                          81.4k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe