Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter Admin 5.0.x: Alpha der neuen UI

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    Test Adapter Admin 5.0.x: Alpha der neuen UI

    This topic has been deleted. Only users with topic management privileges can see it.
    • Homoran
      Homoran Global Moderator Administrators @apollon77 last edited by

      @apollon77 sagte in Test Adapter Admin 5.0.x: Alpha der neuen UI:

      Github issue bitte!!

      Done!
      https://github.com/ioBroker/ioBroker.admin/issues/794

      Homoran created this issue in ioBroker/ioBroker.admin

      closed host name is missing in instances overview #794

      1 Reply Last reply Reply Quote 0
      • da_Woody
        da_Woody @apollon77 last edited by da_Woody

        @apollon77 mir müllts in den letzten tagen so das log zu mit warnings, daß mir der ganze proxmox rechner 3x abgekackt ist.
        mal so ein kleiner ausschnitt:

        radar2.0	2021-05-01 21:11:12.481	warn	Read-only state "radar2.0.Google_Ping._nHere" has been written without ack-flag with value "87"
        radar2.0	2021-05-01 21:11:12.429	warn	Read-only state "radar2.0.Syno_FTP._lastHere" has been written without ack-flag with value "2021-05-01@21:11:12"
        radar2.0	2021-05-01 21:11:12.375	warn	Read-only state "radar2.0.Syno_Privat._lastHere" has been written without ack-flag with value "2021-05-01@21:11:12"
        radar2.0	2021-05-01 21:11:12.323	warn	Read-only state "radar2.0.Fronius._lastHere" has been written without ack-flag with value "2021-05-01@21:11:12"
        radar2.0	2021-05-01 21:11:12.272	warn	Read-only state "radar2.0.Luci._lastHere" has been written without ack-flag with value "2021-05-01@21:11:12"
        radar2.0	2021-05-01 21:11:12.224	warn	Read-only state "radar2.0.AP_HQ._lastHere" has been written without ack-flag with value "2021-05-01@21:11:12"
        mihome-vacuum.0	2021-05-01 21:11:11.322	warn	State value to set for "mihome-vacuum.0.info.water_box" has wrong type "boolean" but has to be "string"
        wallpanel.0	2021-05-01 21:11:08.997	warn	State value to set for "wallpanel.0.samsung.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:11:08.955	warn	State value to set for "wallpanel.0.tab_white.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:11:08.852	warn	State value to set for "wallpanel.0.tab_black.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        	2021-05-01 21:11:07.040	warn	radar2.0Read-only state "radar2.0.ioBroker_Master._lastHere" has been written without ack-flag with value "2021-05-01@21:11:07"
        	2021-05-01 21:11:06.996	warn	radar2.0Read-only state "radar2.0.Motioneye._lastHere" has been written without ack-flag with value "2021-05-01@21:11:06"
        	2021-05-01 21:11:06.950	warn	radar2.0Read-only state "radar2.0.Grafana._lastHere" has been written without ack-flag with value "2021-05-01@21:11:06"
        	2021-05-01 21:11:06.888	warn	radar2.0Read-only state "radar2.0.pi_Hole._lastHere" has been written without ack-flag with value "2021-05-01@21:11:06"
        	2021-05-01 21:11:06.840	warn	radar2.0Read-only state "radar2.0.Proxmox._lastHere" has been written without ack-flag with value "2021-05-01@21:11:06"
        	2021-05-01 21:11:06.797	warn	radar2.0Read-only state "radar2.0.Router._lastHere" has been written without ack-flag with value "2021-05-01@21:11:06"
        	2021-05-01 21:11:06.789	warn	radar2.0Read-only state "radar2.0.Google_Ping._lastHere" has been written without ack-flag with value "2021-05-01@21:11:06"
        synology.1	2021-05-01 21:11:04.221	info	Connecting to Synology 192.168.0.2:4001
        synology.0	2021-05-01 21:11:04.204	info	Connecting to Synology 192.168.0.3:5001
        javascript.0	2021-05-01 21:10:55.304	warn	Read-only state "0_userdata.0.Lüftung.Bad/WC.AbsoluteFeuchte" has been written without ack-flag with value "10.99"
        mihome-vacuum.0	2021-05-01 21:10:51.015	warn	State value to set for "mihome-vacuum.0.info.water_box" has wrong type "boolean" but has to be "string"
        wallpanel.0	2021-05-01 21:10:50.154	warn	State value to set for "wallpanel.0.samsung.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:10:50.106	warn	State value to set for "wallpanel.0.tab_white.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:10:49.915	warn	State value to set for "wallpanel.0.tab_black.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        meldungsliste.1	2021-05-01 21:10:48.499	warn	State value to set for "meldungsliste.1.Meldungen" has wrong type "undefined" but has to be "string"
        javascript.0	2021-05-01 21:10:45.187	warn	Read-only state "0_userdata.0.Lüftung.Bad/WC.AbsoluteFeuchte" has been written without ack-flag with value "11.03"
        	2021-05-01 21:10:42.988	warn	radar2.0Read-only state "radar2.0.Syno_FTP._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.941	warn	radar2.0Read-only state "radar2.0.Syno_Privat._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.893	warn	radar2.0Read-only state "radar2.0.Fronius._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.849	warn	radar2.0Read-only state "radar2.0.Luci._nHere" has been written without ack-flag with value "45"
        	2021-05-01 21:10:42.802	warn	radar2.0Read-only state "radar2.0.AP_HQ._nHere" has been written without ack-flag with value "45"
        	2021-05-01 21:10:42.756	warn	radar2.0Read-only state "radar2.0.ioBroker_Master._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.712	warn	radar2.0Read-only state "radar2.0.Motioneye._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.668	warn	radar2.0Read-only state "radar2.0.Grafana._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.621	warn	radar2.0Read-only state "radar2.0.pi_Hole._nHere" has been written without ack-flag with value "86"
        shelly.0	2021-05-01 21:10:42.610	warn	State value to set for "shelly.0.SHDM-1#F34432#1.temperatureF" has value "126.49" greater than max "100"
        	2021-05-01 21:10:42.561	warn	radar2.0Read-only state "radar2.0.Proxmox._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.509	warn	radar2.0Read-only state "radar2.0.Router._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.465	warn	radar2.0Read-only state "radar2.0.Google_Ping._nHere" has been written without ack-flag with value "86"
        	2021-05-01 21:10:42.416	warn	radar2.0Read-only state "radar2.0.Syno_FTP._lastHere" has been written without ack-flag with value "2021-05-01@21:10:42"
        	2021-05-01 21:10:42.371	warn	radar2.0Read-only state "radar2.0.Syno_Privat._lastHere" has been written without ack-flag with value "2021-05-01@21:10:42"
        	2021-05-01 21:10:42.320	warn	radar2.0Read-only state "radar2.0.Fronius._lastHere" has been written without ack-flag with value "2021-05-01@21:10:42"
        	2021-05-01 21:10:42.273	warn	radar2.0Read-only state "radar2.0.Luci._lastHere" has been written without ack-flag with value "2021-05-01@21:10:42"
        	2021-05-01 21:10:42.224	warn	radar2.0Read-only state "radar2.0.AP_HQ._lastHere" has been written without ack-flag with value "2021-05-01@21:10:42"
        proxmox.0	2021-05-01 21:10:37.967	warn	State value to set for "proxmox.0.qemu_Nagios.pid" has wrong type "string" but has to be "number"
        proxmox.0	2021-05-01 21:10:37.880	warn	State value to set for "proxmox.0.qemu_ioBroker.pid" has wrong type "string" but has to be "number"
        proxmox.0	2021-05-01 21:10:37.872	warn	State value to set for "proxmox.0.qemu_PiHole.pid" has wrong type "string" but has to be "number"
        proxmox.0	2021-05-01 21:10:37.870	warn	State value to set for "proxmox.0.qemu_Influx-Grafana-Tasmo.pid" has wrong type "string" but has to be "number"
        proxmox.0	2021-05-01 21:10:37.870	warn	State value to set for "proxmox.0.qemu_MotionEye.pid" has wrong type "string" but has to be "number"
        proxmox.0	2021-05-01 21:10:37.772	warn	State value to set for "proxmox.0.node_Homeserver.status" has wrong type "string" but has to be "boolean"
        	2021-05-01 21:10:37.095	warn	radar2.0Read-only state "radar2.0.ioBroker_Master._lastHere" has been written without ack-flag with value "2021-05-01@21:10:37"
        	2021-05-01 21:10:37.052	warn	radar2.0Read-only state "radar2.0.Motioneye._lastHere" has been written without ack-flag with value "2021-05-01@21:10:37"
        	2021-05-01 21:10:37.010	warn	radar2.0Read-only state "radar2.0.Grafana._lastHere" has been written without ack-flag with value "2021-05-01@21:10:37"
        	2021-05-01 21:10:36.961	warn	radar2.0Read-only state "radar2.0.pi_Hole._lastHere" has been written without ack-flag with value "2021-05-01@21:10:36"
        	2021-05-01 21:10:36.904	warn	radar2.0Read-only state "radar2.0.Proxmox._lastHere" has been written without ack-flag with value "2021-05-01@21:10:36"
        	2021-05-01 21:10:36.855	warn	radar2.0Read-only state "radar2.0.Router._lastHere" has been written without ack-flag with value "2021-05-01@21:10:36"
        	2021-05-01 21:10:36.793	warn	radar2.0Read-only state "radar2.0.Google_Ping._lastHere" has been written without ack-flag with value "2021-05-01@21:10:36"
        wallpanel.0	2021-05-01 21:10:34.180	warn	State value to set for "wallpanel.0.samsung.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:10:34.104	warn	State value to set for "wallpanel.0.tab_white.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:10:33.935	warn	State value to set for "wallpanel.0.tab_black.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        mihome-vacuum.0	2021-05-01 21:10:30.873	warn	State value to set for "mihome-vacuum.0.info.water_box" has wrong type "boolean" but has to be "string"
        shelly.0	2021-05-01 21:10:27.579	warn	State value to set for "shelly.0.SHDM-1#F34432#1.temperatureF" has value "126.67" greater than max "100"
        wallpanel.0	2021-05-01 21:10:18.208	warn	State value to set for "wallpanel.0.samsung.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:10:18.149	warn	State value to set for "wallpanel.0.tab_white.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        wallpanel.0	2021-05-01 21:10:17.976	warn	State value to set for "wallpanel.0.tab_black.lastInfoUpdate" has wrong type "number" but has to be "boolean"
        javascript.0	2021-05-01 21:10:15.157	warn	Read-only state "0_userdata.0.Lüftung.Bad/WC.AbsoluteFeuchte" has been written without ack-flag with value "11.05"
        	2021-05-01 21:10:13.221	warn	radar2.0Read-only state "radar2.0.Syno_FTP._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:13.173	warn	radar2.0Read-only state "radar2.0.Syno_Privat._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:13.068	warn	radar2.0Read-only state "radar2.0.Fronius._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:13.026	warn	radar2.0Read-only state "radar2.0.Luci._nHere" has been written without ack-flag with value "44"
        	2021-05-01 21:10:12.982	warn	radar2.0Read-only state "radar2.0.AP_HQ._nHere" has been written without ack-flag with value "44"
        	2021-05-01 21:10:12.937	warn	radar2.0Read-only state "radar2.0.ioBroker_Master._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:12.892	warn	radar2.0Read-only state "radar2.0.Motioneye._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:12.849	warn	radar2.0Read-only state "radar2.0.Grafana._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:12.804	warn	radar2.0Read-only state "radar2.0.pi_Hole._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:12.760	warn	radar2.0Read-only state "radar2.0.Proxmox._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:12.717	warn	radar2.0Read-only state "radar2.0.Router._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:12.669	warn	radar2.0Read-only state "radar2.0.Google_Ping._nHere" has been written without ack-flag with value "85"
        	2021-05-01 21:10:12.615	warn	radar2.0Read-only state "radar2.0.Syno_FTP._lastHere" has been written without ack-flag with value "2021-05-01@21:10:12"
        	2021-05-01 21:10:12.550	warn	radar2.0Read-only state "radar2.0.Syno_Privat._lastHere" has been written without ack-flag with value "2021-05-01@21:10:12"
        	2021-05-01 21:10:12.506	warn	radar2.0Read-only state "radar2.0.Fronius._lastHere" has been written without ack-flag with value "2021-05-01@21:10:12"
        	2021-05-01 21:10:12.457	warn	radar2.0Read-only state "radar2.0.Luci._lastHere" has been written without ack-flag with value "2021-05-01@21:10:12"
        shelly.0	2021-05-01 21:10:12.413	warn	State value to set for "shelly.0.SHDM-1#F34432#1.temperatureF" has value "126.49" greater than max "100"
        

        das hatte ich noch nie...

        afuerhoff apollon77 2 Replies Last reply Reply Quote 0
        • afuerhoff
          afuerhoff Developer @da_Woody last edited by afuerhoff

          @da_woody
          Aufgrund es neuen js-controllers 3.3.x kommen diese Warnungen. Muss in den Adaptern angepasst werden.

          Am besten die betroffenen Adapter so lange auf Log Stufe Error setzen

          da_Woody 1 Reply Last reply Reply Quote 1
          • da_Woody
            da_Woody @afuerhoff last edited by

            @afuerhoff ah, ok, den hab ich heute getutet, erklärt aber nicht, warum mir in 4 tagen der rechner 3x komplett abkackt. nicht der iobroker, sondern alle VMs und proxmox auch.

            apollon77 afuerhoff Chaot 3 Replies Last reply Reply Quote 0
            • apollon77
              apollon77 @da_Woody last edited by

              @da_woody In dem Thread sollte man das nicht diskutieren, aber in nem anderen Thread oder Discord vllt ne idee mal gemeinsam das anzuschauen

              1 Reply Last reply Reply Quote 1
              • afuerhoff
                afuerhoff Developer @da_Woody last edited by

                @da_woody sagte in Test Adapter Admin 5.0.x: Alpha der neuen UI:

                und proxmox auch.

                Wie groß ist denn das Log-File.

                da_Woody 1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @da_Woody last edited by

                  @da_woody Ja aber VOR dem "Error setzen" wie von @afuerhoff vorgeschlagen bitte UNBEDINGT bei den Adatern Issues anlegen wenn noch keine da sind!

                  1 Reply Last reply Reply Quote 0
                  • da_Woody
                    da_Woody @afuerhoff last edited by

                    @afuerhoff welches meinst du? proxmox, oder iob protokoll? iob 8,4MB im mom.

                    afuerhoff 1 Reply Last reply Reply Quote 0
                    • afuerhoff
                      afuerhoff Developer @da_Woody last edited by afuerhoff

                      @da_woody
                      iob protokoll. Aufgrund der vielen Log Einträge läuft da einiges auf. Das könnte zu einem Speicher Problem werden.
                      -> Logvel der betroffenen Adapter mal auf Error setzen und beobachten.

                      da_Woody 1 Reply Last reply Reply Quote 0
                      • da_Woody
                        da_Woody @afuerhoff last edited by da_Woody

                        @afuerhoff jep, schon begriffen, da hab ich einiges zu tun... 😉
                        hehe, sogar der proxmox adapter zickt...

                        proxmox.0	2021-05-01 21:23:37.944	warn	State value to set for "proxmox.0.qemu_ioBroker.pid" has wrong type "string" but has to be "number"
                        proxmox.0	2021-05-01 21:23:37.943	warn	State value to set for "proxmox.0.qemu_PiHole.pid" has wrong type "string" but has to be "number"
                        proxmox.0	2021-05-01 21:23:37.864	warn	State value to set for "proxmox.0.qemu_MotionEye.pid" has wrong type "string" but has to be "number"
                        proxmox.0	2021-05-01 21:23:37.862	warn	State value to set for "proxmox.0.qemu_Nagios.pid" has wrong type "string" but has to be "number"
                        proxmox.0	2021-05-01 21:23:37.858	warn	State value to set for "proxmox.0.qemu_Influx-Grafana-Tasmo.pid" has wrong type "string" but has to be "number"
                        proxmox.0	2021-05-01 21:23:37.769	warn	State value to set for "proxmox.0.node_Homeserver.status" has wrong type "string" but has to be "boolean"
                        
                        apollon77 1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 @da_Woody last edited by

                          @da_woody Langsam ... "zicken" tut der nicht. der Loggt ein paar DInge wo der Dev was tun muss. Das alles hat KEINERLEI AUSWIRKUNG AUF DIE FUNKTIONALITÄT!

                          1 Reply Last reply Reply Quote 0
                          • Chaot
                            Chaot @da_Woody last edited by

                            @da_woody Lüfter zu?
                            Ich habe wegen den Meldungen im Log eine höhere Prozessorlast im gesamten Proxmox System. Das ging von normalerweise etwa 40% auf fast 60% hoch. Der NUC wurde entsprechend deutlich wärmer und der eigentlich unhörbare Lüfter ist deutlich hörbar gelaufen.

                            da_Woody 1 Reply Last reply Reply Quote 0
                            • da_Woody
                              da_Woody @Chaot last edited by

                              @chaot hmpf, musste gerade wieder hard resetten...
                              559bdf9f-1b58-47e9-85d7-5cdcac4a2d2e-grafik.png
                              sieht eigentlich nicht wild aus. werd die kiste morgen mal ordentlich durchputzen. so sauber gehts in einer werkstatt ja auch nicht zu, auch wenn die kiste im büro steht. wenn ich dann schon dabei bin, zerlegen, neue leitpaste und den ganzen sermon...
                              @apollon77 unter zicken versteh ich das auch da warnings kommen! brauchst nicht gleich laut schreien! 😉

                              apollon77 1 Reply Last reply Reply Quote 0
                              • apollon77
                                apollon77 @da_Woody last edited by

                                @da_woody sagte in Test Adapter Admin 5.0.x: Alpha der neuen UI:

                                zicken versteh ich das auch da warnings kommen! brauchst nicht gleich laut schreien!

                                zicken heisst für mich das was nicht geht 🙂 Alles gut

                                amg_666 1 Reply Last reply Reply Quote 1
                                • amg_666
                                  amg_666 @apollon77 last edited by

                                  @apollon77 mit laut schreien meinte der nur dass DU ALLES GROSS GESCHRIEBEN HAST 🙂 Schon klar, dass du damit nur klarstellen wolltest, dass es sich nicht auf die Funktionalität auswirkt...

                                  da_Woody 1 Reply Last reply Reply Quote 0
                                  • da_Woody
                                    da_Woody @amg_666 last edited by

                                    @amg_666 👍 ja, ich stamme noch aus der zeit wo auf einen großbuchstaben mit *plonk reagiert wurde...
                                    mei erstes modem war mit höllischen 300 Baud, selbstgelötet. 🙂
                                    wenn was nicht geht, sag ich: dieses teil ist tot. frau ist ja auch nicht kaputt, zickt aber tropsdem mal... 😉

                                    1 Reply Last reply Reply Quote 1
                                    • afuerhoff
                                      afuerhoff Developer last edited by

                                      Hallo,

                                      bei mir wird der Systemeinstellungsdialog in der 5.0.12 nicht angezeigt. Eine weiße Seite erscheint.
                                      https://github.com/ioBroker/ioBroker.admin/issues/803

                                      afuerhoff created this issue in ioBroker/ioBroker.admin

                                      closed system settings dialog - white page #803

                                      1 Reply Last reply Reply Quote 0
                                      • afuerhoff
                                        afuerhoff Developer last edited by

                                        Und hier noch gleiches Problem mit den Scripten
                                        https://github.com/ioBroker/ioBroker.admin/issues/804

                                        afuerhoff created this issue in ioBroker/ioBroker.admin

                                        closed Script view is not shown #804

                                        Homoran 1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators @afuerhoff last edited by

                                          @afuerhoff
                                          kann ich beides nicht nachvollziehen

                                          Die üblichen Verdächtigen

                                          • Browsercache
                                          • Browserkonsole
                                            hast du durch?
                                          afuerhoff 1 Reply Last reply Reply Quote 0
                                          • R
                                            Ritter last edited by

                                            Hallo,

                                            wo kann man bei der neuen Ansicht history und statistik konfigurieren, wo es vorher war steht nur noch Telegram.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            796
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            86
                                            938
                                            207585
                                            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