stimmt, kann man zuschauen !!!!
nochmal unendlichen dank, das ist mal forum auf 150%
jetzt erstmal ein cheers
stimmt, kann man zuschauen !!!!
nochmal unendlichen dank, das ist mal forum auf 150%
jetzt erstmal ein cheers
hi ja ich habe das mittels Skripten (anders ist die Logik m.E. nicht abbildbar) hinbekommen.... anschließend ist der hmip-broll mit cloud-accesspoint auch in yahka / HomeKit verwendbar
Skript-Blockly sieht beispielhaft (auf eigene Installation anzupassen) für einen Rolladen wie folgt aus
yahka dann wie folgt
das funktioniert bei mir einwandfrei mit Status anzeige öffnen/schließen in HomeKit
@thomas-braun natürlich nicht sry. geht nicht alles so schnell
das sich an der Namensgebung der gerate gestört wird, sehe ich selbst..... wundere mich nur warum es vorhin noch ging
reicht es aus alles umzubenennen?!
2025-05-06 12:52:23.456 - info: yahka.0 (2824) publishing bridge yahka on 0.0.0.0 using bonjour-hap
2025-05-06 12:52:23.464 - info: yahka.0 (2824) publishing device DG-Schlafzimmer Fernseher on 0.0.0.0 using avahi
2025-05-06 12:52:23.759 - info: yahka.0 (2824) publishing device OG-Wohnzimmer Fernseher on 0.0.0.0 using avahi
2025-05-06 12:52:23.823 - error: yahka.0 (2824) 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().
2025-05-06 12:52:23.824 - error: yahka.0 (2824) unhandled promise rejection: EISDIR: illegal operation on a directory, read
2025-05-06 12:52:24.185 - error: yahka.0 (2824) Error: EISDIR: illegal operation on a directory, read
at Object.readFileSync (node:fs:449:20)
at LocalStorage.parseDirSync (/opt/iobroker/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:637:35)
at LocalStorage.parseDataDirSync (/opt/iobroker/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:572:21)
at LocalStorage.initSync (/opt/iobroker/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:145:14)
at HAPStorage.storage (/opt/iobroker/node_modules/hap-nodejs/src/lib/model/HAPStorage.ts:28:25)
at Function.storage (/opt/iobroker/node_modules/hap-nodejs/src/lib/model/HAPStorage.ts:16:26)
at Function.load (/opt/iobroker/node_modules/hap-nodejs/src/lib/model/AccessoryInfo.ts:278:30)
at Bridge.publish (/opt/iobroker/node_modules/hap-nodejs/src/lib/Accessory.ts:1126:41)
at devicesToPublish (/opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:34:35)
at /opt/iobroker/node_modules/iobroker.yahka/webpack:/yahka.homekit-bridge.ts:77:41
2025-05-06 12:52:24.186 - error: yahka.0 (2824) Exception-Code: EISDIR: EISDIR: illegal operation on a directory, read
2025-05-06 12:52:24.235 - info: yahka.0 (2824) cleaning up ...
2025-05-06 12:52:24.236 - info: yahka.0 (2824) cleaned up ...
2025-05-06 12:52:24.238 - info: yahka.0 (2824) terminating
2025-05-06 12:52:24.240 - warn: yahka.0 (2824) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-05-06 12:52:24.745 - info: yahka.0 (2824) terminating
2025-05-06 12:52:24.875 - error: host.buanet-iobroker1 Caught by controller[0]: HAP-NodeJS WARNING: The accessory 'DG-Schlafzimmer Ventilator' has an invalid 'Name' characteristic ('DG-Schlafzimmer Ventilator'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.875 - error: host.buanet-iobroker1 Caught by controller[1]: HAP-NodeJS WARNING: The accessory 'DG-Schlafzimmer Ventilator' has an invalid 'Name' characteristic ('DG-Schlafzimmer Ventilator'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.876 - error: host.buanet-iobroker1 Caught by controller[2]: HAP-NodeJS WARNING: The accessory 'OG-Wohnzimmer Stehlampe' has an invalid 'Name' characteristic ('OG-Wohnzimmer Stehlampe'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.877 - error: host.buanet-iobroker1 Caught by controller[3]: HAP-NodeJS WARNING: The accessory 'OG-Wohnzimmer Stehlampe' has an invalid 'Name' characteristic ('OG-Wohnzimmer Stehlampe'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.877 - error: host.buanet-iobroker1 Caught by controller[4]: HAP-NodeJS WARNING: The accessory 'DG-Schlafzimmer Fernseher' has an invalid 'Name' characteristic ('DG-Schlafzimmer Fernseher'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.878 - error: host.buanet-iobroker1 Caught by controller[5]: HAP-NodeJS WARNING: The accessory 'DG-Schlafzimmer Fernseher' has an invalid 'Name' characteristic ('DG-Schlafzimmer Fernseher'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.878 - error: host.buanet-iobroker1 Caught by controller[6]: HAP-NodeJS WARNING: The accessory 'OG-Wohnzimmer Fernseher' has an invalid 'Name' characteristic ('OG-Wohnzimmer Fernseher'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.879 - error: host.buanet-iobroker1 Caught by controller[7]: HAP-NodeJS WARNING: The accessory 'OG-Wohnzimmer Fernseher' has an invalid 'Name' characteristic ('OG-Wohnzimmer Fernseher'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.879 - error: host.buanet-iobroker1 Caught by controller[8]: HAP-NodeJS WARNING: The accessory '' has an invalid 'Name' characteristic (''). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.880 - error: host.buanet-iobroker1 Caught by controller[9]: HAP-NodeJS WARNING: The accessory 'DG-Schlafzimmer Fernseher 47C3' has an invalid 'Name' characteristic ('DG-Schlafzimmer Fernseher 47C3'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.880 - error: host.buanet-iobroker1 Caught by controller[10]: HAP-NodeJS WARNING: The accessory 'OG-Wohnzimmer Fernseher 2564' has an invalid 'Name' characteristic ('OG-Wohnzimmer Fernseher 2564'). Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis. This may prevent the accessory from being added in the Home App or cause unresponsiveness.
2025-05-06 12:52:24.881 - error: host.buanet-iobroker1 Caught by controller[11]: [DG-Schlafzimmer Fernseher 47C3] The selected advertiser, "avahi", isn't available on this platform. Reverting to "ciao"
2025-05-06 12:52:24.881 - error: host.buanet-iobroker1 Caught by controller[12]: [OG-Wohnzimmer Fernseher 2564] The selected advertiser, "avahi", isn't available on this platform. Reverting to "ciao"
2025-05-06 12:52:24.882 - error: host.buanet-iobroker1 Caught by controller[13]: [yahka 818C@DG-Schlafzimmer Ventilator@DG-Schlafzimmer Ventilator@Lock Physical Controls] characteristic value expected valid finite number and received "undefined" (undefined)
2025-05-06 12:52:24.882 - error: host.buanet-iobroker1 Caught by controller[14]: [yahka 818C@DG-Schlafzimmer Ventilator@DG-Schlafzimmer Ventilator@Swing Mode] characteristic value expected valid finite number and received "undefined" (undefined)
2025-05-06 12:52:24.882 - error: host.buanet-iobroker1 Caught by controller[15]: [yahka 818C@DG-Schlafzimmer Ventilator@DG-Schlafzimmer Ventilator@Active] characteristic value expected valid finite number and received "undefined" (undefined)
2025-05-06 12:52:24.883 - error: host.buanet-iobroker1 Caught by controller[16]: [yahka 818C@Schlafzimmer Rack@Schlafzimmer Rack@Name] characteristic was supplied illegal value: number instead of string, supplying illegal values will throw errors in the future
2025-05-06 12:52:24.883 - error: host.buanet-iobroker1 Caught by controller[17]: [yahka 818C@Schlafzimmer Rack 2@Schlafzimmer Rack 2@Name] characteristic was supplied illegal value: number instead of string, supplying illegal values will throw errors in the future
2025-05-06 12:52:24.884 - error: host.buanet-iobroker1 instance system.adapter.yahka.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-05-06 12:52:24.885 - info: host.buanet-iobroker1 Restart adapter system.adapter.yahka.0 because enabled
2025-05-06 12:52:24.885 - warn: host.buanet-iobroker1 Do not restart adapter system.adapter.yahka.0 because restart loop detected
also konnte das neue image installieren, meine Daten wieder einfügen und komme auch wieder auf die admin Oberfläche.
der parser Adapter lässt sich jetzt einwandfrei installieren (den Adapter selbst schaue ich mir dann an)
leider macht aber jetzt der yahka Adapter Probleme und startet nicht mehr
im log werden jetzt unzählige Fehler geworfen
@codierknecht hab das bild / url wieder entfernt
hab jetzt latest v-10 gezogen, die Beschreibung bleibt gleich
@jan1 ich kann nur in dem Docker Container auf der Synology hier das image laden und dann sieht das so aus
-entfernt-
außer ich gebe eine repository url ein, aber wie lautet die?
@samson71 na ja ich zieh mir ein neues buanet-iobroker latest image
wie gesagt steht direkt dabei das bullseye als Debian verwendet wird
buanet-iobroker image scheint nur mit Debian-bullseye statt bookworm zur verfügung zu stehen?
@toralt einfach? hab ich noch nie gemacht muss ich mir erstmal anschauen was da zu sichern, im einzelnen zu tun ist
anbei noch der diagnose Auszug
v.2025-02-23
/home/iobroker/.diag.sh: line 979: hostnamectl: command not found
Installation:
Kernel: x86_64
Userland: 64 bit
/home/iobroker/.diag.sh: line 988: timedatectl: command not found
Timezone:
User-ID: 0
Display-Server: false
/home/iobroker/.diag.sh: line 995: systemctl: command not found
Boot Target:
Pending OS-Updates: 0
Pending iob updates: 0
Nodejs-Installation:
/usr/bin/nodejs v22.15.0
/usr/bin/node v22.15.0
/usr/bin/npm 10.9.2
/usr/bin/npx 10.9.2
/usr/bin/corepack 0.32.0
Recommended versions are nodejs 20.19.1 and npm 10.8.2
nodeJS installation is correct
MEMORY:
total used free shared buff/cache available
Mem: 3.9G 2.6G 623M 30M 715M 1.1G
Swap: 4.4G 726M 3.7G
Total: 8.4G 3.3G 4.3G
Active iob-Instances: 18
Upgrade policy: none
ioBroker Core: js-controller 7.0.7
admin 7.6.14
ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: jsonl
Status admin and web instance:
+ system.adapter.admin.0 : admin : buanet-iobroker1 - enabled, port: 8081,
bind: 0.0.0.0, run as: admin
+ system.adapter.web.0 : web : buanet-iobroker1 - enabled, port: 8082,
bind: 0.0.0.0, run as: admin
Objects: 4455
States: 3890
Size of iob-Database:
35M /opt/iobroker/iobroker-data/objects.jsonl
8.8M /opt/iobroker/iobroker-data/objects.json.migrated8.8M /opt/iobroker/iobroker-data/objects.json.bak.migrated
7.0M /opt/iobroker/iobroker-data/states.jsonl
1.2M /opt/iobroker/iobroker-data/states.json.migrated
1.2M /opt/iobroker/iobroker-data/states.json.bak.migrated
0 /opt/iobroker/iobroker-data/states.json.broken
Debian Release codenamed 'buster' reached its END OF LIFE and needs to be updated to the latest stable release 'bookworm' NOW!
=================== END OF SUMMARY ====================
sowohl die Installation von v 2.3.1 oder auch die latest (stable) des Adapters parser (ist nur beispielhaft andere Adapter laufen auch auf Fehler 25) schlägt fehlt
$ iobroker add parser auto --host buanet-iobroker1 --debug
NPM version: 10.9.2
Installing iobroker.parser@2.2.4... (System call)
npm error code EBADENGINE
npm error engine Unsupported enginenpm error engine Not compatible with your version of node/npm: hap-nodejs@1.1.0npm error notsup Not compatible with your version of node/npm: hap-nodejs@1.1.0npm error notsup Required: {"node":"^18 || ^20"}npm error notsup Actual: {"npm":"10.9.2","node":"v22.15.0"}
npm error A complete log of this run can be found in: /opt/iobroker/.npm/_logs/2025-05-06T05_14_53_545Z-debug-0.log
host.buanet-iobroker1 Cannot install iobroker.parser@2.2.4: 1
ERROR: Process exited with code 25
na ja bin bei version 22.x gelandet also etwas übers sie hinaus.
z.b. bei Installation des Adapters Perser erhalte ich folgende Fehlermeldung
iobroker npm error code EBADENGINEnpm error engine Unsupported enginenpm error engine Not compatible with your version of node/npm: hap-nodejs@1.1.0npm error notsup Not compatible with your version of node/npm: hap-nodejs@1.1.0npm error notsup Required: {"node":"^18 || ^20"}npm error notsup Actual: {"npm":"10.9.2","node":"v22.15.0"}