Bei mir verbindet sich der iot-Adapter nicht (gelb).

Cannot fetch keys: "Internal server error"

error{}

Ich habe den Adapter neu gestartet, unter "Einstellungen" "erhalten Sie neue Verbindungszertifikate" angeklickt, …

Was kann ich noch machen?

Ich nutze die pro-Version.

Gibt es tatsächlich keinen Hinweis, was ich falsch mache oder anders machn kann?

Oder bin ich in der falschen Rubrik?

Andi

Ich habe Homematic mit und ohne IP, Alexa, Synology, buanet-image in Docker

Fast zwei Jahre lief mein System (ich konnte Homematic-Geräte per Alexa steuern). Vor ca. 3 Wochen ging die Steuerung nicht mehr, Updates funktionierten nicht mehr. Ich habe einen neuen Container mit dem neuen buanet-image installiert.

alexa 2.0 - grün
iot.0 - grün
hm-rega.0 - grün - Homematic-Programme und Variablen vorhanden
hm-rpc.0 - grün - Homematic-Geräte vorhanden
hm-rpc.1 - grün - Homematic-IP-Geräte vorhanden

In iot wurden automatisch aufgelistet:
Rasenmäher, gesteuert durch robonect
Außenthermometer
Sonst keine weiteren Geräte. Bei der letzten Installation vor Monaten wurden alle Geräte automatisch gefunden.

Wenn ich über "+" Geräte hinzufügen möchte, sehe ich die Punkte "hm-rega" mit Programmen und Variblen, und 1 x "hm-rpc" mit den Geräten. Füge ich davon eins in iot dazu, kommt ein Fehlerhinweis.

Ich habe auch keinen Punkt unter hm-rpc.0 oder .1 gefunden, wo ich über den rpc-Adapter ein Gerät direkt einschalten kann.

Ich habe nichts gefunden, was mir weitergeholfen hat. Was mache ich falsch?

Andi

Vermutlich blöde Frage, aber wie setze ich den Beitrag auf gelöst? Einen Button sehe ich nicht. "gelöst" in der Überschrift ergänzen?

Das hat funktioniert. Vielen Dank!!

Über die Synology konnte ich jedoch keine Terminaleingaben machen. Über portainer ging es.

Meinst du diese Angabe: /volume1/docker/iobroker_data

Ich habe iobroker auf der Synology mit docker neu installiert. Der Zugriff über die Webseite funktionierte. Dann habe ich einen Fehler gemacht und die Voreinstellung "hört auf alle IP" (so ähnlich ) auf eine falsche IP geändert. Jetzt habe ich über IP:8081 keinen Zugriff mehr.

Ich habe den Container gelöscht und wieder neu installiert, das Problem hat sich nicht gelöst.

Muss ich im Verzeichnis /docker/iobroker_data eine Datei mit den alten Einstellungen löschen? Wenn ja, welche ist das?

Grüße

Andi

Danke.

Habe ich eine Chance, das Gerät mehr einzugrenzen? Kommt das aus Homematic oder IOBroker?

Ich habe im Stundenrhythmus einen Warnhinweis zu Alexa. Bin ich der Einzige mit diesem Problem, oder ist das normal?

Grüße
Ulf

alexa2.0 2019-05-25 22:40:39.519 warn Device-type:ATH4K2BAIXVHQ (MICROPHONE,PEONY,VOLUME_SETTING)
alexa2.0 2019-05-25 22:40:39.518 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 21:40:35.215 warn Device-type:ATH4K2BAIXVHQ (PEONY,VOLUME_SETTING,MICROPHONE)
alexa2.0 2019-05-25 21:40:35.214 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 20:40:30.748 warn Device-type:ATH4K2BAIXVHQ (MICROPHONE,PEONY,VOLUME_SETTING)
alexa2.0 2019-05-25 20:40:30.748 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 19:40:26.786 warn Device-type:ATH4K2BAIXVHQ (VOLUME_SETTING,MICROPHONE,PEONY)
alexa2.0 2019-05-25 19:40:26.786 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 18:40:22.716 warn Device-type:ATH4K2BAIXVHQ (VOLUME_SETTING,PEONY,MICROPHONE)
alexa2.0 2019-05-25 18:40:22.715 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 17:40:18.494 warn Device-type:ATH4K2BAIXVHQ (VOLUME_SETTING,PEONY,MICROPHONE)
alexa2.0 2019-05-25 17:40:18.494 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 16:40:14.510 warn Device-type:ATH4K2BAIXVHQ (MICROPHONE,PEONY,VOLUME_SETTING)
alexa2.0 2019-05-25 16:40:14.510 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 15:40:10.569 warn Device-type:ATH4K2BAIXVHQ (VOLUME_SETTING,MICROPHONE,PEONY)
alexa2.0 2019-05-25 15:40:10.569 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2019-05-25 14:40:06.624 warn Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
alexa2.0 2019-05-25 14:40:06.624 warn Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please

Ich habe das Problem, dass Sprachbefehle an Alexa vereinzelt nicht umgesetzt, von Alexa aber als ausgeführt bestätigt werden.

Ich habe dann im log den Hinweis auf duty circle gefunden, nachts, wenn eigentlich nichts geschaltet wird. Dabei sind mir die Einträge im log-file zu Alexa aufgefallen. Ist das normal? Die Warnungen tauchen zu nachtschlafender Zeit auf, wenn niemand etwas mit Alexa macht.

2019-04-29 00:56:15.311 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 00:56:15.311 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
2019-04-29 01:56:18.915 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 01:56:18.915 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (PEONY,VOLUME_SETTING,MICROPHONE)
2019-04-29 02:04:44.171 - info: host.buanet-iobroker1 Delete log file iobroker.2019-04-22.log
2019-04-29 02:56:22.502 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 02:56:22.502 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,PEONY,VOLUME_SETTING)
2019-04-29 03:56:26.262 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 03:56:26.262 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (PEONY,VOLUME_SETTING,MICROPHONE)
2019-04-29 04:56:30.085 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 04:56:30.085 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,PEONY,VOLUME_SETTING)
2019-04-29 05:56:34.023 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 05:56:34.023 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (PEONY,MICROPHONE,VOLUME_SETTING)
2019-04-29 06:56:37.672 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 06:56:37.672 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
2019-04-29 07:05:53.564 - error: hm-rpc.0 Ping error: Error: response timeout
2019-04-29 07:05:53.564 - info: hm-rpc.0 Disconnected
2019-04-29 07:06:01.816 - info: hm-rpc.0 Connected
2019-04-29 07:34:36.832 - error: hm-rpc.0 Ping error: Error: response timeout
2019-04-29 07:34:36.832 - info: hm-rpc.0 Disconnected
2019-04-29 07:34:40.490 - info: hm-rpc.0 Connected
2019-04-29 07:56:41.582 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 07:56:41.582 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
2019-04-29 08:56:45.316 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 08:56:45.316 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (VOLUME_SETTING,MICROPHONE,PEONY)
2019-04-29 09:56:49.016 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 09:56:49.016 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (VOLUME_SETTING,PEONY,MICROPHONE)
2019-04-29 10:56:52.672 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 10:56:52.672 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (PEONY,VOLUME_SETTING,MICROPHONE)
2019-04-29 11:56:56.368 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 11:56:56.369 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
2019-04-29 12:56:59.989 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 12:56:59.989 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (VOLUME_SETTING,PEONY,MICROPHONE)
2019-04-29 13:57:03.716 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 13:57:03.743 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,PEONY,VOLUME_SETTING)
2019-04-29 14:04:46.252 - info: admin.0 Request actual repository...
2019-04-29 14:04:46.272 - info: host.buanet-iobroker1 Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2019-04-29 14:04:47.518 - info: admin.0 Repository received successfully.
2019-04-29 14:57:07.532 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 14:57:07.532 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,PEONY,VOLUME_SETTING)
2019-04-29 15:57:11.133 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 15:57:11.133 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
2019-04-29 16:57:14.253 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 16:57:14.253 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
2019-04-29 17:57:18.051 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 17:57:18.051 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (PEONY,MICROPHONE,VOLUME_SETTING)
2019-04-29 18:57:22.003 - warn: alexa2.0 Disabling some commands for device because of unknown type. Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-04-29 18:57:22.004 - warn: alexa2.0 Device-type:ATH4K2BAIXVHQ (MICROPHONE,VOLUME_SETTING,PEONY)
2019-04-29 19:40:17.122 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.188.81
2019-04-29 19:40:17.166 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.188.81
2019-04-29 19:40:17.434 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.188.81
2019-04-29 19:40:18.017 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.188.81
2019-04-29 19:41:42.579 - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.188.81 rickshaw

@apollon77
Ich habe noch einmal den Skill und den Adapter neu installiert. Jetzt geht es.

Ibrocker läuft auf meiner Synology in Docker - Buanet-iobroker1.

In der Regel ist meine installierte Version gleich oder höher (?) als die verfügbare Version. So ist mein IoT Assistants die Version 0.2.2. Kann es sein, dass bei meiner Installation Updates nicht möglich sind, sondern dass das Docker-Image neu installiert werden muss (wenn denn ein neues Image hergestellt wurde)?