UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Meister Mopper]

@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.

[Tom Son]

@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 melden

bei 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

[tombox]

@tom-son Kannst du mal über github installieren und schauen ob die Warnungen weg sind

[Tom Son]

@tombox drüber installieren? oder vorher de und dann wieder installieren?

[tombox]

@tom-son Einfach drüber installieren und instanze neustarten

[Tom Son]

@tombox OK, erledigt, sieht mal ruhig aus, auch mit Loglevel Info

[MassiveAttack]

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"})

[tombox]

@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

[Glasfaser]

@massiveattack
Hierrüber Installieren

[MassiveAttack]

@glasfaser
Besten Dank! Scheint nun stabil zu laufen, danke für die raschen Rückmeldungen :)

[MassiveAttack]

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?

[Glasfaser]

@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 .

[MassiveAttack]

@glasfaser

deleted...

[Glasfaser]

@massiveattack
Log ist für @tombox

Setze den Log in Code-Tags </>

[tombox]

@massiveattack Lösche bitte den log und schicke mir das per PN.

[MassiveAttack]

@glasfaser
sry, done :)

[Tom Son]

@massiveattack
Habe gleiches Problem, seit dem update gestern kommen keine Werte mehr rein, habt ihr schon was gefunden? Neuesten Adapter habe ich via Github schon installiert...

[tombox]

@tom-son Habe das problem gefunden und behoben

[MassiveAttack]

@tombox
super, danke dir, läuft wieder alles :)

[Tom Son]

@tombox OK, super... was ist zu tun? Adapter wieder von Github drüber installieren?