Weihnachtsangebot 2025! 🎄

[Ro75]

@tombox Dann gibt es wohl eine neue Version, hatte bisher nicht einfach so geladen.

[jr]

@tombox auch mit dem aktuellen leider keine Änderung, die Anzeige kommt und geht, im Log immer wieder "No Amazon orders found"

[Ro75]

Ich hatte @tombox geschrieben gehabt, dass Amazon selber nicht das Problem ist. Das Sorgenkind sind die Daten in DP "parcel.0.allProviderJson". Dieser ist mal gefüllt dann wieder leer dann wieder gefüllt usw.

[oFbEQnpoLKKl6mbY5e13]

@tombox

Ich habe heute ein Update von 0.0.28 auf 0.0.30 durchgeführt:

2023-06-07 20:34:13.658  - info: host.iobroker Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
2023-06-07 20:34:29.719  - info: host.iobroker iobroker upgrade parcel@0.0.30 --debug
2023-06-07 20:34:32.902  - info: host.iobroker iobroker Update parcel from @0.0.28 to @0.0.30
2023-06-07 20:34:35.515  - info: host.iobroker iobroker NPM version: 9.5.1
2023-06-07 20:34:35.518  - info: host.iobroker iobroker Installing iobroker.parcel@0.0.30... (System call)
2023-06-07 20:34:57.166  - info: host.iobroker iobroker 
2023-06-07 20:34:57.168  - info: host.iobroker iobroker removed 722 packages, and changed 4 packages in 20s172 packages are looking for funding  run `npm fund` for details
2023-06-07 20:34:57.264  - info: host.iobroker iobroker Update "system.adapter.parcel.1"
2023-06-07 20:34:57.278  - info: host.iobroker stopInstance system.adapter.parcel.1 (force=false, process=true)
2023-06-07 20:34:57.285  - info: host.iobroker iobroker Update "system.adapter.parcel.0"
2023-06-07 20:34:57.297  - info: host.iobroker stopInstance system.adapter.parcel.1 send kill signal
2023-06-07 20:34:57.299  - info: host.iobroker stopInstance system.adapter.parcel.0 (force=false, process=true)
2023-06-07 20:34:57.298  - info: parcel.1 (9522) Got terminate signal TERMINATE_YOURSELF
2023-06-07 20:34:57.310  - info: host.iobroker stopInstance system.adapter.parcel.0 send kill signal
2023-06-07 20:34:57.311  - info: parcel.0 (9192) Got terminate signal TERMINATE_YOURSELF
2023-06-07 20:34:57.318  - info: parcel.0 (9192) terminating
2023-06-07 20:34:57.322  - info: parcel.0 (9192) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-06-07 20:34:57.317  - info: parcel.1 (9522) terminating
2023-06-07 20:34:57.323  - info: parcel.1 (9522) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-06-07 20:34:57.398  - info: host.iobroker iobroker upload [3] parcel.admin /opt/iobroker/node_modules/iobroker.parcel/admin/index_m.html index_m.html text/html
2023-06-07 20:34:57.976  - info: host.iobroker instance system.adapter.parcel.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-06-07 20:34:58.051  - info: host.iobroker iobroker upload [2] parcel.admin /opt/iobroker/node_modules/iobroker.parcel/admin/parcel.png parcel.png image/pngupload [1] parcel.admin /opt/iobroker/node_modules/iobroker.parcel/admin/style.css style.css text/cssupload [0] parcel.admin /opt/iobroker/node_modules/iobroker.parcel/admin/words.js words.js application/javascript
2023-06-07 20:34:58.054  - info: host.iobroker instance system.adapter.parcel.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-06-07 20:34:58.975  - info: host.iobroker iobroker exit 0
2023-06-07 20:35:00.441  - info: host.iobroker instance system.adapter.parcel.1 started with pid 2254
2023-06-07 20:35:00.469  - info: host.iobroker instance system.adapter.parcel.0 started with pid 2255
2023-06-07 20:35:04.668  - info: parcel.0 (2255) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2023-06-07 20:35:04.744  - info: parcel.1 (2254) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2023-06-07 20:35:05.166  - info: parcel.1 (2254) starting. Version 0.0.30 in /opt/iobroker/node_modules/iobroker.parcel, node: v18.16.0, js-controller: 4.0.24
2023-06-07 20:35:05.178  - info: parcel.0 (2255) starting. Version 0.0.30 in /opt/iobroker/node_modules/iobroker.parcel, node: v18.16.0, js-controller: 4.0.24
2023-06-07 20:35:05.535  - info: parcel.0 (2255) Login to DHL
2023-06-07 20:35:05.553  - info: parcel.1 (2254) Login to Amazon
2023-06-07 20:35:07.859  - info: parcel.0 (2255) Login to DHL successful
2023-06-07 20:35:07.879  - info: parcel.0 (2255) Login to Amazon
2023-06-07 20:35:08.437  - info: parcel.1 (2254) Login to Amazon successful
2023-06-07 20:35:10.588  - info: parcel.0 (2255) Login to Amazon successful

Danach waren alle Amazon Lieferungen vorhanden. Dann plötzlich:

2023-06-07 20:55:16.034  - warn: parcel.1 (2254) No Amazon orders found
2023-06-07 20:55:18.081  - info: parcel.1 (2254) Login to Amazon successful
2023-06-07 20:55:40.328  - warn: parcel.0 (2255) No Amazon orders found
2023-06-07 20:55:43.566  - info: parcel.0 (2255) Login to Amazon successful

[DJMarc75]

Hab vorhin auf die GIT 0.0.30 upgedatet.
Das Login bei Hermes scheint gefixed allerdings wirft das LOG nach Neustart Folgendes aus:

parcel.0
	2023-06-08 11:37:26.724	info	undefined is not a valid state value for id "parcel.0.hermes.sendungen06.id"
parcel.0
	2023-06-08 11:37:26.719	info	undefined is not a valid state value for id "parcel.0.hermes.sendungen05.id"
parcel.0
	2023-06-08 11:37:26.693	info	undefined is not a valid state value for id "parcel.0.hermes.sendungen04.id"
parcel.0
	2023-06-08 11:37:26.692	info	undefined is not a valid state value for id "parcel.0.hermes.sendungen03.id"
parcel.0
	2023-06-08 11:37:26.691	info	undefined is not a valid state value for id "parcel.0.hermes.sendungen02.id"
parcel.0
	2023-06-08 11:37:26.687	info	undefined is not a valid state value for id "parcel.0.hermes.sendungen01.id"
parcel.0
	2023-06-08 11:37:26.654	warn	This object will not be created in future versions. Please report this to the developer.
parcel.0
	2023-06-08 11:37:26.654	warn	Object parcel.0.hermes.sendungen06.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
parcel.0
	2023-06-08 11:37:26.648	warn	This object will not be created in future versions. Please report this to the developer.
parcel.0
	2023-06-08 11:37:26.648	warn	Object parcel.0.hermes.sendungen05.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
parcel.0
	2023-06-08 11:37:26.648	warn	This object will not be created in future versions. Please report this to the developer.
parcel.0
	2023-06-08 11:37:26.648	warn	Object parcel.0.hermes.sendungen04.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
parcel.0
	2023-06-08 11:37:26.648	warn	This object will not be created in future versions. Please report this to the developer.
parcel.0
	2023-06-08 11:37:26.648	warn	Object parcel.0.hermes.sendungen03.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
parcel.0
	2023-06-08 11:37:26.648	warn	This object will not be created in future versions. Please report this to the developer.
parcel.0
	2023-06-08 11:37:26.648	warn	Object parcel.0.hermes.sendungen02.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
parcel.0
	2023-06-08 11:37:26.648	warn	This object will not be created in future versions. Please report this to the developer.
parcel.0
	2023-06-08 11:37:26.647	warn	Object parcel.0.hermes.sendungen01.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
parcel.0
	2023-06-08 11:37:22.156	info	Login to Hermes successful
parcel.0
	2023-06-08 11:37:21.774	info	Login to Hermes

[bommel_030]

Hab auch auf die 0.0.30 aktualisiert. Hermes gibt im LOG nichts mehr aus. Dafür habe ich (bei einem Abrufintervall von 15 min ?!?) alle 30 min die Warnmeldung "No Amazon orders found". Grundsätzlich nicht verkehrt, weil aktuell nichts bestellt, aber sollte das ne Warnung Wert sein?

[Einstein2002]

Hallo,
was muss ich machen damit ich mich auf Amazon anmelden kann??

parcel.0
2023-06-09 16:00:23.972	error	MFA: Login to Amazon failed, please login manually to Amazon

parcel.0
2023-06-09 16:00:23.542	info	Found MFA token login

parcel.0
2023-06-09 16:00:22.234	info	Login to Amazon

parcel.0
2023-06-09 16:00:22.229	info	Login to DHL successful

parcel.0
2023-06-09 16:00:20.161	info	Login to DHL

parcel.0
2023-06-09 16:00:20.143	info	starting. Version 0.0.30 (non-npm: TA2k/ioBroker.parcel) in /opt/iobroker/node_modules/iobroker.parcel, node: v18.16.0, js-controller: 4.0.24

[Einstein2002]

Ich finde den hier nicht.

Amazon OTP Token vor dem Login eingeben, falls 2FA aktiviert ist

Wo auf Amazon ist der versteckt??

[Einstein2002]

@ofbeqnpolkkl6mby5e13

Wie hast Du den login bei Amazon bewältigt??
2FA abgeschaltet??

[Einstein2002]

Nachdem ich die 2FA abgeschaltet habe klappt der Login, aber wie geht es mit Aktiver 2FA ??? Bitte um einen Lösungsvorschlag oder ein kleinen Tipp

[Ro75]

@einstein2002 Gib im Adapter deine Login-Daten ein und den aktuellen 2FA-Schlüssel (sollte noch etwas Restzeit da sein damit dieser gültig ist). Adaptereinstellungen speichern und schließen.

[Einstein2002]

@ro75
Hatte ich so probiert, habe mich am PC bei Amazon angemeldet und den Schlüssel dann im Adapter eingegeben, hatte nicht geklappt, am PC die gleichen Zahlen und ich war angemeldet

[Einstein2002]

Jetzt geht es. Warum auch immer.
Danke.

[DJMarc75]

@einstein2002 sagte in Adapter Paketverfolgung DHL, Briefe, Amazon, DPD,GLS,UPS,17T:

Kennt einer von Euch diese Meldung??
Alexa-Push-Connection disconnected
Die kommt alle paar Minuten als Info in den Protokollen

Was hat das jetzt hier zu suchen ?

[Ro75]

Hallo. Gibt es schon neue Erkenntnisse zu dem Amazon-Problem? Da - weg - da - weg - da - ...?

Ro75.

[eWeem]

Hallo, leider habe ich das Problem dass ich bei Benutzung von 2 Instanzen, die zweite nicht funktioniert. Leider bin ich nicht so in der Materie.

2023-06-23 09:56:34.266 - info: parcel.1 (12992) starting. Version 0.0.30 (non-npm: TA2k/ioBroker.parcel#8c8f3dd2f36aba1c8414cbfaf33dec376af56cf7) in C:/ioBroker/node_modules/iobroker.parcel, node: v18.16.0, js-controller: 5.0.3
2023-06-23 09:56:34.288 - info: parcel.1 (12992) Login to DHL
2023-06-23 09:56:36.830 - info: parcel.1 (12992) Login to DHL successful
2023-06-23 09:56:36.850 - info: parcel.1 (12992) Login to DPD
2023-06-23 09:56:39.980 - info: parcel.1 (12992) Login to DPD successful
2023-06-23 09:56:40.565 - info: parcel.1 (12992) Login to Hermes
2023-06-23 09:56:40.975 - info: parcel.1 (12992) Login to Hermes successful
2023-06-23 09:56:46.639 - warn: parcel.1 (12992) Object parcel.1.hermes.sendungen01.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
2023-06-23 09:56:46.641 - warn: parcel.1 (12992) This object will not be created in future versions. Please report this to the developer.
2023-06-23 09:56:46.642 - warn: parcel.1 (12992) Object parcel.1.hermes.sendungen02.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json
2023-06-23 09:56:46.642 - warn: parcel.1 (12992) This object will not be created in future versions. Please report this to the developer.
2023-06-23 09:56:46.680 - error: parcel.1 (12992) 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().
2023-06-23 09:56:46.680 - error: parcel.1 (12992) unhandled promise rejection: undefined is not a valid state value
2023-06-23 09:56:46.774 - error: parcel.1 (12992) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (C:\ioBroker\node_modules\@iobroker\js-controller-common\src\lib\common\maybeCallback.ts:136:17)
at Parcel._setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7468:26)
at Parcel.setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7426:21)
at C:\ioBroker\node_modules\iobroker.parcel\lib\json2iob.js:126:34
at runNextTicks (node:internal/process/task_queues:60:5)
at processImmediate (node:internal/timers:447:9)
2023-06-23 09:56:46.774 - error: parcel.1 (12992) undefined is not a valid state value
2023-06-23 09:56:46.785 - info: parcel.1 (12992) terminating
2023-06-23 09:56:46.786 - warn: parcel.1 (12992) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-06-23 09:56:46.802 - error: parcel.1 (12992) 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().
2023-06-23 09:56:46.803 - error: parcel.1 (12992) unhandled promise rejection: undefined is not a valid state value
2023-06-23 09:56:46.804 - error: parcel.1 (12992) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (C:\ioBroker\node_modules\@iobroker\js-controller-common\src\lib\common\maybeCallback.ts:136:17)
at Parcel._setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7468:26)
at Parcel.setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7426:21)
at C:\ioBroker\node_modules\iobroker.parcel\lib\json2iob.js:126:34
at runNextTicks (node:internal/process/task_queues:60:5)
at processImmediate (node:internal/timers:447:9)
2023-06-23 09:56:46.804 - error: parcel.1 (12992) undefined is not a valid state value
2023-06-23 09:56:47.295 - info: parcel.1 (12992) terminating
2023-06-23 09:56:47.343 - error: host.HOMESERVER 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:
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[0]: Error: undefined is not a valid state value
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[0]: at Object.maybeCallbackWithError (C:\ioBroker\node_modules\@iobroker\js-controller-common\src\lib\common\maybeCallback.ts:136:17)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[0]: at Parcel._setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7468:26)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[0]: at Parcel.setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7426:21)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[0]: at C:\ioBroker\node_modules\iobroker.parcel\lib\json2iob.js:126:34
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[0]: at runNextTicks (node:internal/process/task_queues:60:5)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[0]: at processImmediate (node:internal/timers:447:9)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[1]: 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:
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[2]: Error: undefined is not a valid state value
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[2]: at Object.maybeCallbackWithError (C:\ioBroker\node_modules\@iobroker\js-controller-common\src\lib\common\maybeCallback.ts:136:17)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[2]: at Parcel._setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7468:26)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[2]: at Parcel.setState (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:7426:21)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[2]: at C:\ioBroker\node_modules\iobroker.parcel\lib\json2iob.js:126:34
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
2023-06-23 09:56:47.343 - error: host.HOMESERVER Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
2023-06-23 09:56:47.343 - error: host.HOMESERVER instance system.adapter.parcel.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-06-23 09:56:47.343 - info: host.HOMESERVER Restart adapter system.adapter.parcel.1 because enabled
2023-06-23 09:57:02.735 - info: host.HOMESERVER "system.adapter.parcel.1" disabled

Ich sehe leider bei den JS-Meldungen nicht wirklich durch.

2 Instanzen benötigen wir bei uns, da meine Frau auf ihren Namen natürlich auch Pakete und Briefe erhält.

EDIT: Parcel bleibt allerdings Fehlerfrei wenn ich über die zweite Instanz keine Hermes LogIn-Daten eingebe.

[DJMarc75]

Tag ,
heut mal wieder Hermes mit ins Boot genommen und, naja, bekomme bei jedem Abfrageintervall

parcel.0
	2023-06-24 09:25:58.076	info	undefined is not a valid state value for id "parcel.0.hermes.sendungen01.id"
parcel.0
	2023-06-24 09:25:58.071	warn	This object will not be created in future versions. Please report this to the developer.
parcel.0
	2023-06-24 09:25:58.071	warn	Object parcel.0.hermes.sendungen01.id is invalid: obj.common.type has an invalid value (undefined) but has to be one of number, string, boolean, array, object, mixed, file, json

und somit völlig unbrauchbar da es meine schöne VIS unschön macht :) (und natürlich das LOG vermüllt)
geht´s noch wem so ?

Greets

[Ro75]

Im Moment schein etwas Sand im Getriebe bei diesem Adapter zu sein. Hoffe es wird wieder.

[Ro75]

Aktuell bestehen immer noch Probleme mit Amazon:

1. Amazon Lieferungen werden mal angezeigt, mal nicht - wechselt permanent
2. "Geisterlieferungen" Amazon - diese Lieferungen sind schon längst erledigt. Selbst wenn ich die angezeigte Lieferung "archiviere" bei Amazon, kommt die nächste.

Das macht im Moment keinen Spaß und der Adapter leider keinen Sinn. Gibt es denn eine Chance, dass die Probleme in absehbarer Zeit behoben werden?

Ro75.

[tombox]

@ro75 MAl die github version testen für amazon