Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. HMIP (BROLL und BBL) type Fehler

    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

    HMIP (BROLL und BBL) type Fehler

    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      reutli last edited by

      Hallo,

      habe seit geraumer Zeit ziemlich viele "Fehlermeldungen" zu falschem Typ bei den Aktoren von HMIP:

      hm-rpc.1
	2023-04-28 09:58:57.654	info	State value to set for "hm-rpc.1.0013570996027C.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:57:52.241	info	State value to set for "hm-rpc.1.001358A9955884.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:57:28.175	info	State value to set for "hm-rpc.1.001358A99558C8.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:57:02.050	info	State value to set for "hm-rpc.1.001357099603DC.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:55:33.880	info	State value to set for "hm-rpc.1.001357099606C9.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:53:52.610	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:52:05.118	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:52:04.758	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:52:00.724	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:52:00.397	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:47:39.681	info	State value to set for "hm-rpc.1.001358A99558CD.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:47:15.623	info	State value to set for "hm-rpc.1.00111A499157F2.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:42:05.015	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:42:04.651	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:42:00.607	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:42:00.278	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:32:05.153	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:32:04.800	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:32:00.532	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:32:00.323	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:31:12.927	info	State value to set for "hm-rpc.1.001397099C4727.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:28:21.507	info	State value to set for "hm-rpc.1.0013570995FDFA.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:27:11.833	info	State value to set for "hm-rpc.1.001358A9955878.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:24:28.451	info	State value to set for "hm-rpc.1.001358A99558C8.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:22:05.167	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:22:04.826	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:22:00.821	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:22:00.468	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:15:05.873	info	State value to set for "hm-rpc.1.00369F2999E89F.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:13:22.083	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:13:05.117	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:13:04.786	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:13:00.586	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:13:00.352	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:12:05.092	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:12:04.840	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:12:00.719	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:12:00.373	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:11:51.828	info	State value to set for "hm-rpc.1.001357099603DC.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:09:15.075	info	State value to set for "hm-rpc.1.001358A9955878.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:08:22.889	info	State value to set for "hm-rpc.1.0013570996027C.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:02:18.391	info	State value to set for "hm-rpc.1.00369F2999E89F.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:02:13.267	info	State value to set for "hm-rpc.1.001358A9955884.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:02:05.077	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:02:04.721	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:02:00.668	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:02:00.332	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 09:01:30.587	info	State value to set for "hm-rpc.1.00111A499157F2.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:58:24.672	info	State value to set for "hm-rpc.1.00135D89B0377F.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:56:17.184	info	State value to set for "hm-rpc.1.001397099C4727.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:52:05.010	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:52:04.656	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:52:00.649	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:52:00.291	info	State value to set for "hm-rpc.1.00111D8994B65B.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:51:27.857	info	State value to set for "hm-rpc.1.001358A99558CD.3.SECTION" has to be type "number" but received type "string"
hm-rpc.1
	2023-04-28 08:50:29.774	info	State value to set for "hm-rpc.1.0013570995FDFA.3.SECTION" has to be type "number" but received type "string"

      Es scheint daran zu liegen, dass die Geräte, wenn Sie geschalten werden im DP "gerät.3.SECTION" keinen Wert enthalten, der dann als "String" erkannt wird, aber "number" erwartet wird.

      Hier beispielhaft ein Objekt:

      {
  "type": "state",
  "common": {
    "name": "Markise Wintergarten Status.SECTION",
    "role": "",
    "def": 0,
    "type": "number",
    "read": true,
    "write": false,
    "min": 0,
    "max": 15
  },
  "native": {
    "MIN": 0,
    "OPERATIONS": 5,
    "MAX": 15,
    "FLAGS": 1,
    "ID": "SECTION",
    "TYPE": "INTEGER",
    "DEFAULT": 0
  },
  "from": "system.adapter.hm-rega.0",
  "user": "system.user.admin",
  "ts": 1682610367811,
  "_id": "hm-rpc.1.00111D8994B65B.3.SECTION",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  }
}

      Die Meldungen sind natürlich ziemlich nervig und eigentlich steht ja eigentlich ein default "0" drin, der auch einmalig nach Adapterstart oder Neueinlesen greift. Sobald aber der Aktor bedient wird, fliegt die "0" raus und DP ist leer.

      Gibt es hierfür einen Lösungsansatz oder workaround?
      Mir ist schon bewusst, dass das ein Homematic Problem zu sein scheint, allerdings suche ich nach einer Lösung, dass es einfach ignoriert wird oder nach Erfahrungen und Lösungen anderer User.

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

        @reutli sagte in HMIP (BROLL und BBL) type Fehler:

        dass die Geräte, wenn Sie geschalten werden

        per Script?

        R 1 Reply Last reply Reply Quote 0
        • R
          reutli @Homoran last edited by reutli

          @homoran sagte in HMIP (BROLL und BBL) type Fehler:

          per Script?

          wahlfrei.

          Neustart des Adapter/einmalig neu einlesen --> 3.section = 0
          Aktor steuern - egal wie --> 3.section = ""

          Channel "3" ist der Status-Channel, also nicht der Aktor. Damit wird der nicht direkt angefasst beim Schalten, sondern liefert nur Status zurück.

          Codierknecht 1 Reply Last reply Reply Quote 0
          • Codierknecht
            Codierknecht Developer Most Active @reutli last edited by

            @reutli
            Sieht bei mir genau so aus, führt aber zu keinem Fehler.
            Möglicherweise weil ich diesen Wert nirgendwo verwende.

            3e823d60-74ea-4b53-a8cd-7d4ac65852b9-image.png

            R 1 Reply Last reply Reply Quote 0
            • R
              reutli @Codierknecht last edited by reutli

              @codierknecht

              Tja, ich habe das m.E. auch nicht bei jedem der 20-30 Stück, aber eben bei einigen.
              Es wirft ja auch nicht wirklich einen "Fehler" sondern eine Meldung. Ist nur unglaublich nervig... vor allem will man ja das LOG einigermaßen sauber haben.

              Den Wert nutze ich btw. auch an keiner Stelle, ausser vielleicht (unwissentlich) in Jarvis und ich habe Alices angelegt... aber das kann doch nicht wirklich der Auslöser sein?

              Codierknecht 1 Reply Last reply Reply Quote 0
              • Codierknecht
                Codierknecht Developer Most Active @reutli last edited by

                @reutli sagte in HMIP (BROLL und BBL) type Fehler:

                und ich habe Alices angelegt

                Aliase auf diesen DP?
                Ich habe keine darauf - könnte natürlich eine Ursache sein. Aber da der Fehler vom Hm-RPC und nicht vom Alias geworfen wird, würde ich das mal ausschließen.

                1 Reply Last reply Reply Quote 0
                • Dr. Bakterius
                  Dr. Bakterius Most Active last edited by

                  Dafür gibt es seit ein paar Wochen ein Issue: https://github.com/ioBroker/ioBroker.hm-rpc/issues/872

                  MichaelSchaaf999 created this issue in ioBroker/ioBroker.hm-rpc

                  closed Since CCU firmware update to 3.69.6 we see info messages for nearly every HmIP device #872

                  R 1 Reply Last reply Reply Quote 0
                  • R
                    reutli @Dr. Bakterius last edited by

                    @dr-bakterius

                    Danke für den Hinweis. Dann muss das wohl ein RPC-Adapter-Update geben, oder wo ist der "root-cause"?

                    Dr. Bakterius 1 Reply Last reply Reply Quote 0
                    • Dr. Bakterius
                      Dr. Bakterius Most Active @reutli last edited by

                      @reutli Ich habe mir damit beholfen den DP auf Text zu ändern. Da kommt nur einmal die Meldung wenn die '0' geschrieben wird. Mit 'multistate' sollte nicht einmal das passieren. Wäre also leicht vom Entwickler zu beheben...

                      F 1 Reply Last reply Reply Quote 0
                      • F
                        Frank 5 @Dr. Bakterius last edited by

                        @dr-bakterius

                        Hallo, hat jemand eine Lösung gefunden?
                        Ich bekomme die Fehlermeldung immer noch!

                        R 1 Reply Last reply Reply Quote 0
                        • R
                          reutli @Frank 5 last edited by

                          @frank-5

                          Bisher nicht, da braucht es ein Adapter - Update, da steht aber gerade Wichtigeres an... ansonsten Lösungsansätze siehe oben....

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

                          Support us

                          ioBroker
                          Community Adapters
                          Donate
                          FAQ Cloud / IOT
                          HowTo: Node.js-Update
                          HowTo: Backup/Restore
                          Downloads
                          BLOG

                          502
                          Online

                          31.9k
                          Users

                          80.1k
                          Topics

                          1.3m
                          Posts

                          5
                          11
                          474
                          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