Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter iobroker.uv-protect 0.3.x

    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

    Test Adapter iobroker.uv-protect 0.3.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • FredF
      FredF Most Active Forum Testing @JohGre last edited by

      @johgre
      Und wo ist ein Fehler (error)?
      Die Instanz steht auf Log-Stufe debug - da kommen dann viele Meldungen. Besser umstellen auf info

      JohGre 1 Reply Last reply Reply Quote 0
      • JohGre
        JohGre @FredF last edited by

        @fredf vorletzte Zeile, im ioBroker log zwar ein warn, aber als response ein HTML Error und somit keine Daten

        FredF 1 Reply Last reply Reply Quote 0
        • FredF
          FredF Most Active Forum Testing @JohGre last edited by

          @johgre Code 503 sagt laut suche, dass der Server nicht antwortet. API key eingetragen?

          1 Reply Last reply Reply Quote 0
          • JohGre
            JohGre last edited by

            @fredf Ja, API Key ist eingetragen (und auch der richtige) und beim starten werden auch einmalig Daten geholt.

            2022-03-05 14:08:22.246 - debug: uv-protect.0 (207612) Redis Objects: Use Redis connection: 10.0.0.227:9001
2022-03-05 14:08:22.272 - debug: uv-protect.0 (207612) Objects client ready ... initialize now
2022-03-05 14:08:22.275 - debug: uv-protect.0 (207612) Objects create System PubSub Client
2022-03-05 14:08:22.275 - debug: uv-protect.0 (207612) Objects create User PubSub Client
2022-03-05 14:08:22.312 - debug: uv-protect.0 (207612) Objects client initialize lua scripts
2022-03-05 14:08:22.316 - debug: uv-protect.0 (207612) Objects connected to redis: 10.0.0.227:9001
2022-03-05 14:08:22.341 - debug: uv-protect.0 (207612) Redis States: Use Redis connection: 10.0.0.227:9000
2022-03-05 14:08:22.356 - debug: uv-protect.0 (207612) States create System PubSub Client
2022-03-05 14:08:22.357 - debug: uv-protect.0 (207612) States create User PubSub Client
2022-03-05 14:08:22.379 - debug: uv-protect.0 (207612) States connected to redis: 10.0.0.227:9000
2022-03-05 14:08:23.036 - info: uv-protect.0 (207612) starting. Version 0.3.5 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v14.19.0, js-controller: 4.0.18
2022-03-05 14:08:23.072 - debug: uv-protect.0 (207612) System language: en
2022-03-05 14:08:23.072 - debug: uv-protect.0 (207612) System longitude: 13. System latitude: 48.
2022-03-05 14:08:23.082 - debug: uv-protect.0 (207612) API Request started ...
2022-03-05 14:08:23.592 - debug: uv-protect.0 (207612) API Request successfully completed
2022-03-05 14:08:23.592 - debug: uv-protect.0 (207612) {"result":{"uv":1.8666,"uv_time":"2022-03-05T13:08:23.511Z","uv_max":2.597,"uv_max_time":"2022-03-05T11:17:22.820Z","ozone":346.6,"ozone_time":"2022-03-05T12:04:38.489Z","safe_exposure_time":{"st1":89,"st2":107,"st3":143,"st4":179,"st5":286,"st6":536},"sun_info":{"sun_times":{"solarNoon":"2022-03-05T11:17:22.820Z","nadir":"2022-03-04T23:17:22.820Z","sunrise":"2022-03-05T05:39:49.203Z","sunset":"2022-03-05T16:54:56.436Z","sunriseEnd":"2022-03-05T05:43:03.240Z","sunsetStart":"2022-03-05T16:51:42.399Z","dawn":"2022-03-05T05:08:40.125Z","dusk":"2022-03-05T17:26:05.514Z","nauticalDawn":"2022-03-05T04:32:38.608Z","nauticalDusk":"2022-03-05T18:02:07.031Z","nightEnd":"2022-03-05T03:56:17.360Z","night":"2022-03-05T18:38:28.279Z","goldenHourEnd":"2022-03-05T06:21:47.708Z","goldenHour":"2022-03-05T16:12:57.931Z"},"sun_position":{"azimuth":0.571989127405678,"altitude":0.5310458359058243}}}}
2022-03-05 14:08:23.837 - debug: uv-protect.0 (207612) API Request done
2022-03-05 14:08:29.845 - info: uv-protect.0 (207612) Terminated (NO_ERROR): Without reason
2022-03-05 15:00:00.413 - debug: uv-protect.0 (208702) Redis Objects: Use Redis connection: 10.0.0.227:9001
2022-03-05 15:00:00.444 - debug: uv-protect.0 (208702) Objects client ready ... initialize now
2022-03-05 15:00:00.446 - debug: uv-protect.0 (208702) Objects create System PubSub Client
2022-03-05 15:00:00.447 - debug: uv-protect.0 (208702) Objects create User PubSub Client
2022-03-05 15:00:00.490 - debug: uv-protect.0 (208702) Objects client initialize lua scripts
2022-03-05 15:00:00.495 - debug: uv-protect.0 (208702) Objects connected to redis: 10.0.0.227:9001
2022-03-05 15:00:00.528 - debug: uv-protect.0 (208702) Redis States: Use Redis connection: 10.0.0.227:9000
2022-03-05 15:00:00.551 - debug: uv-protect.0 (208702) States create System PubSub Client
2022-03-05 15:00:00.552 - debug: uv-protect.0 (208702) States create User PubSub Client
2022-03-05 15:00:00.594 - debug: uv-protect.0 (208702) States connected to redis: 10.0.0.227:9000
2022-03-05 15:00:01.506 - info: uv-protect.0 (208702) starting. Version 0.3.5 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v14.19.0, js-controller: 4.0.18
2022-03-05 15:00:01.563 - debug: uv-protect.0 (208702) System language: en
2022-03-05 15:00:01.563 - debug: uv-protect.0 (208702) System longitude: 13. System latitude: 48.
2022-03-05 15:00:01.572 - debug: uv-protect.0 (208702) API Request started ...
2022-03-05 15:00:32.016 - warn: uv-protect.0 (208702) Request error: Error: Request failed with status code 503
2022-03-05 15:00:38.025 - info: uv-protect.0 (208702) Terminated (NO_ERROR): Without reason
            1 Reply Last reply Reply Quote 0
            • P
              ps1304 @simatec last edited by ps1304

              @simatec erstmal danke für den Adapter - habe ich neu installiert auf iobroker - bekomme für alle Datenpunkte Fehlermeldungen ala:

              Object uv-protect.0.sun_info.sun_position.altitude is invalid: Default value has to be type "number" but received type "string"
              System iobroker: 4.0.19node.js 16.14 / NPM 8.3.1 auf proxmox vm installiert

              Ist der Fehler bekannt?

              Komplettes Log zum Adapterstart:

              2022-03-13 15:42:50.792  - info: host.iobroker-master instance system.adapter.uv-protect.0 started with pid 50746
2022-03-13 16:42:52.812  - warn: uv-protect.0 (50746) Object uv-protect.0.uv is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.815  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.835  - warn: uv-protect.0 (50746) Object uv-protect.0.uv_max is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.835  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.848  - warn: uv-protect.0 (50746) Object uv-protect.0.ozone is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.849  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.862  - warn: uv-protect.0 (50746) Object uv-protect.0.safe_exposure_time.st1 is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.862  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.872  - warn: uv-protect.0 (50746) Object uv-protect.0.safe_exposure_time.st2 is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.873  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.883  - warn: uv-protect.0 (50746) Object uv-protect.0.safe_exposure_time.st3 is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.883  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.931  - warn: uv-protect.0 (50746) Object uv-protect.0.safe_exposure_time.st4 is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.932  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.940  - warn: uv-protect.0 (50746) Object uv-protect.0.safe_exposure_time.st5 is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.940  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:52.948  - warn: uv-protect.0 (50746) Object uv-protect.0.safe_exposure_time.st6 is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:52.948  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:53.036  - warn: uv-protect.0 (50746) Object uv-protect.0.sun_info.sun_position.azimuth is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:53.036  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:53.043  - warn: uv-protect.0 (50746) Object uv-protect.0.sun_info.sun_position.altitude is invalid: Default value has to be type "number" but received type "string"
2022-03-13 16:42:53.044  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:53.102  - warn: uv-protect.0 (50746) Object uv-protect.0.uv_alert is invalid: Default value has to be type "boolean" but received type "string"
2022-03-13 16:42:53.102  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:53.110  - warn: uv-protect.0 (50746) Object uv-protect.0.uv_warn is invalid: Default value has to be type "boolean" but received type "string"
2022-03-13 16:42:53.110  - warn: uv-protect.0 (50746) This object will not be created in future versions. Please report this to the developer.
2022-03-13 16:42:53.119  - info: uv-protect.0 (50746) starting. Version 0.3.4 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v16.14.0, js-controller: 4.0.19```
              simatec 1 Reply Last reply Reply Quote 0
              • simatec
                simatec Developer Most Active @ps1304 last edited by

                @ps1304
                Das sind nur Warnungen… Fixe ich in der nächsten Version

                P Z 2 Replies Last reply Reply Quote 0
                • P
                  ps1304 @simatec last edited by

                  @simatec danke dir für die schnelle antwort und deinen adapter

                  1 Reply Last reply Reply Quote 0
                  • Z
                    zolpetol @simatec last edited by zolpetol

                    @simatec
                    Bei mir leider auch nur aktuelle Daten direkt nach dem Starten des Adapter, danach folgende Meldungen und keine Aktualisierung mehr:

                    2022-03-26 15_21_10-logs - iobroker.jpg

                    APi-Key ist eingetragen

                    16:43h: zur Zeit funktioniert die Aktualisierung
                    19:19h. wieder vorbei Code 403 oder auch Code 500

                    simatec 2 Replies Last reply Reply Quote 0
                    • simatec
                      simatec Developer Most Active @zolpetol last edited by

                      @zolpetol Du hast nur eine gewisse Anzahl an API Abrufen innerhalb von 24 Stunden mit der freien Version.

                      Du solltest dementsprechend den Zeitintervall nicht so klein setzen

                      1 Reply Last reply Reply Quote 0
                      • simatec
                        simatec Developer Most Active @zolpetol last edited by

                        @zolpetol Zitat auf der Page von OpenUV:

                        Need more than 50 daily requests? Check our Extended Plan for just $15 USD/month. Payments and billing processed by Stripe.

                        Z 1 Reply Last reply Reply Quote 0
                        • Z
                          zolpetol @simatec last edited by

                          @simatec

                          Danke für die Info! Das Zeitintervall wurde gemäß dieser Info eingestellt:

                          2022-03-28 16_19_42-Test Adapter iobroker.uv-protect 0.3.x.jpg

                          simatec 1 Reply Last reply Reply Quote 0
                          • simatec
                            simatec Developer Most Active @zolpetol last edited by

                            @zolpetol Dann sollte es nun funktionieren ...

                            1 Reply Last reply Reply Quote 0
                            • JohGre
                              JohGre last edited by

                              @zolpetol sagte in Test Adapter iobroker.uv-protect 0.3.x:

                              @simatec
                              Bei mir leider auch nur aktuelle Daten direkt nach dem Starten des Adapter, danach folgende Meldungen und keine Aktualisierung mehr:

                              2022-03-26 15_21_10-logs - iobroker.jpg

                              APi-Key ist eingetragen

                              16:43h: zur Zeit funktioniert die Aktualisierung
                              19:19h. wieder vorbei Code 403 oder auch Code 500

                              Hast du das Problem schon lösen können? Auch bei mir immer wieder ein 403 trotz neuem Key. Werd den Adapter wohl wieder deaktivieren

                              simatec 1 Reply Last reply Reply Quote 0
                              • simatec
                                simatec Developer Most Active @JohGre last edited by

                                @johgre Wie oft holst du die Daten?
                                Mit der kostenlosen Version dieser API kannst du maximal 50 Anfragen pro Tag starten.

                                Wenn du mehr abfragen hast, bekommst du diesen fehler.

                                Zitat von openuv.io:
                                Need more than 50 daily requests? Check our Extended Plan for just $15 USD/month.

                                JohGre 1 Reply Last reply Reply Quote 0
                                • JohGre
                                  JohGre @simatec last edited by

                                  @simatec Default-Einstellung des Adapters

                                  simatec 1 Reply Last reply Reply Quote 0
                                  • simatec
                                    simatec Developer Most Active @JohGre last edited by

                                    @johgre Dann ist die API sicher gerade nicht erreichbar ... Was aber nicht am Adapter liegt.
                                    Es ist ja auch nur eine reine Warnung und nix böses

                                    1 Reply Last reply Reply Quote 0
                                    • Albert K
                                      Albert K @simatec last edited by

                                      @simatec

                                      Vielen Dank für den Adapter!!! 👍 👍 👍

                                      Hatte mit dem open-uv Adapter mehr und mehr Probleme (ständige Abstürze). Und meine Rollladen Steuerung zur Beschattung basiert auf dem berechneten lokalen UVI Wert.

                                      Jetzt klappt das wieder Super!

                                      viele Grüße

                                      1 Reply Last reply Reply Quote 0
                                      • Jörg Knechten
                                        Jörg Knechten last edited by

                                        Hi der letzte Eintrag ist schon etwas her, aber ich versuche es einfach mal.
                                        Erstmal vielen Dank für die Arbeit, die in dem Adapter steckt. Für uns extrem hilfreich. da meine Frau Lupus hat und somit Sonne bzw. hohe UV-Strahlung meiden soll.

                                        Leider habe ich ein Problem. Die Werte aktualisieren sich bei mir nur, wenn ich den Adapter neu starte. Aktualisierung, wie empfohlen, alle 60 Min. Das Protokoll spuckt folgendes aus.

                                        host.vmiob
2022-08-13 07:00:12.503	info	instance system.adapter.uv-protect.0 terminated with code 0 (NO_ERROR)

uv-protect.0
2022-08-13 07:00:11.988	info	Terminated (NO_ERROR): Without reason

uv-protect.0
2022-08-13 07:00:05.984	warn	Request error: AxiosError: timeout of 5000ms exceeded

uv-protect.0
2022-08-13 07:00:00.909	info	starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v18.6.0, js-controller: 4.0.23
host.vmiob
2022-08-13 07:00:00.164	info	instance system.adapter.uv-protect.0 started with pid 21308
host.vmiob
2022-08-13 06:00:12.351	info	instance system.adapter.uv-protect.0 terminated with code 0 (NO_ERROR)

uv-protect.0
2022-08-13 06:00:11.836	info	Terminated (NO_ERROR): Without reason

uv-protect.0
2022-08-13 06:00:05.832	warn	Request error: AxiosError: timeout of 5000ms exceeded

uv-protect.0
2022-08-13 06:00:00.758	info	starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v18.6.0, js-controller: 4.0.23
host.vmiob
2022-08-13 06:00:00.019	info	instance system.adapter.uv-protect.0 started with pid 21185
host.vmiob
2022-08-13 05:00:12.372	info	instance system.adapter.uv-protect.0 terminated with code 0 (NO_ERROR)

uv-protect.0
2022-08-13 05:00:11.857	info	Terminated (NO_ERROR): Without reason

uv-protect.0
2022-08-13 05:00:05.853	warn	Request error: AxiosError: timeout of 5000ms exceeded

uv-protect.0
2022-08-13 05:00:00.780	info	starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v18.6.0, js-controller: 4.0.23
host.vmiob
2022-08-13 05:00:00.019	info	instance system.adapter.uv-protect.0 started with pid 21159

mercedesme.0
2022-08-13 04:58:46.419	info	Lost WebSocket connection. Reconnect WebSocket
host.vmiob
2022-08-13 04:00:12.354	info	instance system.adapter.uv-protect.0 terminated with code 0 (NO_ERROR)

uv-protect.0
2022-08-13 04:00:11.840	info	Terminated (NO_ERROR): Without reason

uv-protect.0
2022-08-13 04:00:05.836	warn	Request error: AxiosError: timeout of 5000ms exceeded

uv-protect.0
2022-08-13 04:00:00.762	info	starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v18.6.0, js-controller: 4.0.23
host.vmiob
2022-08-13 04:00:00.019	info	instance system.adapter.uv-protect.0 started with pid 21131
host.vmiob
2022-08-13 03:00:12.382	info	instance system.adapter.uv-protect.0 terminated with code 0 (NO_ERROR)

uv-protect.0
2022-08-13 03:00:11.867	info	Terminated (NO_ERROR): Without reason

uv-protect.0
2022-08-13 03:00:05.862	warn	Request error: AxiosError: timeout of 5000ms exceeded

uv-protect.0
2022-08-13 03:00:00.786	info	starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v18.6.0, js-controller: 4.0.23
host.vmiob
2022-08-13 03:00:00.018	info	instance system.adapter.uv-protect.0 started with pid 21090
host.vmiob
2022-08-13 02:00:12.353	info	instance system.adapter.uv-protect.0 terminated with code 0 (NO_ERROR)

uv-protect.0
2022-08-13 02:00:11.840	info	Terminated (NO_ERROR): Without reason

uv-protect.0
2022-08-13 02:00:05.835	warn	Request error: AxiosError: timeout of 5000ms exceeded

uv-protect.0
2022-08-13 02:00:00.761	info	starting. Version 0.3.6 in /opt/iobroker/node_modules/iobroker.uv-protect, node: v18.6.0, js-controller: 4.0.23
host.vmiob
2022-08-13 02:00:00.021	info	instance system.adapter.uv-protect.0 started with pid 21051

                                        Das Problem scheint der Timout zu sein. Bin allerdings Newb bzgl. ioBroker.

                                        Vielen Dank im Voraus!

                                        simatec 1 Reply Last reply Reply Quote 0
                                        • simatec
                                          simatec Developer Most Active @Jörg Knechten last edited by

                                          @jörg-knechten Hast du dir ein API-Key geholt und diesen im Adapter eingetragen?
                                          Geo-Daten werden vom System geholt ... dort müsst sie aber richtig eingetragen sein.

                                          Auch auf die Nachkommastellen achten, da die API von OpenUV diese so benötigt

                                          Beispiel:
                                          Längengrad: 13.376935
                                          Breitgrad: 52.516181

                                          Jörg Knechten 2 Replies Last reply Reply Quote 0
                                          • Jörg Knechten
                                            Jörg Knechten @simatec last edited by

                                            @simatec
                                            Sorry war im Urlaub.
                                            Den API habe ich geholt. Habe jetzt mal die GPS Koordinaten von Hand eingetragen. Mal schauen was passiert.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            706
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            13
                                            41
                                            2557
                                            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