@walter-white im iot adapter unter Service kannst du ein Dienst hinzufügen/erstellen, den man über eine URL verändern kann. Die URL kannst du in der fritzbox und fritz app bei geo abrufen lassen beim verlassen oder betreten.
Funktioniert tadellos und super schnell. Bis jetzt das einfachste und beste was ich für mein Android Handy nutzen kann.
NEWS
Best posts made by denjo
-
RE: FritzBox SmartHome app Beta
-
RE: Ring Doorbell Bild versenden
So also, ist klar das ihr Telegram einrichten müsst und den Rest seht ihr an den Bildern hoffe ich, falls fragen sind einfach fragen.
-
RE: Adapter für Navimow Rasenmähroboter?
@surfer09 Hallo, also ich habe meine i105 jetzt in iobroker drin. Kann ihn über iobroker und alexa steuern und kann sehen was er gerade macht. Ich habe es mit der google integration gelöst. dort ist der Robbi ein gerät bedeutet man kann damit in google home routinen erstellen. also erstellt man mehrere objekte in iobroker für alle zustände die der Robbi in google liefert und bringt diese mit den IOT Adapter in google home rein. Dann erstellt man mehrere Routinen in Google zb wenn er startet soll er das Objekt von iOBroker "Start Stop Status" zb auf an schalten. Das macht man mit allen wie gesagt. Dann muss man natürlich Blocklys erstellen wenn was passiert usw. Und dann kann man den Robbi auch in Alexa zuverlässig bringen.
Hoffe man versteht mich.
Jetzt will ich nur noch eine liste erstellen wann er die letzten male wie lange gemäht hat.Und ja man kann nicht alles auslesen wie zb Wlan Akku usw aber wie gesagt man kann ihn steuern. Erstmal reicht das bis eine API hoffentlich kommt.
-
RE: intel nuc wlan vebindung?
@amg_666 wie gesagt bei der einrichtung hatte ich lan dran, deswegen wurde ich nicht gefragt. aber dann werde ich keine wlan vebindung einrichten.
-
spotify vis??
hallo, ich habe den Spotify adapter eingerichtet und er läuft auch, aber leider habe ich keine button im vis.editor zum einfügen. ich habe auch den browser cache geleert und verschiedene browser ausprobiert. oder wo bekomme ich die her?
-
RE: Neue Installationsroutine (für Linux)
ja cool, so hat geklappt.
für alle die so blöd sind wie ich hier:cd /opt/iobroker sudo systemctl stop iobroker curl -sL https://iobroker.net/fix.sh | bash - start iobroker cd /opt/iobroker iobroker stop iobroker update iobroker upgrade self iobroker start
-
RE: Suche anwesensheits skript
@Albert-K hab mir jetzt eine neue fritz bestellt
-
Neuer Tado Adapter und VIS
Hallo, ich habe den neuen Tado Adapter installiert und alles läuft nun wollte ich ein widget konfigurieren wie im Bild zu sehen. Aber es fehlen alle Ordner wenn ich das Widget konfigurieren möchte außer der Alexa2, wie im Bild zu sehen.
Hatte jemand schon mal das selbe problem? -
RE: Alexa2 3.4.0 - KILLER FEATURE textCommand :-)
@apollon77 sagte in Alexa2 3.4.0 - KILLER FEATURE textCommand
:
@Dr-Bakterius Theoretisch kann der Custom SKill mit bissl JS Skript ds "warten auf antwort" ... jetzt könnte man da vllt echt was basteln
ich würde gerne wissen ob wenn zb ein objekt sich ändert das alexa mir eine frage stellt und ich mit ja oder nein antworten muss???
Latest posts made by denjo
-
RE: Test Adapter Linux Control v1.x.x
ich habe auch probleme mit dem Adapter
über Putty kann ich ohne probleme zugreifen
Mein IObroker ist bei allem auf aktuellen stand
Node.js: v20.19.4
JS Controller 7.0.6
Adapter. 1.1.5host.iOBroker 2025-08-13 20:44:20.577 info "system.adapter.linux-control.0" disabled linux-control.0 2025-08-13 20:44:06.264 error Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string" host.iOBroker 2025-08-13 20:44:05.094 info instance system.adapter.linux-control.0 in version "1.1.5" started with pid 3987 host.iOBroker 2025-08-13 20:43:34.740 info Restart adapter system.adapter.linux-control.0 because enabled host.iOBroker 2025-08-13 20:43:34.740 error instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[14]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[14]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[14]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[14]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[13]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[13]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[13]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[13]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[13]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[12]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[12]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[12]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[12]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[11]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[11]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[11]: ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[11]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[10]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[10]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[10]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[10]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[9]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[9]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[9]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[9]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[8]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[8]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[8]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[8]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[7]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[7]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[7]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[6]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.740 error Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[5]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[5]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[5]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[5]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[4]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[4]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[4]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[4]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[3]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[3]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[3]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[3]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[2]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[2]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[2]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[2]: 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(). The promise rejected with the reason: host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[1]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[1]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[1]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern host.iOBroker 2025-08-13 20:43:34.739 error Caught by controller[0]: 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(). The promise rejected with the reason: linux-control.0 2025-08-13 20:43:34.634 error [needrestart] hyperion (192.168.178.67:22): error: Cannot find view "system", stack: Error: Cannot find view "system" at ObjectsInRedisClient._getObjectView (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4272:19) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4346:33) linux-control.0 2025-08-13 20:43:34.595 error Cannot find view "system" for search "state" : Connection is closed. linux-control.0 2025-08-13 20:43:34.593 error [servicesInfo] hyperion (192.168.178.67:22): error: DB closed, stack: Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:639:26) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:343:12) linux-control.0 2025-08-13 20:43:34.554 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.554 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.554 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.553 error 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(). linux-control.0 2025-08-13 20:43:34.515 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.515 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.515 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.514 error 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(). linux-control.0 2025-08-13 20:43:34.480 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.480 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.479 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.479 error 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(). linux-control.0 2025-08-13 20:43:34.464 error Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.463 error ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) linux-control.0 2025-08-13 20:43:34.463 error unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.463 error 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(). host.iOBroker-Server 2025-08-13 20:43:34.462 warn States 127.0.0.1:45704 Error from InMemDB: Error: The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:242:14) at RedisHandler.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:380:26) at RedisHandler.emit (node:events:524:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:483:21) linux-control.0 2025-08-13 20:43:34.436 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.436 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.435 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.435 error 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(). linux-control.0 2025-08-13 20:43:34.366 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.366 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.365 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.365 error 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(). linux-control.0 2025-08-13 20:43:34.351 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.351 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.351 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.350 error 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(). linux-control.0 2025-08-13 20:43:34.288 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.288 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.287 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.287 error 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(). linux-control.0 2025-08-13 20:43:34.256 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.256 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.255 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.255 error 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(). linux-control.0 2025-08-13 20:43:34.215 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.215 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.215 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.215 error 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(). linux-control.0 2025-08-13 20:43:34.194 error The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.194 error Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) linux-control.0 2025-08-13 20:43:34.145 error unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.145 error 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(). linux-control.0 2025-08-13 20:43:34.138 error ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) linux-control.0 2025-08-13 20:43:34.138 error unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.138 error Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern linux-control.0 2025-08-13 20:43:34.137 error 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().
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico weiß ich ausn kopf nicht, ausprobieren am besten. Ist mit sicherheit ein nicht schreib geschütztes Objekt, da gibt es nicht als so viele.
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico du solltest dir mal ein paar Videos zu iobroker bei Youtube rein ziehen, bissl grund wissen kann nicht schaden.
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico das ist ja auch die voraussetzen die app zu haben und den tv dort rein zu machen.
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico achja stimmt da hat sich was geändert, da bin ich erstmal raus. Da ich jetzt auch schlafen gehe nach meiner nachtschicht
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico steht aber bestimmt in der Beschreibung
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico ich hab den vor jahren eingerichtet, man muss doch mit einem normalen Browser sich in den samsung konto anmelden und einen Token erstellen.
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico auf die drei Punkte und installieren
-
RE: Samsung TV mittels Samsung Titzen Instanz nutzen
@mico über die Katze installieren