Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Hardware
    4. Growatt exception: Error: {"result":3}

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Growatt exception: Error: {"result":3}

    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nobbiman @Thomas Braun last edited by

      @thomas-braun

      sudo apt update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:3 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:4 http://ftp.debian.org/debian bullseye-backports InRelease [49.0 kB]
Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:7 https://www.debmatic.de/debmatic stable InRelease
Reading package lists... Done
E: Release file for http://deb.debian.org/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for another 2min 50s). Updates for this repository will not be applied.
E: Release file for http://ftp.debian.org/debian/dists/bullseye-backports/InRelease is not valid yet (invalid for another 2min 50s). Updates for this repository will not be applied.
      1 Reply Last reply Reply Quote 0
      • N
        nobbiman @Thomas Braun last edited by

        @thomas-braun

        pi@iobroker-pi:~ $ sudo systemctl enable systemd-timesyncd.service
Failed to enable unit: Unit file systemd-timesyncd.service does not exist.

        Könnte diese Meldung auf die Spur führen? In welches Verzeichnis gehört die Datei und welchen Inhalt hat sie, bzw kann sie automatisch installiert werden?

        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @nobbiman last edited by

          @nobbiman sagte in Growatt exception: Error: {"result":3}:
          Ist das entsprechende Paket nicht installiert?
          Das ist eigentlich immer vorinstalliert.

          sudo apt update
apt policy systemd-timesyncd
          N 1 Reply Last reply Reply Quote 0
          • N
            nobbiman @Thomas Braun last edited by

            @thomas-braun said in Growatt exception: Error: {"result":3}:

            apt policy systemd-timesyncd

            pi@iobroker-pi:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:3 http://security.debian.org/debian-security bullseye-security InRelease [48               .4 kB]
Get:4 http://ftp.debian.org/debian bullseye-backports InRelease [49.0 kB]
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:6 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:7 https://www.debmatic.de/debmatic stable InRelease
Get:8 http://security.debian.org/debian-security bullseye-security/main Sources                [183 kB]
Get:9 http://security.debian.org/debian-security bullseye-security/main armhf Pa               ckages [217 kB]
Get:10 http://security.debian.org/debian-security bullseye-security/main Transla               tion-en [145 kB]
Get:11 http://ftp.debian.org/debian bullseye-backports/main armhf Packages [379                kB]
Get:12 http://ftp.debian.org/debian bullseye-backports/main Translation-en [322                kB]
Fetched 1,388 kB in 2s (601 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
pi@iobroker-pi:~ $ apt policy systemd-timesyncd
systemd-timesyncd:
  Installed: (none)
  Candidate: 247.3-7+deb11u1
  Version table:
     252.4-1~bpo11+1 100
        100 http://ftp.debian.org/debian bullseye-backports/main armhf Packages
     247.3-7+deb11u1 500
        500 http://deb.debian.org/debian bullseye/main armhf Packages
            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @nobbiman last edited by Thomas Braun

              @nobbiman

              Nicht installiert...

              sudo apt install systemd-timesyncd

              Und wo kommen die backports her? Schmeiß das Repository dazu raus.

              N 1 Reply Last reply Reply Quote 0
              • N
                nobbiman @Thomas Braun last edited by nobbiman

                @thomas-braun
                kein Ahnung wo die herkommen wenn nicht von der Version buster.
                Keine Ahnung aber auch, wie ich sie deinstallieren kann.

                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @nobbiman last edited by

                  @nobbiman

                  Vermutlich steht die Quelle in der
                  /etc/apt/sources.list
                  drin.
                  Meine schaut z. B. so aus:

                  deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free
# deb http://deb.debian.org/debian bullseye-backports main contrib non-free

# Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
#deb-src http://deb.debian.org/debian bullseye main contrib non-free
#deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
#deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free
#deb-src http://deb.debian.org/debian bullseye-backports main contrib non-free

                  Man beachte Zeile 4.

                  N 1 Reply Last reply Reply Quote 0
                  • N
                    nobbiman @Thomas Braun last edited by

                    @thomas-braun

                    #deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
deb http://deb.debian.org/debian/ bullseye main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main
deb http://ftp.debian.org/debian bullseye-backports main contrib non-free

                    Und welche müssen raus?

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @nobbiman last edited by

                      @nobbiman

                      Übernimm einfach die Datei so wie die bei mir aussieht.

                      N 1 Reply Last reply Reply Quote 0
                      • N
                        nobbiman @Thomas Braun last edited by nobbiman

                        @thomas-braun
                        Puuhhh, das war jetzt schon mal erfolgreich!
                        Leider will aber der Growatt-Adaper auch nach einem Neustart des ioBrokers immer noch nicht!
                        Auch nach Deinstallieren des Growatt-Adapters/-Instanz, Reboot des Hosts, und Neuinstallation Adapter/Instanz !!

                        growatt.0
	2023-02-02 10:35:14.614	error	Growatt exception: Error: {"result":3}
growatt.0
	2023-02-02 10:35:12.908	info	starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.growatt, node: v16.19.0, js-controller: 4.0.24
                        1 Reply Last reply Reply Quote 0
                        • wendy2702
                          wendy2702 last edited by

                          @nobbiman sagte in Growatt exception: Error: {"result":3}:

                          2.0.0

                          Kannst du das loggen mal auf Debug stellen und den kompletten output vom Adapterstart hier posten.

                          N 1 Reply Last reply Reply Quote 0
                          • N
                            nobbiman @wendy2702 last edited by

                            @wendy2702
                            Da ist leider nicht viel zu sehen!

                            growatt.0
	2023-02-02 11:37:01.734	info	not connected
growatt.0
	2023-02-02 11:37:01.733	warn	Login:{}
growatt.0
	2023-02-02 11:35:01.681	info	not connected
growatt.0
	2023-02-02 11:35:01.680	warn	Login:{}
growatt.0
	2023-02-02 11:33:01.539	info	not connected
growatt.0
	2023-02-02 11:33:01.538	warn	Login:{}
growatt.0
	2023-02-02 11:31:01.477	info	not connected
growatt.0
	2023-02-02 11:31:01.476	warn	Login:{}
growatt.0
	2023-02-02 11:29:01.148	info	not connected
growatt.0
	2023-02-02 11:29:01.147	warn	Login:{}
growatt.0
	2023-02-02 11:27:01.074	info	not connected
growatt.0
	2023-02-02 11:27:01.073	warn	Login:{}
growatt.0
	2023-02-02 11:25:01.007	info	not connecte
                            wendy2702 1 Reply Last reply Reply Quote 0
                            • wendy2702
                              wendy2702 @nobbiman last edited by

                              @nobbiman Steht auch nicht auf Debug.

                              Beispiel:

                              e301d189-450f-4c50-9558-24908ea8791d-grafik.png

                              N 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active last edited by

                                @nobbiman sagte in Growatt exception: Error: {"result":3}:

                                Puuhhh, das war jetzt schon mal erfolgreich!

                                Das heißt die Zeit tickt jetzt richtig?

                                N 1 Reply Last reply Reply Quote 0
                                • N
                                  nobbiman @Thomas Braun last edited by

                                  @thomas-braun
                                  Ja, Danke noch einmal, du hast mich gut durch das Problem geführt - ich merke immer mehr, dass ich tiefer einsteigen müsste.

                                  1 Reply Last reply Reply Quote 0
                                  • N
                                    nobbiman @wendy2702 last edited by

                                    @wendy2702
                                    Sorry, ich war an der falschen Stelle - hier nun sicher korrekt

                                    growatt.0
	2023-02-02 11:41:30.658	debug	Leave growattData :170ms
growatt.0
	2023-02-02 11:41:30.656	info	not connected
growatt.0
	2023-02-02 11:41:30.655	debug	Growatt time for login : 167ms
growatt.0
	2023-02-02 11:41:30.654	debug	Growatt isConnected() : false
growatt.0
	2023-02-02 11:41:30.653	warn	Login:{}
growatt.0
	2023-02-02 11:41:30.495	debug	Enter lifeSignCallback 600000ms
growatt.0
	2023-02-02 11:41:30.494	debug	Growatt login with user and password
growatt.0
	2023-02-02 11:41:30.493	debug	Growatt isConnected() : false
growatt.0
	2023-02-02 11:41:30.490	debug	Growatt new API
growatt.0
	2023-02-02 11:41:30.488	debug	Enter lifeSignCallback 600000ms
growatt.0
	2023-02-02 11:41:30.487	debug	Enter growattData, Param: sessionHold:true
growatt.0
	2023-02-02 11:41:30.416	info	starting. Version 2.0.0 in /opt/iobroker/node_modules/iobroker.growatt, node: v16.19.0, js-controller: 4.0.24
growatt.0
	2023-02-02 11:41:29.995	debug	Plugin sentry Initialize Plugin (enabled=true)
growatt.0
	2023-02-02 11:41:29.893	debug	States connected to redis: 127.0.0.1:9000
growatt.0
	2023-02-02 11:41:29.801	debug	States create User PubSub Client
growatt.0
	2023-02-02 11:41:29.799	debug	States create System PubSub Client
growatt.0
	2023-02-02 11:41:29.774	debug	Redis States: Use Redis connection: 127.0.0.1:9000
growatt.0
	2023-02-02 11:41:29.725	debug	Objects connected to redis: 127.0.0.1:9001
growatt.0
	2023-02-02 11:41:29.717	debug	Objects client initialize lua scripts
growatt.0
	2023-02-02 11:41:29.633	debug	Objects create User PubSub Client
growatt.0
	2023-02-02 11:41:29.631	debug	Objects create System PubSub Client
growatt.0
	2023-02-02 11:41:29.628	debug	Objects client ready ... initialize now
growatt.0
	2023-02-02 11:41:29.568	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
growatt.0
	2023-02-02 11:41:24.945	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
growatt.0
	2023-02-02 11:41:24.944	info	terminating
growatt.0
	2023-02-02 11:41:24.941	info	Got terminate signal TERMINATE_YOURSELF
growatt.0
	2023-02-02 11:41:02.146	info	not connected
growatt.0
	2023-02-02 11:41:02.145	warn	Login:{}
                                    wendy2702 1 Reply Last reply Reply Quote 0
                                    • wendy2702
                                      wendy2702 @nobbiman last edited by

                                      @nobbiman sagte in Growatt exception: Error: {"result":3}:

                                      not connected

                                      Der verbindet sich nicht mit dem China Server.

                                      Was für eine Adresse steht denn in der Config?

                                      N 1 Reply Last reply Reply Quote 1
                                      • N
                                        nobbiman @wendy2702 last edited by

                                        @wendy2702

                                        https://server.growatt.com
                                        wendy2702 Thomas Braun 2 Replies Last reply Reply Quote 0
                                        • wendy2702
                                          wendy2702 @nobbiman last edited by

                                          @nobbiman und die Seite ist von iobroker erreichbar und du bist dort registriert und kannst dich anmelden?

                                          N 1 Reply Last reply Reply Quote 0
                                          • N
                                            nobbiman @wendy2702 last edited by

                                            @wendy2702 said in Growatt exception: Error: {"result":3}:

                                            iobroker erreichbar und du bist dort registriert

                                            Was heißt "von iobroker erreichbar"?
                                            Bei Growatt bin ich natürlich registriert und empfange meine Infos auch über meinen Browser. Bis von ein paar Tagen war das Auslesen der Daten und die Verbindung auch gar kein Problem. Frag mich aber bitte nicht, ob ich etwas geändert hatte - ich meine nicht!
                                            Growatt-Instanz.JPG

                                            wendy2702 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            961
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            3
                                            81
                                            3802
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo