Monatsrückblick Januar/Februar 2026 ist online!

[klausM]

Hallo,

leider bekomme ich das Problem alleine nicht gelöst. Bis vor kurzen konnte ich mit über Alexa Speak noch Texte ausgeben. Gestern Abend viel mir auf, das dies nicht mehr funktioniert.
Ob es mit dem Umzug auf die ioT Cloud zusammenhängt, kann ich nicht beurteilen. Geräte werden auf Amazon erkannt, Kommandos werden ausgeführt.

Im Log erscheint dieses:

2019-12-16 09:00:00.096 - info: pushover.0 (29716) Send pushover notification: {"message":"Ausfall Gefrierschrank","title":"ioBroker","priority":"0"}
2019-12-16 09:00:00.101 - warn: alexa2.0 (14195) Exception: TypeError: callback is not a function
2019-12-16 09:00:00.110 - error: alexa2.0 (14195) uncaught exception: callback is not a function
2019-12-16 09:00:00.110 - error: alexa2.0 (14195) TypeError: callback is not a function
at AlexaRemote.createSequenceNode (/media/HDSamsung1/iobroker/node_modules/alexa-remote2/alexa-remote.js:1398:28)
at AlexaRemote.sendMultiSequenceCommand (/media/HDSamsung1/iobroker/node_modules/alexa-remote2/alexa-remote.js:1542:38)
at adapter.getState (/media/HDSamsung1/iobroker/node_modules/iobroker.alexa2/main.js:1519:31)
at client.get (/media/HDSamsung1/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:491:17)
at tryCatcher (/media/HDSamsung1/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
at promise.then (/media/HDSamsung1/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-12-16 09:00:00.116 - info: alexa2.0 (14195) terminating
2019-12-16 09:00:00.118 - info: alexa2.0 (14195) Terminated (NO_ERROR): Without reason
2019-12-16 09:00:00.666 - error: host.raspberrypi Caught by controller[0]: TypeError: callback is not a function
2019-12-16 09:00:00.666 - error: host.raspberrypi Caught by controller[0]: at AlexaRemote.createSequenceNode (/media/HDSamsung1/iobroker/node_modules/alexa-remote2/alexa-remote.js:1398:28)
2019-12-16 09:00:00.666 - error: host.raspberrypi Caught by controller[0]: at AlexaRemote.sendMultiSequenceCommand (/media/HDSamsung1/iobroker/node_modules/alexa-remote2/alexa-remote.js:1542:38)
2019-12-16 09:00:00.667 - error: host.raspberrypi Caught by controller[0]: at adapter.getState (/media/HDSamsung1/iobroker/node_modules/iobroker.alexa2/main.js:1519:31)
2019-12-16 09:00:00.667 - error: host.raspberrypi Caught by controller[0]: at client.get (/media/HDSamsung1/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:491:17)
2019-12-16 09:00:00.667 - error: host.raspberrypi Caught by controller[0]: at tryCatcher (/media/HDSamsung1/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
2019-12-16 09:00:00.667 - error: host.raspberrypi Caught by controller[0]: at promise.then (/media/HDSamsung1/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
2019-12-16 09:00:00.668 - error: host.raspberrypi Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:68:7)

LG Klaus

[klausM]

Hallo,

vermutlich habe ich mit meinem Problem die falsche Gruppe gewählt. Ich bin allerdings noch zu unsicher im Umgang mit Forum. Vielleicht wäre das besser unter "Error/Bug" aufgehoben.

Mittlerweile habe einige male die ioT Instanz und Alexa2.0 neu gestartet. Geräte auf Alexa neu eingelesen. Geräte-Gruppen gelöscht und neu erzeugt.
Log bei Restart Alexa2.0:

2019-12-16 17:03:32.663 - info: alexa2.0 (11595) starting. Version 2.6.4 in /media/HDSamsung1/iobroker/node_modules/iobroker.alexa2, node: v10.17.0
2019-12-16 17:03:32.778 - info: alexa2.0 (11595) Proxy IP not set, use first network interface (192.168.0.10) instead
2019-12-16 17:03:39.145 - info: alexa2.0 (11595) Unknown Device, but enabling commands, Try it and report back if commands work.
2019-12-16 17:03:39.146 - info: alexa2.0 (11595) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
2019-12-16 17:03:39.146 - info: alexa2.0 (11595) Device-type:A1RABVCI4QCIKC (GOLDFISH,SLEEP,REMINDERS,AUDIBLE,TUPLE,AUDIO_PLAYER,ALLOW_LOG_UPLOAD,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,GUARD_EARCON,TIMERS_ALARMS_NOTIFICATIONS_VOLUME,DIALOG_INTERFACE_VERSION,TAHOE_BYOD,MICROPHONE,DREAM_TRAINING,TUNE_IN,PAIR_REMOTE,FLASH_BRIEFING,PAIR_BT_SOURCE,SOUND_SETTINGS,VOLUME_SETTING,ALEXA_PRESENCE,GADGETS,LEMUR_ALPHA,TUPLE_CATEGORY_A,PERSISTENT_CONNECTION,SUPPORTS_SOFTWARE_VERSION,BT_PAIRING_FLOW_V2,SET_LOCALE,PAIR_BT_SINK,PANDORA,DEREGISTER_DEVICE,VOICE_TRAINING,ASCENDING_ALARM_VOLUME,POPTART,UPDATE_WIFI,AMAZON_MUSIC,MUSIC_SKILL,KINDLE_BOOKS,FAR_FIELD_WAKE_WORD,SUPPORT_CALENDAR_ALERT,TIMERS_AND_ALARMS,SALMON,I_HEART_RADIO,CHANGE_NAME,EARCONS,DS_VOLUME_SETTING,REQUIRES_OOBE_FOR_SETUP,ACTIVE_AFTER_FRO,CUSTOM_ALARM_TONE)
2019-12-16 17:03:39.500 - info: alexa2.0 (11595) Alexa-Push-Connection established. Disable Polling
2019-12-16 17:03:52.759 - info: alexa2.0 (11595) Deleting the following states: ["... einige States ...."]

Nach den vielen trial and error Aktionen funktioniert Alexa - Speak wieder. Darüber bin ich froh aber wohler wäre mir, wenn ich die Ursache kennen würde.

LG Klaus