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.

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

Bug report: Instance keeps in warning-mode, even if everything is working fine #89

Open
1 of 2 tasks
JM2014 opened this issue Mar 13, 2023 · 0 comments
Open
1 of 2 tasks
Labels
bug Something isn't working

Comments

@JM2014
Copy link

JM2014 commented Mar 13, 2023

The problem

Bug:
The instance keeps in warning-state in ioborker-instance-view, when it recognizes that another session "stole" the connectivity for a while and reconnects again.
If the other system disconnects, the comfairq is again delivering data to the iobroker objects, but it remains in warning (yellow)-sate.

Expectation:
The comfoairq-instance should go in green-state under iobroker-instances view after a successful reconnect.

Versions:
I am using v.0.3.0 and the beta-train of iobroker.

Assumption:
It seems that the instance is not updating the instance.-status, after reestablishing a connection.

Version of nodejs

v16.19.1

Version of ioBroker js-controller

4.0.24

Version of Adapter

0.3.0
comfo2

Operating system running ioBroker

Linux

Checklist of files to include below

  • iobroker.current.log (Please share the logs in debug mode)
  • Contents of the JavaScript browser console (always include in cases of issues with the user interface)

Additional information & file uploads

comfo1.txt
Uploading comfo2.png…

@JM2014 JM2014 added the bug Something isn't working label Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant