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

[AlCalzone]

@JungleFire Noch wird der originale dafür benötigt. Die Oberfläche gehe ich im nächsten Update an.

[stephan61]

Hallo AlCalzone
bekomme mit der 0.3 folgenden Fehler und der Adapter startet laufend neu

zwave2.0	2019-11-27 09:46:44.440	info	(6048) terminating
zwave2.0	2019-11-27 09:46:44.411	info	(6048) Cleaned everything up!
zwave2.0	2019-11-27 09:46:44.402	info	(6048) Shutting down driver...
zwave2.0	2019-11-27 09:46:44.401	error	at Timeout.saveToCacheTimer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zwave-js/build/lib/driver/Driver.js:1099:68)
zwave2.0	2019-11-27 09:46:44.401	error	at Driver.saveNetworkToCache (/opt/iobroker/node_modules/zwave-js/build/lib/driver/Driver.js:1107:21)
zwave2.0	2019-11-27 09:46:44.401	error	at Driver.saveNetworkToCacheInternal (/opt/iobroker/node_modules/zwave-js/build/lib/driver/Driver.js:1084:47)
zwave2.0	2019-11-27 09:46:44.401	error	at ZWaveController.serialize (/opt/iobroker/node_modules/zwave-js/build/lib/controller/Controller.js:593:70)
zwave2.0	2019-11-27 09:46:44.401	error	at Array.map (<anonymous>)
zwave2.0	2019-11-27 09:46:44.401	error	at nodes.objects_1.composeObject.map (/opt/iobroker/node_modules/zwave-js/build/lib/controller/Controller.js:593:111)
zwave2.0	2019-11-27 09:46:44.401	error	at ZWaveNode.serialize (/opt/iobroker/node_modules/zwave-js/build/lib/node/Node.js:946:18)
zwave2.0	2019-11-27 09:46:44.401	error	at Array.map (<anonymous>)
zwave2.0	2019-11-27 09:46:44.401	error	at commandClasses.objects_1.composeObject.sort.map (/opt/iobroker/node_modules/zwave-js/build/lib/node/Node.js:951:41)
zwave2.0	2019-11-27 09:46:44.401	error	at ZWaveNode.createCCInstance (/opt/iobroker/node_modules/zwave-js/build/lib/node/Endpoint.js:154:19)
zwave2.0	2019-11-27 09:46:44.401	error	(6048) Error: Cannot create an instance of the unsupported CC Basic (0x20)
zwave2.0	2019-11-27 09:46:44.401	error	(6048) uncaught exception: Cannot create an instance of the unsupported CC Basic (0x20)
zwave2.0	2019-11-27 09:46:43.640	info	(6048) Node 1: interview completed
zwave2.0	2019-11-27 09:46:43.570	info	(6048) The driver is ready. Found 5 nodes.
zwave2.0	2019-11-27 09:46:42.724	info	(6048) starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.zwave2, node: v10.17.0

Gruss Stephan
bin erstmal auf 0. 2.1 zurück

[AlCalzone]

@stephan61 Kannst du mir bitte deine Cache-Datei schicken?

/opt/iobroker/node_modules/zwave-js/cache/<irgendwas>.json

[stephan61]

Hallo AlCalzone anbei die cache datei f72e307b.json

Gruß Stephan

[AlCalzone]

@stephan61 Bitte teste mal v0.3.1, sollte in Kürze verfügbar sein.

[stephan61]

Hallo mit 0.3.1 kommt keine Fehlermeldung
Danke

[stephan61]

Hallo AlCalzone
bekomme leider immernoch Fehlermeldungen
alle 2 Stunden kommt folgender Fehler

2019-11-28 08:04:22.979  - info: zwave2.0 (23350) Node 2: is now awake
2019-11-28 08:04:23.536  - error: zwave2.0 (23350) uncaught exception: Cannot read property 'toUpperCase' of undefined
2019-11-28 08:04:23.536  - error: zwave2.0 (23350) TypeError: Cannot read property 'toUpperCase' of undefined
    at str.split.map (/opt/iobroker/node_modules/iobroker.zwave2/src/lib/objects.ts:45:17)
    at Array.map (<anonymous>)
    at camelCase (/opt/iobroker/node_modules/iobroker.zwave2/src/lib/objects.ts:42:4)
    at nameToStateId (/opt/iobroker/node_modules/iobroker.zwave2/src/lib/objects.ts:36:9)
    at Object.computeId (/opt/iobroker/node_modules/iobroker.zwave2/src/lib/objects.ts:60:33)
    at Zwave2.onNodeMetadataUpdated (/opt/iobroker/node_modules/iobroker.zwave2/src/main.ts:180:22)
    at ZWaveNode.emit (events.js:198:13)
    at ZWaveNode.translateValueEvent (/opt/iobroker/node_modules/zwave-js/build/lib/node/Node.js:128:18)
    at ValueDB.emit (events.js:198:13)
    at ValueDB.setMetadata (/opt/iobroker/node_modules/zwave-js/build/lib/node/ValueDB.js:108:18)
2019-11-28 08:04:23.538  - info: zwave2.0 (23350) Shutting down driver...
2019-11-28 08:04:23.637  - info: zwave2.0 (23350) Cleaned everything up!
2019-11-28 08:04:23.659  - info: zwave2.0 (23350) terminating
2019-11-28 08:04:23.662  - info: zwave2.0 (23350) Terminated (NO_ERROR): Without reason

Node 2 ist ein FGMS001 Motion Sensor

Gruß Stephan

[AlCalzone]

@stephan61 Danke für den Report! v0.3.2 (in ein paar Minuten verfügbar) sollte das fixen.

[stephan61]

Hallo Alcazone habe einen Fehler gefunden
wenn ich bei node 3 Fibaro flood fsgs 101
unter configuration zwave2.0.Node_003.Configuration.typeAlarmFrameSentTo1-stAssocGroup änder e habe ich nur 0 und 255 zur auswahl stimmt so weit bei dem wert 255 kommt folgender Fehler

host.proiobroker	2019-11-30 17:46:30.285	info	instance system.adapter.zwave2.0 terminated with code 0 (NO_ERROR)
host.proiobroker	2019-11-30 17:46:30.284	error	Caught by controller[0]: at processImmediate (timers.js:658:5)
host.proiobroker	2019-11-30 17:46:30.284	error	Caught by controller[0]: at tryOnImmediate (timers.js:676:5)
host.proiobroker	2019-11-30 17:46:30.283	error	Caught by controller[0]: at runCallback (timers.js:705:18)
host.proiobroker	2019-11-30 17:46:30.282	error	Caught by controller[0]: at Immediate.setImmediate (/opt/iobroker/node_modules/zwave-js/build/lib/driver/Driver.js:930:33)
host.proiobroker	2019-11-30 17:46:30.282	error	Caught by controller[0]: at Driver.workOffSendQueue (/opt/iobroker/node_modules/zwave-js/build/lib/driver/Driver.js:987:30)
host.proiobroker	2019-11-30 17:46:30.282	error	Caught by controller[0]: at SendDataRequest.serialize (/opt/iobroker/node_modules/zwave-js/build/lib/controller/SendDataMessages.js:61:43)
host.proiobroker	2019-11-30 17:46:30.281	error	Caught by controller[0]: at ConfigurationCCSet.serialize (/opt/iobroker/node_modules/zwave-js/build/lib/commandclass/ConfigurationCC.js:700:13)
host.proiobroker	2019-11-30 17:46:30.281	error	Caught by controller[0]: at serializeValue (/opt/iobroker/node_modules/zwave-js/build/lib/commandclass/ConfigurationCC.js:1139:21)
host.proiobroker	2019-11-30 17:46:30.279	error	Caught by controller[0]: at Buffer.writeIntBE (internal/buffer.js:701:12)
host.proiobroker	2019-11-30 17:46:30.278	error	Caught by controller[0]: at writeU_Int8 (internal/buffer.js:555:11)
host.proiobroker	2019-11-30 17:46:30.274	error	Caught by controller[0]: RangeError [ERR_OUT_OF_RANGE]: The value of "value" is out of range. It must be >= -128 and <= 127. Received 255
zwave2.0	2019-11-30 17:46:29.699	info	(12313) Terminated (NO_ERROR): Without reason


[AlCalzone]

@stephan61 Verdammt, du bist gut! Das ist ein grundlegendes Problem, das ich bisher nicht bedacht hatte. Muss mal überlegen, wie ich es am besten löse.

[AlCalzone]

@stephan61 In Kürze ist v0.3.3 verfügbar, die sich daran nicht mehr verschlucken sollte.

[AlCalzone]

Hier gehts weiter:
https://forum.iobroker.net/topic/27592/test-adapter-zwave2-v0-4-x