[FIX available] Alexa per Alexa2 Totalausfall !?
-
Ja, Sentry hat irgendwie beim Publish von deren kram nen Fehler gemacht grmmpfff
https://github.com/getsentry/publish/issues/1513 ... die sind dran.
Geben wir inhnen ne stunden... Ich ne neue Version und Repo Update dauert genauso lang
closed publish: getsentry/sentry-javascript@7.17.0 #1513
-
kann auch nicht auf die 3.19.10 upgraden, kommt immer ein NPM@error (sentry/utils@7.17.0 ), andere Adapter (Synology, Wireshark) gingen problemlos.
Node 16.18.0 und NPM 8.19.2, debian 10, lxc.ilovegym@VMC123-iobroker /opt/iobroker $ iob upgrade --debug This upgrade of "alexa2" will introduce the following changes: ========================================================================== -> 3.19.10: Fix issue in retry handling when rate limit exceeded is returned by Amazon Do not clean up Smart Home Device objects for now - delete manually if you remove a device ========================================================================== Would you like to upgrade alexa2 from @3.19.9 to @3.19.10 now? [(y)es, (n)o]: y Update alexa2 from @3.19.9 to @3.19.10 NPM version: 8.19.2 Installing iobroker.alexa2@3.19.10... (System call) npm ERR! code ETARGET npm ERR! notarget No matching version found for @sentry/utils@7.17.0. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-10-27T13_33_07_142Z-debug-0.logdas npm debuglog:
ilovegym@VMC123-iobroker /opt/iobroker $ cat /home/iobroker/.npm/_logs/2022-10-27T13_33_07_142Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@8.19.2 2 info using node@v16.18.0 3 timing npm:load:whichnode Completed in 0ms 4 timing config:load:defaults Completed in 2ms 5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 6ms 6 timing config:load:builtin Completed in 7ms 7 timing config:load:cli Completed in 3ms 8 timing config:load:env Completed in 0ms 9 timing config:load:file:/opt/iobroker/.npmrc Completed in 3ms 10 timing config:load:project Completed in 19ms 11 timing config:load:file:/home/iobroker/.npmrc Completed in 0ms 12 timing config:load:user Completed in 0ms 13 timing config:load:file:/usr/etc/npmrc Completed in 0ms 14 timing config:load:global Completed in 1ms 15 timing config:load:validate Completed in 1ms 16 timing config:load:credentials Completed in 1ms 17 timing config:load:setEnvs Completed in 1ms 18 timing config:load Completed in 36ms 19 timing npm:load:configload Completed in 37ms 20 timing npm:load:mkdirpcache Completed in 1ms 21 timing npm:load:mkdirplogs Completed in 1ms 22 verbose title npm install iobroker.alexa2@3.19.10 23 verbose argv "install" "--save-exact" "iobroker.alexa2@3.19.10" 24 timing npm:load:setTitle Completed in 1ms 25 timing config:load:flatten Completed in 5ms 26 timing npm:load:display Completed in 7ms 27 verbose logfile logs-max:10 dir:/home/iobroker/.npm/_logs 28 verbose logfile /home/iobroker/.npm/_logs/2022-10-27T13_33_07_142Z-debug-0.log 29 timing npm:load:logFile Completed in 7ms 30 timing npm:load:timers Completed in 1ms 31 timing npm:load:configScope Completed in 0ms 32 timing npm:load Completed in 56ms 33 timing arborist:ctor Completed in 1ms 34 silly logfile start cleaning logs, removing 2 files 35 silly logfile done cleaning log files 36 timing idealTree:init Completed in 1962ms 37 timing idealTree:userRequests Completed in 54ms 38 silly idealTree buildDeps 39 silly fetch manifest iobroker.alexa2@3.19.10 40 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules/iobroker.synology 41 http fetch GET 200 https://registry.npmjs.org/iobroker.alexa2 1642ms (cache hit) 42 silly placeDep ROOT iobroker.alexa2@3.19.10 REPLACE for: iobroker.inst@2.0.3 want: 3.19.10 43 silly fetch manifest alexa-remote2@^5.8.3 44 silly fetch manifest https@^1.0.0 45 silly fetch manifest @sentry/node@^7.16.0 46 silly fetch manifest @sentry/integrations@^7.16.0 47 http fetch GET 200 https://registry.npmjs.org/alexa-remote2 1012ms (cache hit) 48 http fetch GET 200 https://registry.npmjs.org/https 1016ms (cache hit) 49 http fetch GET 200 https://registry.npmjs.org/@sentry%2fnode 1022ms (cache hit) 50 http fetch GET 200 https://registry.npmjs.org/@sentry%2fintegrations 1028ms (cache hit) 51 timing idealTree:#root Completed in 2720ms 52 silly placeDep node_modules/iobroker.alexa2 @sentry/integrations@7.17.0 OK for: iobroker.alexa2@3.19.10 want: ^7.16.0 53 silly placeDep node_modules/iobroker.alexa2 @sentry/node@7.17.0 OK for: iobroker.alexa2@3.19.10 want: ^7.16.0 54 silly placeDep ROOT alexa-remote2@5.8.3 OK for: iobroker.alexa2@3.19.10 want: ^5.8.3 55 silly placeDep ROOT https@1.0.0 OK for: iobroker.alexa2@3.19.10 want: ^1.0.0 56 silly fetch manifest @sentry/types@7.17.0 57 silly fetch manifest @sentry/utils@7.17.0 58 silly fetch manifest @sentry/core@7.17.0 59 silly fetch manifest cookie@^0.4.1 60 silly fetch manifest alexa-cookie2@^4.1.3 61 silly fetch manifest querystring@^0.2.1 62 silly fetch manifest ws@^8.8.1 63 silly fetch manifest uuid@^8.3.2 64 http fetch GET 200 https://registry.npmjs.org/@sentry%2ftypes 39ms (cache hit) 65 http fetch GET 200 https://registry.npmjs.org/@sentry%2fcore 46ms (cache hit) 66 http fetch GET 200 https://registry.npmjs.org/cookie 51ms (cache hit) 67 http fetch GET 200 https://registry.npmjs.org/querystring 53ms (cache hit) 68 http fetch GET 200 https://registry.npmjs.org/uuid 54ms (cache hit) 69 http fetch GET 200 https://registry.npmjs.org/alexa-cookie2 60ms (cache hit) 70 http fetch GET 200 https://registry.npmjs.org/ws 62ms (cache hit) 71 http fetch GET 200 https://registry.npmjs.org/@sentry%2futils 72ms (cache hit) 72 timing idealTree:node_modules/iobroker.alexa2 Completed in 91ms 73 silly fetch manifest bufferutil@^4.0.1 74 http fetch GET 200 https://registry.npmjs.org/bufferutil 10ms (cache hit) 75 silly fetch manifest utf-8-validate@^5.0.2 76 http fetch GET 200 https://registry.npmjs.org/utf-8-validate 8ms (cache hit) 77 silly placeDep ROOT alexa-cookie2@4.1.3 OK for: alexa-remote2@5.8.3 want: ^4.1.3 78 silly placeDep ROOT querystring@0.2.1 OK for: alexa-remote2@5.8.3 want: ^0.2.1 79 silly placeDep node_modules/alexa-remote2 uuid@8.3.2 OK for: alexa-remote2@5.8.3 want: ^8.3.2 80 silly placeDep node_modules/alexa-remote2 ws@8.10.0 OK for: alexa-remote2@5.8.3 want: ^8.8.1 81 silly fetch manifest http-proxy-middleware@^2.0.6 82 silly fetch manifest http-proxy-response-rewrite@^0.0.1 83 http fetch GET 200 https://registry.npmjs.org/http-proxy-middleware 23ms (cache hit) 84 http fetch GET 200 https://registry.npmjs.org/http-proxy-response-rewrite 26ms (cache hit) 85 timing idealTree:node_modules/alexa-remote2 Completed in 83ms 86 silly fetch manifest @types/express@^4.17.13 87 http fetch GET 200 https://registry.npmjs.org/@types%2fexpress 10ms (cache hit) 88 silly placeDep ROOT http-proxy-middleware@2.0.6 OK for: alexa-cookie2@4.1.3 want: ^2.0.6 89 silly placeDep ROOT http-proxy-response-rewrite@0.0.1 OK for: alexa-cookie2@4.1.3 want: ^0.0.1 90 silly fetch manifest @types/http-proxy@^1.17.8 91 silly fetch manifest http-proxy@^1.18.1 92 silly fetch manifest is-plain-obj@^3.0.0 93 silly fetch manifest micromatch@^4.0.2 94 silly fetch manifest bufferhelper@^0.2.1 95 http fetch GET 200 https://registry.npmjs.org/bufferhelper 17ms (cache hit) 96 http fetch GET 200 https://registry.npmjs.org/@types%2fhttp-proxy 22ms (cache hit) 97 http fetch GET 200 https://registry.npmjs.org/is-plain-obj 21ms (cache hit) 98 http fetch GET 200 https://registry.npmjs.org/http-proxy 23ms (cache hit) 99 http fetch GET 200 https://registry.npmjs.org/micromatch 23ms (cache hit) 100 timing idealTree:node_modules/alexa-cookie2 Completed in 57ms 101 silly placeDep ROOT @types/http-proxy@1.17.9 OK for: http-proxy-middleware@2.0.6 want: ^1.17.8 102 silly placeDep ROOT http-proxy@1.18.1 OK for: http-proxy-middleware@2.0.6 want: ^1.18.1 103 silly placeDep node_modules/http-proxy-middleware is-plain-obj@3.0.0 OK for: http-proxy-middleware@2.0.6 want: ^3.0.0 104 silly placeDep ROOT micromatch@4.0.5 OK for: http-proxy-middleware@2.0.6 want: ^4.0.2 105 timing idealTree:node_modules/http-proxy-middleware Completed in 16ms 106 timing idealTree:node_modules/@types/http-proxy Completed in 0ms 107 timing idealTree:node_modules/http-proxy Completed in 0ms 108 silly placeDep ROOT bufferhelper@0.2.1 OK for: http-proxy-response-rewrite@0.0.1 want: ^0.2.1 109 timing idealTree:node_modules/http-proxy-response-rewrite Completed in 4ms 110 timing idealTree:node_modules/bufferhelper Completed in 0ms 111 timing idealTree:node_modules/https Completed in 0ms 112 timing idealTree:node_modules/micromatch Completed in 0ms 113 timing idealTree:node_modules/querystring Completed in 0ms 114 timing idealTree:node_modules/alexa-remote2/node_modules/uuid Completed in 0ms 115 timing idealTree:node_modules/alexa-remote2/node_modules/ws Completed in 0ms 116 timing idealTree:node_modules/http-proxy-middleware/node_modules/is-plain-obj Completed in 1ms 117 silly placeDep node_modules/iobroker.alexa2 @sentry/types@7.17.0 OK for: @sentry/integrations@7.17.0 want: 7.17.0 118 silly placeDep node_modules/iobroker.alexa2/node_modules/@sentry/integrations @sentry/utils@ OK for: @sentry/integrations@7.17.0 want: 7.17.0 119 timing idealTree:node_modules/iobroker.alexa2/node_modules/@sentry/integrations Completed in 12ms 120 silly placeDep node_modules/iobroker.alexa2 @sentry/core@7.17.0 OK for: @sentry/node@7.17.0 want: 7.17.0 121 silly placeDep node_modules/iobroker.alexa2/node_modules/@sentry/node @sentry/utils@ OK for: @sentry/node@7.17.0 want: 7.17.0 122 silly placeDep node_modules/iobroker.alexa2 cookie@0.4.2 OK for: @sentry/node@7.17.0 want: ^0.4.1 123 timing idealTree:node_modules/iobroker.alexa2/node_modules/@sentry/node Completed in 45ms 124 silly placeDep node_modules/iobroker.alexa2/node_modules/@sentry/core @sentry/utils@ OK for: @sentry/core@7.17.0 want: 7.17.0 125 timing idealTree:node_modules/iobroker.alexa2/node_modules/@sentry/core Completed in 5ms 126 timing idealTree:node_modules/iobroker.alexa2/node_modules/@sentry/types Completed in 0ms 127 timing idealTree:node_modules/iobroker.alexa2/node_modules/cookie Completed in 0ms 128 timing idealTree:node_modules/iobroker.alexa2/node_modules/@sentry/core/node_modules/@sentry/utils Completed in 0ms 129 timing idealTree:node_modules/iobroker.alexa2/node_modules/@sentry/integrations/node_modules/@sentry/utils Completed in 0ms 130 timing idealTree:node_modules/iobroker.alexa2/node_modules/@sentry/node/node_modules/@sentry/utils Completed in 0ms 131 timing idealTree:buildDeps Completed in 3045ms 132 timing idealTree:fixDepFlags Completed in 81ms 133 timing idealTree Completed in 5147ms 134 timing command:install Completed in 5162ms 135 verbose type version 136 verbose stack @sentry/utils: No matching version found for @sentry/utils@7.17.0. 136 verbose stack at module.exports (/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23) 136 verbose stack at RegistryFetcher.manifest (/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:125:22) 137 verbose cwd /opt/iobroker 138 verbose Linux 5.15.64-1-pve 139 verbose node v16.18.0 140 verbose npm v8.19.2 141 error code ETARGET 142 error notarget No matching version found for @sentry/utils@7.17.0. 143 error notarget In most cases you or one of your dependencies are requesting 143 error notarget a package version that doesn't exist. 144 verbose exit 1 145 timing npm Completed in 5402ms 146 verbose unfinished npm timer reify 1666877587370 147 verbose unfinished npm timer reify:loadTrees 1666877587378 148 verbose code 1 149 error A complete log of this run can be found in: 149 error /home/iobroker/.npm/_logs/2022-10-27T13_33_07_142Z-debug-0.log ilovegym@VMC123-iobroker /opt/iobroker $ -
User berichtet es geht jetzt
-
@apollon77 ja, lief jetzt durch, Adapter geht wieder, Danke fuers Update!
-
@apollon77 Adapter installation auf 3.19.10 kein Problem, aber SmartDevices gehen (noch ) nicht.
-
@toste sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
aber SmartDevices gehen (noch ) nicht.
Ja ich hoffe ich bekomme noch Rückmeldung von Amazon zum Warum.
Ich hoffe Inständig das nicht irgendwelche "dummen User" (sorry) den Adapter-Code anpassen um die Smart Home device infos schneller zu laden und damit Probleme für alle anderen verursachen.
-
@apollon77 sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
"dummen User" (sorry) den Adapter-Code anpassen um die Smart Home device infos schneller zu laden
Da kannste aber sicher sein ! Kommt ja nicht umsonst alle paar Wochen vor dass mal wieder ein Riegel reingeschoben wird.
-
@apollon77 Wäre sehr ärgerlich. Die Akzeptanz hier im Hause sinkt von mal zu mal. Aber gibt es alternativen?
-
@djmarc75 naja wenn dem so sein sollte und Amazon nicht die verursachenden user separat behandeln und sperren möchte oder anschreiben, bleibt nur die Variante das Smart Home daten laden wieder auszubauen
-
-
@djmarc75 sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
@homoran sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
warum noch ein Thread???
???
..
-
@toste Verbinde die Geräte nicht mit Amazon only sondern nutze welche die von nativen Adaptern unterstützt werden
-
@apollon77 sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
bleibt nur die Variante das Smart Home daten laden wieder auszubauen
mich würde das nicht jucken, ich nutze eh weder Räume noch Skills in der AlexaApp.
Aber ich spreche da nur für mich ! -
@toste sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
@apollon77 aber SmartDevices gehen (noch ) nicht.
bei mir gehen sie, ob sie vor 2 Std auch funktioniert haben. Kann ich nicht sagen
-
Smart Home Devices (TUYA-Geräte) sind zwar in den Objekten vorhanden, lassen sich aber nicht schalten.
-
@old_engineer bitte mal warten da die SmartHomeDevices seitens Amazon im Moment nicht funktionieren.... und bitte nicht den Adapter unnötig neu starten und auch nicht manuell nach SmartHomeDevices scannen!
-
@djmarc75 said in [FIX available] Alexa per Alexa2 Totalausfall !?:
@old_engineer bitte mal warten da die SmartHomeDevices seitens Amazon im Moment nicht funktionieren.... und bitte nicht den Adapter unnötig neu starten und auch nicht manuell nach SmartHomeDevices scannen!
OK, dann warte ich mal. Ich habe angefangen die Tuya Geräte redundant über Alexa zu steuern, da der Tuya Adapter auch gerne aussteigt.
-
@old_engineer sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
da der Tuya Adapter auch gerne aussteigt.
Da hätte ich ja gern in nem anderen Thread oder einerm GitHub Issue Beweise für.
-
Hatte das schon mal gepostet, aber kein Issue auf Github aufgemacht. Versuche das nochmal nachzustellen, aber im Grunde bin ich durch die Nutzung per Alexa vom TUYA Adapter weg.
https://forum.iobroker.net/topic/53243/tuya-stürzt-ab-bei-fehlendem-gerät?_=1666899214200
-
@old_engineer sagte in [FIX available] Alexa per Alexa2 Totalausfall !?:
aber im Grunde bin ich durch die Nutzung per Alexa vom TUYA Adapter weg.
bin ehrlich ... Blöde Idee (kein Angriff). Lokal KANN NUR besser sein als über Alexa ...
