Hallo,
habe heute versucht den Adapter (Version 2.3.1) zu installieren und ans laufen zu bringen. Installation war kein Problem, laufen geht grundsätzlich auch, aber keine Verbindung über die Web API.
Grundsätzliche Frage: Kann man den Adapter auch verwenden wenn der ioBroker und das Nuki in zwei völlig unterschiedlichen Netzen sind und der Zugriff nur über die Web API laufen soll?
Wenn ich unter den "Verbindungseinstellungen für die Nuki Bridge" gar nichts eintrage und bei "Verbindungseinstellungen der Nuki Smart Locks (optional)" den im NukiWeb generierten API Key eingebe, springt die Instanz auf gelb (Verbunden mit Host (grün), Lebenszeichen (grün), Verbunden mit Gerät oder Dienst (rot)). Im Log ist dann folgendes:

nuki-extended.0	2021-11-13 13:10:24.300	warn	No bridges have been defined in settings so far!
nuki-extended.0	2021-11-13 13:10:24.198	info	starting. Version 2.3.1 in /opt/iobroker/node_modules/iobroker.nuki-extended, node: v12.22.6, js-controller: 3.3.18
nuki-extended.0	2021-11-13 13:10:23.636	debug	statesDB connected
nuki-extended.0	2021-11-13 13:10:23.635	debug	States connected to redis: 127.0.0.1:9000
nuki-extended.0	2021-11-13 13:10:23.626	debug	States create User PubSub Client
nuki-extended.0	2021-11-13 13:10:23.625	debug	States create System PubSub Client
nuki-extended.0	2021-11-13 13:10:23.615	debug	Redis States: Use Redis connection: 127.0.0.1:9000
nuki-extended.0	2021-11-13 13:10:23.612	debug	objectDB connected
nuki-extended.0	2021-11-13 13:10:23.601	debug	Objects connected to redis: 127.0.0.1:9001
nuki-extended.0	2021-11-13 13:10:23.585	debug	Objects client initialize lua scripts
nuki-extended.0	2021-11-13 13:10:23.584	debug	Objects create User PubSub Client
nuki-extended.0	2021-11-13 13:10:23.582	debug	Objects create System PubSub Client
nuki-extended.0	2021-11-13 13:10:23.580	debug	Objects client ready ... initialize now
nuki-extended.0	2021-11-13 13:10:23.486	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
nuki-extended.0	2021-11-13 13:10:18.537	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
nuki-extended.0	2021-11-13 13:10:18.536	info	terminating
nuki-extended.0	2021-11-13 13:10:18.535	info	Adapter stopped und unloaded.
nuki-extended.0	2021-11-13 13:10:18.533	info	Got terminate signal TERMINATE_YOURSELF

Wenn ich dann eine fiktiven Bridge in meinem Netz erstelle, in der Hoffnung, dass diese nicht gefunden wird und dann das Fallback auf WebAPI greift bekomme ich folgende Log Meldungen:

nuki-extended.0	2021-11-13 13:20:36.164	warn	No bridges are sufficiently defined! Name, IP or token missing or all bridges deactivated!
nuki-extended.0	2021-11-13 13:20:36.162	debug	Error retrieving callbacks ({"name":"RequestError","code":"EHOSTUNREACH","timings":{"start":1636806033295,"socket":1636806033296,"error":1636806036161,"phases":{"wait":1,"total":2866}}})!
nuki-extended.0	2021-11-13 13:20:33.042	debug	getBridgeApi(): connect EHOSTUNREACH 192.168.1.248:8080
nuki-extended.0	2021-11-13 13:20:33.042	warn	Failed retrieving /info from Nuki Bridge with name FiktiveBridge (forcePlainToken: true)!
nuki-extended.0	2021-11-13 13:20:29.924	debug	_getTokenParams(): {"token":"1234567890"}
nuki-extended.0	2021-11-13 13:20:29.923	debug	getBridgeApi(): connect EHOSTUNREACH 192.168.1.248:8080
nuki-extended.0	2021-11-13 13:20:29.922	warn	Failed retrieving /list from Nuki Bridge with name FiktiveBridge (forcePlainToken: true)!
nuki-extended.0	2021-11-13 13:20:23.514	info	starting. Version 2.3.1 in /opt/iobroker/node_modules/iobroker.nuki-extended, node: v12.22.6, js-controller: 3.3.18
nuki-extended.0	2021-11-13 13:20:23.306	debug	statesDB connected
nuki-extended.0	2021-11-13 13:20:23.305	debug	States connected to redis: 127.0.0.1:9000
nuki-extended.0	2021-11-13 13:20:23.296	debug	States create User PubSub Client
nuki-extended.0	2021-11-13 13:20:23.295	debug	States create System PubSub Client
nuki-extended.0	2021-11-13 13:20:23.286	debug	Redis States: Use Redis connection: 127.0.0.1:9000
nuki-extended.0	2021-11-13 13:20:23.283	debug	objectDB connected
nuki-extended.0	2021-11-13 13:20:23.274	debug	Objects connected to redis: 127.0.0.1:9001
nuki-extended.0	2021-11-13 13:20:23.259	debug	Objects client initialize lua scripts
nuki-extended.0	2021-11-13 13:20:23.258	debug	Objects create User PubSub Client
nuki-extended.0	2021-11-13 13:20:23.256	debug	Objects create System PubSub Client
nuki-extended.0	2021-11-13 13:20:23.229	debug	Objects client ready ... initialize now
nuki-extended.0	2021-11-13 13:20:22.993	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
nuki-extended.0	2021-11-13 13:20:18.062	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
nuki-extended.0	2021-11-13 13:20:18.060	info	terminating
nuki-extended.0	2021-11-13 13:20:18.059	info	Adapter stopped und unloaded.
nuki-extended.0	2021-11-13 13:20:18.057	info	Got terminate signal TERMINATE_YOURSELF

Bei Erstellung einer fiktiven Bridge in einem fiktiven privaten Netz kommen diese Meldungen:

nuki-extended.0	2021-11-13 13:25:49.218	info	starting. Version 2.3.1 in /opt/iobroker/node_modules/iobroker.nuki-extended, node: v12.22.6, js-controller: 3.3.18
nuki-extended.0	2021-11-13 13:25:48.994	debug	statesDB connected
nuki-extended.0	2021-11-13 13:25:48.993	debug	States connected to redis: 127.0.0.1:9000
nuki-extended.0	2021-11-13 13:25:48.984	debug	States create User PubSub Client
nuki-extended.0	2021-11-13 13:25:48.983	debug	States create System PubSub Client
nuki-extended.0	2021-11-13 13:25:48.953	debug	Redis States: Use Redis connection: 127.0.0.1:9000
nuki-extended.0	2021-11-13 13:25:48.949	debug	objectDB connected
nuki-extended.0	2021-11-13 13:25:48.938	debug	Objects connected to redis: 127.0.0.1:9001
nuki-extended.0	2021-11-13 13:25:48.894	debug	Objects client initialize lua scripts
nuki-extended.0	2021-11-13 13:25:48.893	debug	Objects create User PubSub Client
nuki-extended.0	2021-11-13 13:25:48.891	debug	Objects create System PubSub Client
nuki-extended.0	2021-11-13 13:25:48.886	debug	Objects client ready ... initialize now
nuki-extended.0	2021-11-13 13:25:48.679	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
nuki-extended.0	2021-11-13 13:25:43.740	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
nuki-extended.0	2021-11-13 13:25:43.738	info	terminating
nuki-extended.0	2021-11-13 13:25:43.737	info	Adapter stopped und unloaded.
nuki-extended.0	2021-11-13 13:25:43.735	info	Got terminate signal TERMINATE_YOURSELF

Hier tauchen scheinbar keine Fehler auf, aber es bleibt die Instanz trotzdem gelb, da der Punkt "Verbunden mit Gerät oder Dienst" weiterhin rot ist.
Gibt es hierzu Lösungsvorschläge, habe ich Denk- oder Verständnisfehler, oder geht das einfach so nicht? Freue mich auf Unterstützung!
Gruß Meinolf

@bug77
Wie geht es denn? Würde mich auch interessieren.

Hier noch das Blockly für Interessierte:

@Asgothian
So endlich bin ich auch mal zum echten testen gekommen. Also ja es funktioniert alles wie es soll.
Habe nen kleines Blockly geschrieben. Die Schrittwerte für die Lautstärke muss man überlegen wie man die haben will. Bei 1 muss man schon sehr viel drehen, damit sich wahrnehmbar was verändert.
Wegen Pull-Request auf Github. Kannst Du das machen. Ich habe gar keinen Github Account und ehrlich gesagt auch noch nicht richtig verstanden (nach Anleitungen lesen) wie das dann geht.
Müsste nur vorher in deinem Fork noch das geändert werden:
Allerdings habe ich in der devices.js eins der doppelten states.button_action_skip_forward durch ein states.button_action_skip_back ersetzt.
Danke.

@Asgothian
Habe die beiden Dateien angepasst. Scheint zu gehen!
Allerdings habe ich in der devices.js eins der doppelten states.button_action_skip_forward durch ein states.button_action_skip_back ersetzt. In der states.js war das ja schon generisch definiert.
Probiere morgen weiter und dann mal ne echte Steuerung per Blockly.
Danke!

@Asgothian
Batteriestatus hat jetzt einen Wert. Wird wahrscheinlich nur selten übertragen.
Inwieweit sich die Logeinträge per copy/paste eignen kann ich nicht beurteilen, da die eigentlichen Einträge teilweise viel viel läger sind (mouse over) (oder consolenlog)

zigbee.0	2020-02-11 22:50:07.930	debug	(9688) Publish {"action":"skip_backward","step_size":1,"transition_time":0}
zigbee.0	2020-02-11 22:50:07.929	debug	(9688) Type commandStep device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:07.929	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStep', cluster 'genLevelCtrl', data '{"stepmode":1,"stepsize":1,"transtime":0}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:07.928	debug	(9688) handleMessage. {"type":"commandStep","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:07.923	debug	(9688) Publish {"action":"skip_backward","step_size":1,"transition_time":0}
zigbee.0	2020-02-11 22:50:07.922	debug	(9688) Type commandStep device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:07.922	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStep', cluster 'genLevelCtrl', data '{"stepmode":1,"stepsize":1,"transtime":0}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:07.921	debug	(9688) handleMessage. {"type":"commandStep","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:05.209	debug	(9688) Publish {"action":"skip_forward","step_size":1,"transition_time":0}
zigbee.0	2020-02-11 22:50:05.208	debug	(9688) Type commandStep device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:05.207	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStep', cluster 'genLevelCtrl', data '{"stepmode":0,"stepsize":1,"transtime":0}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:05.206	debug	(9688) handleMessage. {"type":"commandStep","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:05.200	debug	(9688) Publish {"action":"skip_forward","step_size":1,"transition_time":0}
zigbee.0	2020-02-11 22:50:05.199	debug	(9688) Type commandStep device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:05.198	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStep', cluster 'genLevelCtrl', data '{"stepmode":0,"stepsize":1,"transtime":0}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:05.197	debug	(9688) handleMessage. {"type":"commandStep","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:03.172	debug	(9688) Publish {"action":"play_pause"}
zigbee.0	2020-02-11 22:50:03.171	debug	(9688) Type commandToggle device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID"
zigbee.0	2020-02-11 22:50:03.170	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:03.169	debug	(9688) handleMessage. {"type":"commandToggle","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
zigbee.0	2020-02-11 22:50:03.162	debug	(9688) Publish {"action":"play_pause"}
zigbee.0	2020-02-11 22:50:03.162	debug	(9688) Type commandToggle device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID"
zigbee.0	2020-02-11 22:50:03.161	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:03.160	debug	(9688) handleMessage. {"type":"commandToggle","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
zigbee.0	2020-02-11 22:50:01.088	debug	(9688) Publish {"action":"rotate_stop","brightness":253}
zigbee.0	2020-02-11 22:50:01.086	debug	(9688) Type commandStop device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:01.086	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStop', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:01.085	debug	(9688) handleMessage. {"type":"commandStop","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:01.079	debug	(9688) Publish {"action":"rotate_stop","brightness":253}
zigbee.0	2020-02-11 22:50:01.078	debug	(9688) Type commandStop device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:01.077	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStop', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:01.077	debug	(9688) handleMessage. {"type":"commandStop","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:01.034	debug	(9688) Publish {"action":"rotate_right","brightness":248}
zigbee.0	2020-02-11 22:50:00.833	debug	(9688) Publish {"action":"rotate_right","brightness":248}
zigbee.0	2020-02-11 22:50:00.633	debug	(9688) Publish {"action":"rotate_right","brightness":228}
zigbee.0	2020-02-11 22:50:00.433	debug	(9688) Publish {"action":"rotate_right","rate":195}
zigbee.0	2020-02-11 22:50:00.432	debug	(9688) Type commandMove device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:00.431	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":0,"rate":195}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:00.430	debug	(9688) handleMessage. {"type":"commandMove","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:00.422	debug	(9688) Publish {"action":"rotate_right","rate":195}
zigbee.0	2020-02-11 22:50:00.422	debug	(9688) Type commandMove device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:00.421	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":0,"rate":195}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:00.420	debug	(9688) handleMessage. {"type":"commandMove","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:00.379	debug	(9688) Publish {"action":"rotate_stop","brightness":208}
zigbee.0	2020-02-11 22:50:00.378	debug	(9688) Type commandStop device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:00.377	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStop', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:00.376	debug	(9688) handleMessage. {"type":"commandStop","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:00.371	debug	(9688) Publish {"action":"rotate_stop","brightness":208}
zigbee.0	2020-02-11 22:50:00.370	debug	(9688) Type commandStop device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:50:00.369	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandStop', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:50:00.369	debug	(9688) handleMessage. {"type":"commandStop","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:50:00.298	debug	(9688) Publish {"action":"rotate_left","brightness":215}
zigbee.0	2020-02-11 22:50:00.098	debug	(9688) Publish {"action":"rotate_left","brightness":235}
zigbee.0	2020-02-11 22:49:59.898	debug	(9688) Publish {"action":"rotate_left","rate":195}
zigbee.0	2020-02-11 22:49:59.896	debug	(9688) Type commandMove device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:49:59.895	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":1,"rate":195}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:49:59.895	debug	(9688) handleMessage. {"type":"commandMove","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
zigbee.0	2020-02-11 22:49:59.888	debug	(9688) Publish {"action":"rotate_left","rate":195}
zigbee.0	2020-02-11 22:49:59.886	debug	(9688) Type commandMove device {"type":"device","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
zigbee.0	2020-02-11 22:49:59.885	debug	(9688) Received Zigbee message from '0xccccccfffea8b045', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":1,"rate":195}' from endpoint 1 with groupID 0
zigbee.0	2020-02-11 22:49:59.884	debug	(9688) handleMessage. {"type":"commandMove","device":{"ID":8,"_type":"EndDevice","_ieeeAddr":"0xccccccfffea8b045","_networkAddress":36520,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"

Also da kommen ja alle Aktionen an:
Publish {"action":"rotate_left","brightness":235}
Publish {"action":"rotate_right","rate":195}
Publish {"action":"rotate_stop","brightness":253}
Publish {"action":"play_pause"} (1 Klick)
Publish {"action":"skip_forward","step_size":1,"transition_time":0} (2 Klick)
Publish {"action":"skip_backward","step_size":1,"transition_time":0} (3 Klick)
Beim Objekt gibt es aber nur diese Status:

Die Log-Meldungen "handleMessage" und vor allem die "Type commandStep device" sind ewig lang. Vielleicht besser wenn benötigt aus dem Consolenlog als File anhängen?!

@Asgothian
Vielen Dank!
Es geht! Ich habe allerdings nicht den gesamten Fork genommen, sondern nur das Bild und die Ergänzungen in den beiden Scriptdateien. Sonst war doch nichts anzupassen, oder?
Was noch nicht geht sind die im Original vorgesehenen Funktionen je nach Druckanzahl:

Also klar, dass die Reaktion was geschehen soll gescriptet werden muss, aber es gibt halt nur ein "true" bei Doppelklick. Die anderen beiden sind ohne Status.
Muss da noch nen Verweis auf "button_action_skip_back" in der devices.js ergänzt werden? Aber dann fehlt ja immer noch der Einfachklick. Ich habe die Systematik der beiden Dateien noch nicht durchdrungen.

Die Batterieanzeige scheint auch noch nicht sauber zu laufen, da Sie dauerhaft auf 0% steht.
Aber nochmal vielen Dank, ist ja schon ein großer Schritt weiter.
Aber liegt das doch alles daran, dass ich nicht den gesamten Fork übernommen habe...?

@Asgothian said in SYMFONISK Sound Controller Zigbee Error:

Der Controller ist in der Zigbee-herdsman-converters Bibliothek bekannt und kann (verhältnismässig einfach) im Zigbee Adapter integriert werden.

Welche Version des Zigbee Adapters nutzt du ?

A.

Wie oben geschrieben die github Version 1.0.3
Bekomme ich das dann selber mit eurer Hilfe hin?

Hallo ich habe den Zigbee Adaper Version 1.0.3 installiert.
Beim Koppeln des SYMFONISK Sound Controller von Ikea funktioniert aus meiner Sicht die Kopplung einwandfrei:

New device joined '0xccccccfffea8b045' model SYMFONISK Sound Controller
Interview successful: {"friendly_name":"0xccccccfffea8b045","model":"E1744","vendor":"IKEA","description":"SYMFONISK sound controller","supported":true}
Pairing time left
Pairing time left: 1
.
Pairing time left: 18
Device '0xccccccfffea8b045' announced itself
Pairing time left: 19
Pairing time left: 20
Interview started: 0xccccccfffea8b045
Pairing time left: 21
.
Pairing time left: 90
Pairing started all

Der Controller taucht auch in der Zigbee Instanzen Konfiguration richtig mit allen Infos und grünem Haken als Gerät auf (nur kein Bild)
Details:
model:E1744
vendor:IKEA
description:SYMFONISK sound controller
supports:volume up/down, play/pause, skip forward/backward
model:SYMFONISK Sound Controller
type:EndDevice
nwk:36520
manuf id:4476
manufacturer:IKEA of Sweden
power:Battery
app version:33
hard version:1
zcl version:3
stack version:98
date code:20190312
build:2.1.022
interviewed:true
configured:true
endpoint:1
profile:260
input clusters:0,1,3,32,4096
output clusters:3,4,6,8,25,4096

Unter den Objekten taucht der Controller jedoch nicht auf und wenn ich ihn benutze kommt folgende Fehlermeldung im Log:

(6231) Device ccccccfffea8b045 "SYMFONISK Sound Controller" not described in statesMapping.

Was habe ich ggf. falsch gemacht oder übersehen? Oder ist der Controller noch nicht vollständig im Adapter supported? Bekannt ist er ja aber schon.
Freue mich über jeden Hinweis oder Tipps wie man ihn ggf. selber im Adapter sauber integrieren kann.
Oder fehlen Infos zum Controller und es wäre hilfreich über die Zigbee-Adapter Analyse zur Integration durch den/die Maintainer beizutragen?