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

Seit der Umstellung vom 1.3.2024 immer wieder diesen Fehler ! #114

Open
ManiacKill opened this issue Mar 26, 2024 · 7 comments
Open

Seit der Umstellung vom 1.3.2024 immer wieder diesen Fehler ! #114

ManiacKill opened this issue Mar 26, 2024 · 7 comments

Comments

@ManiacKill
Copy link

innogy-smarthome.0 | 2024-03-26 01:53:01.833 | warn | Adapter is still not connected to the Innogy API, restarting! -- | -- | -- | -- innogy-smarthome.0 | 2024-03-26 01:52:31.785 | warn | Adapter is not connected ... Will recheck in 30 seconds!

Das kommt so ca alle 3 Stunden vor !
@Apollon77
Copy link
Collaborator

Please add more debug log

@ManiacKill
Copy link
Author

ManiacKill commented Mar 27, 2024 •
edited
Loading

Das konnte ich jetzt mal einfangen,

- 2024-03-27 10:35:53.723  - �[33mwarn�[39m: innogy-smarthome.0 (2017) Adapter is still not connected to the Innogy API, restarting!
- 2024-03-27 10:35:53.723  - �[34mdebug�[39m: innogy-smarthome.0 (2017) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
- 2024-03-27 10:35:53.762  - �[34mdebug�[39m: innogy-smarthome.0 (2017) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
- 2024-03-27 10:35:53.764  - �[35msilly�[39m: innogy-smarthome.0 (2017) States user redis pmessage innogy-smarthome.0.*/innogy-smarthome.0.info.connection:{"val":false,"ack":true,"ts":1711532153762,"q":0,"from":"system.adapter.innogy-smarthome.0","user":"system.user.admin","lc":1711531919931}
- 2024-03-27 10:35:53.764  - �[34mdebug�[39m: innogy-smarthome.0 (2017) state innogy-smarthome.0.info.connection changed: false (ack = true)
- 2024-03-27 10:35:53.813  - �[35msilly�[39m: innogy-smarthome.0 (2017) States user redis pmessage innogy-smarthome.0.*/innogy-smarthome.0.info.connection:{"val":false,"ack":true,"ts":1711532153812,"q":0,"from":"system.adapter.innogy-smarthome.0","user":"system.user.admin","lc":1711531919931}
- 2024-03-27 10:35:53.813  - �[34mdebug�[39m: innogy-smarthome.0 (2017) state innogy-smarthome.0.info.connection changed: false (ack = true)
- 2024-03-27 10:36:00.756  - �[35msilly�[39m: innogy-smarthome.0 (2017) States user redis pmessage innogy-smarthome.0.*/innogy-smarthome.0.info.connection:{"val":true,"ack":true,"ts":1711532160756,"q":0,"from":"system.adapter.innogy-smarthome.0","user":"system.user.admin","lc":1711532160756}
- 2024-03-27 10:36:00.757  - �[34mdebug�[39m: innogy-smarthome.0 (2017) state innogy-smarthome.0.info.connection changed: true (ack = true)
- 2024-03-27 10:36:00.757  - �[32minfo�[39m: innogy-smarthome.0 (2017) Initialization sequence completed: found 13 devices
- 2024-03-27 10:36:00.757  - �[34mdebug�[39m: innogy-smarthome.0 (2017) Processing device -> Virtual.Notification-Sender: "Notification Sender"
- 2024-03-27 10:36:00.757  - �[34mdebug�[39m: innogy-smarthome.0 (2017) Device State: []

@JBSullivan
Copy link

JBSullivan commented Mar 27, 2024 •
edited
Loading

Du hast den Adapter aber schon auf das Lokale Smart Home umgestellt und das dort selbst vergebene Passwort eingetragen?

Die Cloud ist Tot, die Innogy/Livisi Dienste sind seit dem 1.3. abgeschaltet. Das ist aber eigentlich schon seit 2 Jahren bekannt, das man den Adapter auf die lokalen Smart Settings umstellen muss.

@ Apollon77 Von daher wäre es vielleicht ganz gut, wenn man in den Adapter Instanz Einstellungen die Option sich an der Cloud anmelden zu können, ganz entfernt. Die Cloud gibt es seit dem 1.3.24 nicht mehr und das führt ggf. nur zu Verwirrungen.

image

Das hier funktioniert nicht mehr.

image

@Apollon77
Copy link
Collaborator

@ManiacKill Und ein bissl log von vor der Meldung? :-)

@ManiacKill
Copy link
Author

Hallo,

ja schon lange auf Lokal umgestellt, aber der Fehler kommt immer wieder mal,

  • 2024-04-24 10:44:16.536 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.info.lastRealTimeEventReceived changed: 2024-04-24T08:44:16.534Z (ack = true)
    2024-04-24 10:44:16.537 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.Hauswirtschaftsraum.PV-Wechselrichter.Energy-Sensor.TotalEnergy changed: 91329.99 (ack = true)
    2024-04-24 10:44:16.537 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.Hauswirtschaftsraum.PV-Wechselrichter.Energy-Sensor.EnergyPerDayInKWh changed: 55.86 (ack = true)
    2024-04-24 10:44:16.538 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.Hauswirtschaftsraum.PV-Wechselrichter.Energy-Sensor.EnergyPerDayInEuro changed: 0 (ack = true)
    2024-04-24 10:44:16.539 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.Hauswirtschaftsraum.PV-Wechselrichter.Energy-Sensor.EnergyPerMonthInKWh changed: 766.03 (ack = true)
    2024-04-24 10:44:16.579 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.Hauswirtschaftsraum.PV-Wechselrichter.Energy-Sensor.EnergyPerMonthInEuro changed: 0 (ack = true)
    2024-04-24 10:44:16.579 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.Hauswirtschaftsraum.PV-Wechselrichter.Power-Generation-Sensor.PowerInWatt changed: 1850 (ack = true)
    2024-04-24 10:44:16.580 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.Hauswirtschaftsraum.PV-Wechselrichter.Generation-Control.MaximumGenerationPower changed: 10000 (ack = true)
    2024-04-24 10:44:17.808 - �[33mwarn�[39m: innogy-smarthome.0 (1562) Adapter is still not connected to the Innogy API, restarting!
    2024-04-24 10:44:17.809 - �[34mdebug�[39m: innogy-smarthome.0 (1562) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
    2024-04-24 10:44:17.863 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.info.connection changed: false (ack = true)
    2024-04-24 10:44:17.918 - �[34mdebug�[39m: innogy-smarthome.0 (1562) SOCKET CONNECTION TO THE INNOGY API WAS CLOSED
    2024-04-24 10:44:17.962 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.info.connection changed: false (ack = true)
    2024-04-24 10:44:28.558 - �[34mdebug�[39m: innogy-smarthome.0 (1562) state innogy-smarthome.0.info.connection changed: true (ack = true)
    2024-04-24 10:44:28.558 - �[32minfo�[39m: innogy-smarthome.0 (1562) Initialization sequence completed: found 13 devices
    2024-04-24 10:44:28.558 - �[34mdebug�[39m: innogy-smarthome.0 (1562) Processing device -> Virtual.Notification-Sender: "Notification Sender"
    2024-04-24 10:44:28.558 - �[34mdebug�[39m: innogy-smarthome.0 (1562) Device State: []

@Apollon77
Copy link
Collaborator

naja die Frage ist was daran jetzt "das problem" ist?
Die Innogy Base hat die Verbindung die ioBroker geöffnet hat von sich aus geschlossen. grund für ioBroker erstmal unbekannt. Dann versucht er die verbindung wiederherzustellen was dann nach 10s passiet ist.

Ok vllt ist die Meldung mit "still not connected" komisch ... :-)

@ManiacKill
Copy link
Author

Moien, ne kein Problem ist eben immer wieder im Log. Aber funktionierten tut es ja !

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
@ManiacKill @Apollon77 @JBSullivan