Test Adapter Vaillant multiMatic/senso und myVaillant
-
hier ein aktueller Debug Log , zur oben genannten Anfrage :
2020-10-10 20:41:22.028 - debug: javascript.0 (32035) system.adapter.admin.0: logging false 2020-10-10 20:41:29.426 - info: host.iobroker "system.adapter.vaillant.0" enabled 2020-10-10 20:41:29.566 - info: host.iobroker instance system.adapter.vaillant.0 started with pid 26383 2020-10-10 20:41:30.674 - debug: vaillant.0 (26383) Redis Objects: Use Redis connection: 127.0.0.1:9001 2020-10-10 20:41:30.726 - debug: vaillant.0 (26383) Objects client ready ... initialize now 2020-10-10 20:41:30.741 - debug: vaillant.0 (26383) Objects create System PubSub Client 2020-10-10 20:41:30.743 - debug: vaillant.0 (26383) Objects create User PubSub Client 2020-10-10 20:41:30.744 - debug: vaillant.0 (26383) Objects client initialize lua scripts 2020-10-10 20:41:30.784 - debug: vaillant.0 (26383) Objects connected to redis: 127.0.0.1:9001 2020-10-10 20:41:30.792 - debug: vaillant.0 (26383) objectDB connected 2020-10-10 20:41:30.794 - debug: vaillant.0 (26383) Redis States: Use Redis connection: 127.0.0.1:9000 2020-10-10 20:41:30.807 - debug: vaillant.0 (26383) States create User PubSub Client 2020-10-10 20:41:30.810 - debug: vaillant.0 (26383) States create System PubSub Client 2020-10-10 20:41:30.838 - debug: vaillant.0 (26383) States connected to redis: 127.0.0.1:9000 2020-10-10 20:41:30.839 - debug: vaillant.0 (26383) statesDB connected 2020-10-10 20:41:31.901 - info: vaillant.0 (26383) starting. Version 0.0.10 in /opt/iobroker/node_modules/iobroker.vaillant, node: v12.19.0, js-controller: 3.1.6 2020-10-10 20:41:31.931 - info: vaillant.0 (26383) Generate new Id 2020-10-10 20:41:32.282 - debug: vaillant.0 (26383) {"body":{"authToken":"XXXX EDIT TOKEN XXXX"},"meta":{}} 2020-10-10 20:41:32.283 - debug: vaillant.0 (26383) Login successful 2020-10-10 20:41:32.533 - debug: vaillant.0 (26383) Authentication successful 2020-10-10 20:41:32.534 - debug: vaillant.0 (26383) undefined 2020-10-10 20:41:32.698 - debug: vaillant.0 (26383) {"body":{"facilitiesList":[{"serialNumber":"XXXX EDIT Seriennummer XXXX","name":"Dorn","responsibleCountryCode":"DE","supportedBrand":"GREEN_BRAND_COMPATIBLE","capabilities":["ROOM_BY_ROOM","SYSTEMCONTROL_SENSO","SPINE"],"networkInformation":{"macAddressEthernet":"xx:xx:xx:xx:b1:bf","macAddressWifiAccessPoint":"xx:xx:xx:xx:b1:c0","macAddressWifiClient":"xx:xx:xx:xx:b1:c1"},"firmwareVersion":"357.20.7"}]},"meta":{}} 2020-10-10 20:41:32.748 - debug: vaillant.0 (26383) Get: status 2020-10-10 20:41:32.878 - debug: vaillant.0 (26383) status successful 2020-10-10 20:41:32.879 - debug: vaillant.0 (26383) {"body":{"onlineStatus":{"status":"ONLINE"},"firmwareUpdateStatus":{"status":"UPDATE_NOT_PENDING"},"facilityInstallationStatus":{"status":"NOT_INSTALLABLE"}},"meta":{}} 2020-10-10 20:41:33.479 - debug: javascript.0 (32035) system.adapter.admin.0: logging true 2020-10-10 20:41:33.480 - debug: vaillant.0 (26383) system.adapter.admin.0: logging true 2020-10-10 20:41:42.883 - debug: vaillant.0 (26383) Get: systemcontrol 2020-10-10 20:41:42.999 - debug: vaillant.0 (26383) "FACILITY_NOT_COMPATIBLE" 2020-10-10 20:41:43.003 - debug: vaillant.0 (26383) Failed to get systemcontrol 2020-10-10 20:41:53.003 - debug: vaillant.0 (26383) Get: livereport 2020-10-10 20:41:53.113 - debug: vaillant.0 (26383) livereport successful 2020-10-10 20:41:53.113 - debug: vaillant.0 (26383) {"body":{"devices":[{"reports":[{"unit":"bar","name":"Wasserdruck","value":1.4,"_id":"WaterPressureSensor","measurement_category":"PRESSURE","associated_device_function":"HEATING"}],"_id":"Control_SYS_senso","name":"sensoHOME"},{"reports":[{"unit":"°C","name":"Warmwassertemperatur Speicher","value":48.5,"_id":"DomesticHotWaterTankTemperature","measurement_category":"TEMPERATURE","associated_device_function":"DHW"}],"_id":"Control_DHW","name":"Warmwasserkreis"},{"reports":[{"unit":"°C","name":"Vorlauftemperaturfühler","value":44,"_id":"FlowTemperatureSensor","measurement_category":"TEMPERATURE","associated_device_function":"HEATING"}],"_id":"Control_CC1","name":"Heizkreis"}]},"meta":{"resourceState":[{"state":"SYNCED","timestamp":1602355308,"link":{"rel":"child","resourceLink":"/facilities/XXXX EDIT Seriennummer XXXX/livereport/v1/devices/Control_SYS_senso/reports/WaterPressureSensor"}},{"state":"SYNCED","timestamp":1602354946,"link":{"rel":"child","resourceLink":"/facilities/XXXX EDIT Seriennummer XXXX/livereport/v1/devices/Control_DHW/reports/DomesticHotWaterTankTemperature"}},{"state":"SYNCED","timestamp":1602354987,"link":{"rel":"child","resourceLink":"/facilities/XXXX EDIT Seriennummer XXXX/livereport/v1/devices/Control_CC1/reports/FlowTemperatureSensor"}}]}} 2020-10-10 20:42:03.124 - debug: vaillant.0 (26383) Get: spine 2020-10-10 20:42:03.311 - debug: vaillant.0 (26383) spine successful 2020-10-10 20:42:03.313 - debug: vaillant.0 (26383) {"body":{"currentPVMeteringInfo":{}},"meta":{}} 2020-10-10 20:42:03.315 - warn: vaillant.0 (26383) State value to set is invalid for vaillant.0.XXXX EDIT Seriennummer XXXX.spine.currentPVMeteringInfo: The state contains no properties! At least one property is expected! 2020-10-10 20:42:03.316 - warn: vaillant.0 (26383) This value will not be set in future versions. Please report this to the developer. 2020-10-10 20:42:13.318 - debug: vaillant.0 (26383) Get: emf 2020-10-10 20:42:13.499 - debug: vaillant.0 (26383) "NO_REPORT_ENABLED_DEVICES" 2020-10-10 20:42:13.500 - debug: vaillant.0 (26383) Failed to get emf 2020-10-10 20:42:22.652 - debug: vaillant.0 (26383) system.adapter.admin.0: logging false 2020-10-10 20:42:22.650 - debug: javascript.0 (32035) system.adapter.admin.0: logging false 2020-10-10 20:42:47.217 - debug: vaillant.0 (26383) system.adapter.admin.0: logging true -
Hallo ich habe den Adapter installiert jedoch habe ich eine andere Therme als der Entwickler.
Ich habe VR700/6 - VR71. Es werden Daten erzeugt.
Ich habe auf der Vaillant APP die Kreise Fussboden und Heizkörper, sowie Warmwasser und Zirkulation.
Wo finde ich diese DP im Adapter?
Gibt es zu dem Adapter ein WiKi oder so. Ich würde gerne die Daten verstehen.
Gruß
MichaelEDIT: Der Adapter wirft permanent einige Parameter durcheinander, wie Systemwasserdruck und einen VF.
Anbei mal zwei Screenshots, ich habe die entsprechenden Parameter markiert. Innerhalb von wenigen Minuten wechseln die Werte untereinander. Ebensfalls stelle ich bei den Objekten fest, dass immer wieder alle Ebenen ausgeklappt werden, egal ob ich den Objektordner geöffnet habe oder nicht.
Bild 1: 08:36 Uhr
Bild 2: 08:44 Uhr
Ich habe den Adapter bereits gelöscht und die V 0.1.0 wieder installiert, der Effekt bleibt der gleiche.
Gruß
Michael -
Hi alle
So, habe heute alles in Betrieb genommen ebenso diesen Adapter, was auch super funktioniert hat, jetzt wollte ich nur mal wissen was ihr so für VIS habt... Wäre der eine oder andere so nett (auch wenn es keine Vaillant ist) mal eure VIS zu zeigen? damit ich einen Ansatz hätte was ich wie darstellen kann?
danke -
Ich bekomme folgenden Eintrag im Log:
vaillant.0 2020-12-10 17:23:50.153 warn (3084766) This value will not be set in future versions. Please report this to the developer. vaillant.0 2020-12-10 17:23:50.151 warn (3084766) State value to set is invalid for vaillant.0.21204400202529220938031315N1.spine.currentPVMeteringInfo: The state contains no properties! At least one property is expected!Was ist hier zu tun?
-
@Tom-Son Der Erste Satz weißt auf zukünftige Weiterentwicklungen hin, kein To-Do
Der zweite Satz weißt auf eine Photo-Voltaic Anlage hin, hast du eine? -
@michihorn ah, ok... nein ich haben kein PV
-
Seit dem Update von js-controller bekomme ich den Adapter nicht mehr zum Laufen: (node: v12.20.1, js-controller: 3.2.7)
host.RaspberryPi 2021-01-17 19:13:19.347 error instance system.adapter.vaillant.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
vaillant.0 2021-01-17 19:13:18.777 warn (14585) Terminated (UNCAUGHT_EXCEPTION): Without reason
vaillant.0 2021-01-17 19:13:18.775 info (14585) terminating
vaillant.0 2021-01-17 19:13:18.773 info (14585) cleaned everything up...
vaillant.0 2021-01-17 19:13:18.730 error (14585) The state contains no properties! At least one property is expected!
vaillant.0 2021-01-17 19:13:18.729 error at Traverse.forEach (/opt/iobroker/node_modules/traverse/index.js:50:18)
vaillant.0 2021-01-17 19:13:18.729 error at walk (/opt/iobroker/node_modules/traverse/index.js:226:7)
vaillant.0 2021-01-17 19:13:18.729 error at walker (/opt/iobroker/node_modules/traverse/index.js:203:13)
vaillant.0 2021-01-17 19:13:18.729 error at forEach (/opt/iobroker/node_modules/traverse/index.js:298:31)
vaillant.0 2021-01-17 19:13:18.729 error at Array.forEach (<anonymous>)
vaillant.0 2021-01-17 19:13:18.729 error at /opt/iobroker/node_modules/traverse/index.js:208:29
vaillant.0 2021-01-17 19:13:18.729 error at walker (/opt/iobroker/node_modules/traverse/index.js:190:22)
vaillant.0 2021-01-17 19:13:18.729 error at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.vaillant/main.js:459:41)
vaillant.0 2021-01-17 19:13:18.729 error at Vaillant.setState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5897:21)
vaillant.0 2021-01-17 19:13:18.729 error at validateSetStateObjectArgument (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5783:23)
vaillant.0 2021-01-17 19:13:18.729 error (14585) Error: The state contains no properties! At least one property is expected!
vaillant.0 2021-01-17 19:13:18.723 error (14585) unhandled promise rejection: The state contains no properties! At least one property is expected!
vaillant.0 2021-01-17 19:13:18.721 error (14585) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by -
@massiveattack Bitte setze zukünftig den Code in </code tags>, dann wird es leserlich.
3.2.7 ist noch beta, Du solltest ein issue beim js-controller aufmachen. -
@meister-mopper Habe heute auch das update gemacht, wird ja vorgeschlagen
aber lt Post im Forum mit "has no existing Obeject..." sollte man das dem Entwickler meldenbei mir rennt der Adapter zwar, bekomme aber diese Meldungen:
vaillant.0 2021-01-17 19:22:29.430 warn (57240) Terminated (UNCAUGHT_EXCEPTION): Without reason vaillant.0 2021-01-17 19:22:29.427 info (57240) terminating vaillant.0 2021-01-17 19:22:29.425 info (57240) cleaned everything up... vaillant.0 2021-01-17 19:22:29.398 error (57240) The state contains no properties! At least one property is expected! vaillant.0 2021-01-17 19:22:29.398 error (57240) Error: The state contains no properties! At least one property is expected! at validateSetStateObjectArgument (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5783:23) vaillant.0 2021-01-17 19:22:29.395 error (57240) unhandled promise rejection: The state contains no properties! At least one property is expected! vaillant.0 2021-01-17 19:22:29.393 error (57240) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). vaillant.0 2021-01-17 19:22:09.172 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.dhw01.circulation.configuration.operationMode" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.165 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.dhw01.hotwater.configuration.temperature_setpoint" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.164 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.dhw01.hotwater.configuration.operation_mode" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.154 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.configuration.holidaymode.temperature_setpoint" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.153 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.configuration.holidaymode.end_date" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.152 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.configuration.holidaymode.start_date" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.151 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.configuration.holidaymode.active" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.151 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.configuration.eco_mode" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.150 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.configuration.quick_veto.setpoint_temperature" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.149 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.configuration.quick_veto.active" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.148 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.configuration.inside_temperature" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.147 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.configuration.active_function" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.147 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.configuration.enabled" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.145 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.configuration.name" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.137 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.heating.configuration.setpoint_temperature" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.136 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.heating.configuration.setback_temperature" has no existing object, this might lead to an error in future versions vaillant.0 2021-01-17 19:22:09.134 warn (57240) State "vaillant.0.21xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN1.systemcontrol.zones01.heating.configuration.mode" has no existing object, this might lead to an error in future versions -
@tom-son Kannst du mal über github installieren und schauen ob die Warnungen weg sind
-
@tombox drüber installieren? oder vorher de und dann wieder installieren?
-
@tom-son Einfach drüber installieren und instanze neustarten
-
@tombox OK, erledigt, sieht mal ruhig aus, auch mit Loglevel Info
-
sorry fürs schlechte format
wenn ich den adapter mit npm install iobroker.vaillant neu installieren will, bekomme ich auch Fehler:
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN pi No description npm WARN pi No repository field. npm WARN pi No README data npm WARN pi No license field. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.1 (node_modules/iobroker.js-controller/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.vaillant@0.0.10 added 2 packages from 2 contributors and audited 1013 packages in 13.969s 10 packages are looking for funding run `npm fund` for details found 25 vulnerabilities (22 low, 3 high) run `npm audit fix` to fix them, or `npm audit` for details pi@192.168.0.10:~$ sudo npm install iobroker.vaillant npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN pi No description npm WARN pi No repository field. npm WARN pi No README data npm WARN pi No license field. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) -
@massiveattack Ich sehe nur Warnungen, aber du bist im falschen Ordner. Du solltest nur über die admin oberfläche updaten oder über das github icon
-
@massiveattack
Hierrüber Installieren
-
@glasfaser
Besten Dank! Scheint nun stabil zu laufen, danke für die raschen Rückmeldungen -
Es scheint zwar alles ok zu sein, doch ich bekomme leider keine aktuellen Werte rein. Letzte Wertänderung ist vor der Neuinstallation.
Mit der Vaillant App kommen aktuelle Werte, also die Serverseite passt. Wie ist das bei euch? -
@massiveattack sagte in Test Adapter Vaillant multiMatic v0.0.x:
leider keine aktuellen Werte rein. Letzte Wertänderung ist vor der Neuinstallation.
Stelle den Adapter mal auf die Log-Stufe DEBUG , und poste dann das Ergebniss hier .
-
deleted...
