NEWS
[gelöst] Cloudinstanz läuft nicht
-
Hallo zusammen,
habe mich auch gewundert warum ich mittels Alexa nichts mehr steuern konnte und deshalb nebenbei aus Verzweiflung meinen Raspi mal auf den neuesten Stand gebracht :lol:
Ich bin jetzt mit der Cloud 2.4.6 und Admin Version 2.0.9 unterwegs.
Meine CLoudinstanz bleibt grau (also weder grün, rot oder gelb). Ich benutze die freie Variante auf iobroker.net.
Hier ein Log-Auszug, wobei ich einige Sachen ge-x-t habe:
! ````
cloud.0 2018-03-04 15:09:31.707 info User accessed from cloud
cloud.0 2018-03-04 15:09:10.129 info User disconnected from cloud
cloud.0 2018-03-04 15:07:38.431 info Request enums
cloud.0 2018-03-04 15:07:38.422 info Request enums
cloud.0 2018-03-04 15:06:53.449 info Connection changed: connect
cloud.0 2018-03-04 15:06:53.262 info Trying to connect as system.user.admin
fritzdect.0 2018-03-04 15:06:34.082 info no thermostats found
fritzdect.0 2018-03-04 15:06:33.793 info setting up switch object XXXXXXXXXX
fritzdect.0 2018-03-04 15:06:33.743 info setting up switch object XXXXXX
fritzdect.0 2018-03-04 15:06:33.738 info Switches AINs: XXXXXXXX
fritzdect.0 2018-03-04 15:06:33.428 info Talking to FritzBox with firmware: 06.93
fritzdect.0 2018-03-04 15:06:26.749 info entered ready
fritzdect.0 2018-03-04 15:06:26.729 info starting. Version 0.0.10 in /opt/iobroker/node_modules/iobroker.fritzdect, node: v6.13.0
fritzdect.0 2018-03-04 15:06:26.574 info States connected to redis: 127.0.0.1:XXXX
cloud.0 2018-03-04 15:06:23.974 info Trying to connect as system.user.admin
cloud.0 2018-03-04 15:06:23.142 info Connecting with https://iobroker.net:10555 with "ENTFERNT_XXXXXXXXXXXXXcccd"
cloud.0 2018-03-04 15:06:22.815 info starting. Version 2.4.6 in /opt/iobroker/node_modules/iobroker.cloud, node: v6.13.0
cloud.0 2018-03-04 15:06:22.654 info States connected to redis: 127.0.0.1:XXXX
javascript.0 2018-03-04 15:06:20.559 info received all objects
javascript.0 2018-03-04 15:06:19.072 info received all states
host.ioBroker-RasPi 2018-03-04 15:06:17.828 info instance system.adapter.fritzdect.0 started with pid 1145
javascript.0 2018-03-04 15:06:17.719 info requesting all objects
javascript.0 2018-03-04 15:06:17.709 info requesting all states
javascript.0 2018-03-04 15:06:17.675 info starting. Version 3.2.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.13.0
javascript.0 2018-03-04 15:06:17.513 info States connected to redis: 127.0.0.1:XXXX
rpi2.0 2018-03-04 15:06:17.063 info GPIO ports are not configured
host.ioBroker-RasPi 2018-03-04 15:06:14.331 info instance system.adapter.cloud.0 started with pid 1099
rpi2.0 2018-03-04 15:06:13.293 info starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.rpi2, node: v6.13.0
rpi2.0 2018-03-04 15:06:13.113 info States connected to redis: 127.0.0.1:XXXX
host.ioBroker-RasPi 2018-03-04 15:06:10.501 info instance system.adapter.vis.0 terminated while should be started once
host.ioBroker-RasPi 2018-03-04 15:06:09.782 info instance system.adapter.rpi2.0 started with pid 1089
history.0 2018-03-04 15:06:09.359 info starting. Version 1.6.0 in /opt/iobroker/node_modules/iobroker.history, node: v6.13.0
history.0 2018-03-04 15:06:08.976 info States connected to redis: 127.0.0.1:XXXX
vis.0 2018-03-04 15:06:08.916 info vis license is OK.
vis.0 2018-03-04 15:06:08.443 info starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.vis, node: v6.13.0
host.ioBroker-RasPi 2018-03-04 15:06:08.350 info instance system.adapter.javascript.0 started with pid 1075
vis.0 2018-03-04 15:06:05.161 info States connected to redis: 127.0.0.1:XXXX
web.0 2018-03-04 15:06:05.225 info http server listening on port XXXX
web.0 2018-03-04 15:06:05.181 info socket.io server listening on port XXXX
hm-rega.0 2018-03-04 15:06:03.171 info got state values
hm-rega.0 2018-03-04 15:06:02.515 info request state values
hm-rega.0 2018-03-04 15:06:02.510 info deleted 0 variables
hm-rega.0 2018-03-04 15:06:02.508 info added/updated 5 variables
hm-rega.0 2018-03-04 15:06:02.397 info got 5 variables
hm-rega.0 2018-03-04 15:06:02.156 info deleted 0 programs
hm-rega.0 2018-03-04 15:06:02.154 info added/updated 5 programs
hm-rega.0 2018-03-04 15:06:00.473 info got 5 programs
host.ioBroker-RasPi 2018-03-04 15:06:01.827 info instance system.adapter.history.0 started with pid 1065Mir ist momentan nicht klar was hier nicht funktioniert :cry: MOD-Edit by eric2905; Log-Auszüge immer in Code- und ggf. Spoiler-Tags setzen -
sobald ich gegoogelt habe wie das geht, mache ich das :oops:
Mache ich das mit Webstorm wie hier beschrieben?
https://github.com/ioBroker/ioBroker/wi … nvironment
Ansonsten würde ich mich freuen wenn du mir mitteilst wie ich hier auf dem raspi vorgehen muss
-
-
Der Cloudadapter ist jetzt grün (warum auch immer). Sprachsteuerung funktioniert aber trotzdem nicht. Hier ein Debug-Auszug, da ich nicht weiß welche Infos man besser für sich behält, leicht ge-x-t:
! ````
cloud.0 2018-03-04 15:46:59.875 warn Unknown applianceId: fritzdect_0_DECT200_XXXXXXXXX_state
cloud.0 2018-03-04 15:46:59.874 debug ALEXA ON: fritzdect_0_DECT200_XXXXXXXX_state
cloud.0 2018-03-04 15:46:59.873 debug New Request: TurnOnRequest
cloud.0 2018-03-04 15:46:59.872 debug null
cloud.0 2018-03-04 15:46:59.870 debug XXXXXXXXXX ALEXA: {"header":{"namespace":"Alexa.ConnectedHome.Control","name":"TurnOnRequest","payloadVersion":"2","messageId":"XXXXXXXXXXXXXX"},"payload":{"accessToken":"3bde
cloud.0 2018-03-04 15:46:41.031 warn Unknown applianceId: hm-rpc_0_MEQ1428758_1_LEVEL
cloud.0 2018-03-04 15:46:41.031 debug ALEXA Percent: hm-rpc_0_MEQ1428758_1_LEVEL 0%
cloud.0 2018-03-04 15:46:41.030 debug New Request: SetPercentageRequest
cloud.0 2018-03-04 15:46:41.011 debug null
cloud.0 2018-03-04 15:46:41.008 debug XXXXXXXXXX ALEXA: {"header":{"namespace":"Alexa.ConnectedHome.Control","name":"SetPercentageRequest","payloadVersion":"2","messageId":"GELÖSCHT"},"payload":{"accessToken
cloud.0 2018-03-04 15:45:45.571 debug Invalid state "rpi2.0.wlan.wifi_send". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.570 debug Invalid state "rpi2.0.wlan.wifi_received". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.551 debug Invalid state "rpi2.0.uptime.uptime". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.550 debug Invalid state "rpi2.0.temperature.soc_temp". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.550 debug Invalid state "rpi2.0.swap.swap_used". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.549 debug Invalid state "rpi2.0.swap.swap_total". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.548 debug Invalid state "rpi2.0.sdcard.sdcard_boot_used". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.547 debug Invalid state "rpi2.0.sdcard.sdcard_root_used". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.547 debug Invalid state "rpi2.0.sdcard.sdcard_boot_total". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.546 debug Invalid state "rpi2.0.sdcard.sdcard_root_total". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.545 debug Invalid state "rpi2.0.network.net_send". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.544 debug Invalid state "rpi2.0.network.net_received". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.543 debug Invalid state "rpi2.0.memory.memory_available". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.538 debug Invalid state "rpi2.0.memory.memory_free". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.537 debug Invalid state "rpi2.0.memory.memory_total". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.535 debug Invalid state "rpi2.0.cpu.scaling_governor". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.530 debug Invalid state "rpi2.0.cpu.load15". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.530 debug Invalid state "rpi2.0.cpu.load5". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.529 debug Invalid state "rpi2.0.cpu.load1". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.528 debug Invalid state "rpi2.0.cpu.cpu_frequency". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.527 debug Invalid state "hm-rpc.0.updated". Not exist or no native part.
cloud.0 2018-03-04 15:45:45.445 info Connection changed: connect
cloud.0 2018-03-04 15:45:45.444 debug API KEY OK
cloud.0 2018-03-04 15:45:45.418 debug Connected. Check api key...
cloud.0 2018-03-04 15:45:45.417 debug Created ALEXA device: Grüne Lampe ["turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.415 debug Created ALEXA device: Jalousie Bad EG ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.415 debug Created ALEXA device: Jalousie Franka ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.414 debug Created ALEXA device: Jalousie Küche ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.413 debug Created ALEXA device: Jalousie Schlafzimmer ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.412 debug Created ALEXA device: Jalousie Wohnzimmerfenster ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.411 debug Created ALEXA device: Jalousie Wohnzimmertür 1 LEVEL ["setPercentage","incrementPercentage","decrementPercentage","turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.402 debug Created ALEXA device: Licht Gästezimmer ["turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.402 debug Created ALEXA device: Steckdose Kino ["turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.401 debug Created ALEXA device: Warmes Wasser ["turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.400 debug Created ALEXA device: Wasser ["turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.399 debug Created ALEXA device: Yamaha ["turnOn","turnOff"]
cloud.0 2018-03-04 15:45:45.398 debug Name "Switch total energy" cannot be written and will be ignored
cloud.0 2018-03-04 15:45:45.398 debug Name "Switch act power" cannot be written and will be ignored
cloud.0 2018-03-04 15:45:45.397 debug Name "Switch present" cannot be written and will be ignoredMOD-Edit by eric2905; Tags benutzen -
Hi,
vorab: Bitte Logs & Co. immer in Code- und ggf. Spoiler-Tags setzen. Ich habe das jetzt 2 x für Dich gemacht und jeweils in rot den Hinweis gegeben.
Zum Thema:
Hast Du die Geräte bei Alexa mal gelöscht und neu angelegt (taucht schon einige Male im Forum auf)?
Bitte beachten : Dabei gehen auch die dort angelegten Gruppen, usw. verloren.
Gruß,
Eric
808
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge