Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

During connection always throws ERRORS #48

Open
MichaelSchaaf999 opened this issue Jan 1, 2023 · 15 comments
Open

During connection always throws ERRORS #48

MichaelSchaaf999 opened this issue Jan 1, 2023 · 15 comments

Comments

@MichaelSchaaf999
Copy link

Hi,
unfortunately the app throws errors while having successful connections to the server:

zoe2.0 2023-01-01 10:45:04.386 error Cannot read property 'status' of undefined
zoe2.0 2023-01-01 10:45:04.386 error TypeError: Cannot read property 'status' of undefined at /opt/iobroker/node_modules/iobroker.zoe2/main.js:363:29 at processTicksAndRejections (internal/process/task_queues.js:95:5)
zoe2.0 2023-01-01 10:45:04.385 error unhandled promise rejection: Cannot read property 'status' of undefined
zoe2.0 2023-01-01 10:45:04.385 error 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().
zoe2.0 2023-01-01 10:45:04.385 error Error in step 5, errorCode: 2
zoe2.0 2023-01-01 10:45:04.384 error Error: timeout of 3000ms exceeded
zoe2.0 2023-01-01 10:45:04.384 error Maybe Kamereon-API Key has changed, please check https://github.com/fungus75/ioBroker.zoe2/wiki
zoe2.0 2023-01-01 10:45:04.383 error No valid response1 from getKamereonAccount service

The necessary values are being transferred correct, though.
What can we do to avoid these errors?
LG
Michael
@fungus75
Copy link
Owner

fungus75 commented Jan 1, 2023

Hi,

please upgrade to the very last version (use expert-mode in iobrokers-adapters, click on "from own URL" and enter that URL: https://github.com/fungus75/ioBroker.zoe2.git

After upgrading, please re-enter all parameters in setup-screen, also please enter the current API-Key from https://github.com/fungus75/ioBroker.zoe2/wiki

Hopefully it helps,

cu
Fungus

@MichaelSchaaf999
Copy link
Author

Update done, thanks, now:

image

It was not necessary to re-enter all the parameters: Everything was still present.

But:

zoe2.0 2023-01-02 11:30:06.253 error Cannot read property 'status' of undefined
zoe2.0 2023-01-02 11:30:06.252 error TypeError: Cannot read property 'status' of undefined at /opt/iobroker/node_modules/iobroker.zoe2/main.js:580:29 at processTicksAndRejections (internal/process/task_queues.js:95:5)
zoe2.0 2023-01-02 11:30:06.252 error unhandled promise rejection: Cannot read property 'status' of undefined
zoe2.0 2023-01-02 11:30:06.252 error 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().
zoe2.0 2023-01-02 11:30:06.251 error Error in step 9, errorCode: 2
zoe2.0 2023-01-02 11:30:06.251 error Error: timeout of 3000ms exceeded
zoe2.0 2023-01-02 11:30:06.250 error No valid response1 from getLocation service

CU
M.

@Wiednitz
Copy link

Wiednitz commented Jan 2, 2023

Der Adapter läuft zur Zeit ohne Probleme. Aller paar Monate habe ich auch oben genannte Fehler und der Adapter stellt seine Arbeit ein, die Uhr neben dem Adapter ist dauerhaft blau, normal sollte die gelb sein.
Drüber installieren bringt nix, Adapter komplett deinstallieren und neu installieren !

@MichaelSchaaf999
Copy link
Author

--> "Drüber installieren bringt nix, Adapter komplett deinstallieren und neu installieren !"

This leads to some warnings:

"Befehl ausführen

Process exited with code 0
weniger

mehr
$ iobroker url https://github.com/fungus75/ioBroker.zoe2.git --host iobroker --debug
install fungus75/ioBroker.zoe2#759f83fcd615d1e3186185cc8f4ef8b0e8c61f0d
Installing fungus75/ioBroker.zoe2#759f83fcd615d1e3186185cc8f4ef8b0e8c61f0d... (System call)
npm WARN @material-ui/[email protected] requires a peer of @material-ui/core@^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @material-ui/[email protected] requires a peer of react@^16.8.0 || ^17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of buffer@>=6.0.3 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>=16.6.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-dom@>=16.6.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react@>=16.8 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):

added 3 packages from 5 contributors in 72.949s
221 packages are looking for funding run npm fund for details
upload [1] zoe2.admin /opt/iobroker/node_modules/iobroker.zoe2/admin/index_m.html index_m.html text/html
upload [0] zoe2.admin /opt/iobroker/node_modules/iobroker.zoe2/admin/zoe.png zoe.png image/png
Process exited with code 0"

and...
image

But...
No Zoe-instance can be found. Sorry.

@fungus75
Copy link
Owner

fungus75 commented Jan 3, 2023

Update done, thanks, now:

image

It was not necessary to re-enter all the parameters: Everything was still present.

But:

zoe2.0 2023-01-02 11:30:06.253 error Cannot read property 'status' of undefined
zoe2.0 2023-01-02 11:30:06.252 error TypeError: Cannot read property 'status' of undefined at /opt/iobroker/node_modules/iobroker.zoe2/main.js:580:29 at processTicksAndRejections (internal/process/task_queues.js:95:5)
zoe2.0 2023-01-02 11:30:06.252 error unhandled promise rejection: Cannot read property 'status' of undefined
zoe2.0 2023-01-02 11:30:06.252 error 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().
zoe2.0 2023-01-02 11:30:06.251 error Error in step 9, errorCode: 2
zoe2.0 2023-01-02 11:30:06.251 error Error: timeout of 3000ms exceeded
zoe2.0 2023-01-02 11:30:06.250 error No valid response1 from getLocation service
CU M.

Please try to adjust the timeout in setup-screen:
image

@fungus75
Copy link
Owner

fungus75 commented Jan 3, 2023

--> "Drüber installieren bringt nix, Adapter komplett deinstallieren und neu installieren !"

This leads to some warnings:

"Befehl ausführen

Process exited with code 0 weniger

mehr $ iobroker url https://github.com/fungus75/ioBroker.zoe2.git --host iobroker --debug install fungus75/ioBroker.zoe2#759f83fcd615d1e3186185cc8f4ef8b0e8c61f0d Installing fungus75/ioBroker.zoe2#759f83fcd615d1e3186185cc8f4ef8b0e8c61f0d... (System call) npm WARN @material-ui/[email protected] requires a peer of @material-ui/core@^4.0.0 but none is installed. You must install peer dependencies yourself. npm WARN @material-ui/[email protected] requires a peer of react@^16.8.0 || ^17.0.0 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of buffer@>=6.0.3 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of react@>=16.6.0 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of react-dom@>=16.6.0 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of react@>=16.8 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):

added 3 packages from 5 contributors in 72.949s 221 packages are looking for funding run npm fund for details upload [1] zoe2.admin /opt/iobroker/node_modules/iobroker.zoe2/admin/index_m.html index_m.html text/html upload [0] zoe2.admin /opt/iobroker/node_modules/iobroker.zoe2/admin/zoe.png zoe.png image/png Process exited with code 0"

and... image

But... No Zoe-instance can be found. Sorry.

You can use the plus-sign in admin-screen to create an instance if not created automatically:

image

@fungus75
Copy link
Owner

fungus75 commented Jan 3, 2023

It also works in the Tile-Display-Mode

image

@MichaelSchaaf999
Copy link
Author

yes, but this installs 02.5 NOT 02.6

@MichaelSchaaf999
Copy link
Author

MichaelSchaaf999 commented Jan 4, 2023 •
edited
Loading

So: Repeated the installation process...
image
So it says 02.6 has been installed BUT still NO instance can be seen.
Interesting: No number (i.e.: "1") is displayed here as number of installed instances.
So the installation "your own..." with your link does not work correctly.

and by the way: The parameter timeout you mentioned was NOT shown in previous installations, this is the screenshot from your above entry here:
image

What do you recommend?

@MichaelSchaaf999
Copy link
Author

Aktuell:
image

Fehler:

host.iobroker 2023-01-09 14:30:08.668 error instance system.adapter.zoe2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
zoe2.0 2023-01-09 14:30:08.163 error Cannot read property 'status' of undefined
zoe2.0 2023-01-09 14:30:08.163 error TypeError: Cannot read property 'status' of undefined at /opt/iobroker/node_modules/iobroker.zoe2/main.js:532:29 at processTicksAndRejections (internal/process/task_queues.js:95:5)
zoe2.0 2023-01-09 14:30:08.162 error unhandled promise rejection: Cannot read property 'status' of undefined
zoe2.0 2023-01-09 14:30:08.162 error 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().
zoe2.0 2023-01-09 14:30:08.162 error Error in step 8, errorCode: 2
zoe2.0 2023-01-09 14:30:08.161 error Error: timeout of 5000ms exceeded
zoe2.0 2023-01-09 14:30:08.161 error No valid response1 from getCockpit service

Was soll da nun noch geschehen?

LG
M

@fungus75
Copy link
Owner

fungus75 commented Jan 9, 2023

Kommt der Fehler regelmäßig vor, oder nur vereinzelt? Die API ist leider nicht stabil. z.B. um +/- 20:00 Uhr klappt es nicht,... Auch zwischendurch kommt es immer wieder zu Fehler. Aber 90% der Aufrufe sollten schon klappen.

Die im Screenhot angezeigten Fehler sind - so wie es sich für mich darstellt - nur Folgefehler des Timeouts.
Bei mir (allerdings Renault Twingo Electric) klappt es mit 5000 ms Timeout "recht gut", aber wie gesagt, vereinzelt kommt es zu obigen Fehler.

@MichaelSchaaf999
Copy link
Author

Regelmässig.
Ich kann ja auch mal den TimeOut höher setzen, falls das was bringt. 50000 ms oder so?

@fungus75
Copy link
Owner

fungus75 commented Jan 9, 2023

Hast du an dem Intervall vom Adapter geschraubt? Wird der Adapter nach wie vor alle 10 Minuten aufgerufen, oder öfter? Was wir mit einem anderen User schon herausgefunden haben: der Adapter läuft am stabilsten, wenn er allerhöchstens alle 3 Minuten aufgerufen wird. Darüber hinaus limitiert die API wohl.

@MichaelSchaaf999
Copy link
Author

Nein, das Intervall ist unverändert:

image

@MichaelSchaaf999
Copy link
Author

Fehler liegt immer noch vor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fungus75 @MichaelSchaaf999 @Wiednitz