Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Einbindung von Geräten
  5. Homematic IP - keine Werte (HmIP-eTRV-2)

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    3.5k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.1k

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.5k

Homematic IP - keine Werte (HmIP-eTRV-2)

Geplant Angeheftet Gesperrt Verschoben Einbindung von Geräten
16 Beiträge 4 Kommentatoren 1.2k Aufrufe 2 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • HomoranH Homoran

    @a-gun wer versteckt sich hinter der .59?
    due CCU oder ioBroker?

    du hast duese IP bei beiden drin

    A GunA Offline
    A GunA Offline
    A Gun
    schrieb am zuletzt editiert von
    #7

    @Homoran
    die 192.168.133.59 ist die IP der Homematic CCU, die auf einem Raspberry läuft.
    Ich habe keinen HMIP-Access Point, da läuft bei mir über die CCU.


    iobroker Docker on Synology 918+, jarvis V3.1.2

    HomoranH 1 Antwort Letzte Antwort
    0
    • A GunA A Gun

      @Homoran
      die 192.168.133.59 ist die IP der Homematic CCU, die auf einem Raspberry läuft.
      Ich habe keinen HMIP-Access Point, da läuft bei mir über die CCU.

      HomoranH Nicht stören
      HomoranH Nicht stören
      Homoran
      Global Moderator Administrators
      schrieb am zuletzt editiert von
      #8

      @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

      Ich habe keinen HMIP-Access Point,

      ???

      @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

      die 192.168.133.59 ist die IP der Homematic CCU,

      die hast du aber als Callback Adresse eingetragen. Da muss die IP des ioBroker rein, wenn du schon 0.0.0.0 in den Haupteinstellungen nimmst.
      Warum eigentlich?

      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

      A GunA 1 Antwort Letzte Antwort
      0
      • A GunA A Gun

        @Homoran
        Du meinst, ob ich eine separate RPC-Instanz habe?
        Ja, das habe ich:

        Unbenannt4.PNG Unbenannt3.PNG

        paul53P Offline
        paul53P Offline
        paul53
        schrieb am zuletzt editiert von
        #9

        @a-gun
        Lesen bildet.

        Bitte verzichtet auf Chat-Nachrichten, denn die Handhabung ist grauenhaft !
        Produktiv: RPi 2 mit S.USV, HM-MOD-RPI und SLC-USB-Stick mit root fs

        1 Antwort Letzte Antwort
        2
        • HomoranH Homoran

          @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

          Ich habe keinen HMIP-Access Point,

          ???

          @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

          die 192.168.133.59 ist die IP der Homematic CCU,

          die hast du aber als Callback Adresse eingetragen. Da muss die IP des ioBroker rein, wenn du schon 0.0.0.0 in den Haupteinstellungen nimmst.
          Warum eigentlich?

          A GunA Offline
          A GunA Offline
          A Gun
          schrieb am zuletzt editiert von A Gun
          #10

          @Homoran
          Oha, eben sehe ich es erst, habe ich gleich geändert.

          Leider klappt es immer noch nicht :-(


          iobroker Docker on Synology 918+, jarvis V3.1.2

          HomoranH 1 Antwort Letzte Antwort
          0
          • A GunA A Gun

            @Homoran
            Oha, eben sehe ich es erst, habe ich gleich geändert.

            Leider klappt es immer noch nicht :-(

            HomoranH Nicht stören
            HomoranH Nicht stören
            Homoran
            Global Moderator Administrators
            schrieb am zuletzt editiert von
            #11

            @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

            Leider klappt es immer noch nicht

            und warum nicht?
            was steht om debug log?

            kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

            A GunA 1 Antwort Letzte Antwort
            0
            • HomoranH Homoran

              @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

              Leider klappt es immer noch nicht

              und warum nicht?
              was steht om debug log?

              A GunA Offline
              A GunA Offline
              A Gun
              schrieb am zuletzt editiert von A Gun
              #12

              @homoran

              Reicht das? Oder brauchst du noch mehr Infos?

              Homematic-CCU: 192.168.133.59
              iobroker (Docker Instanz auf Synology NAS): 192.168.133.102

              2022-11-26 16:55:50.967 - info: hm-rega.0 (22778) Got terminate signal TERMINATE_YOURSELF
              2022-11-26 16:55:51.004 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rega.0 send kill signal
              2022-11-26 16:55:51.023 - info: hm-rega.0 (22778) terminating
              2022-11-26 16:55:51.024 - info: hm-rega.0 (22778) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-11-26 16:55:51.600 - info: host.buanet-iobroker1 instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-11-26 16:55:51.613 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
              2022-11-26 16:55:51.621 - info: hm-rpc.0 (26543) Got terminate signal TERMINATE_YOURSELF
              2022-11-26 16:55:51.627 - info: hm-rpc.0 (26543) xmlrpc -> 192.168.133.59:2001/ init ["http://192.168.133.102:2001",""]
              2022-11-26 16:55:51.635 - info: hm-rpc.0 (26543) Disconnected
              2022-11-26 16:55:51.636 - info: hm-rpc.0 (26543) terminating
              2022-11-26 16:55:51.638 - info: hm-rpc.0 (26543) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-11-26 16:55:51.676 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.0 send kill signal
              2022-11-26 16:55:52.203 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-11-26 16:55:52.430 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.1 (force=false, process=true)
              2022-11-26 16:55:52.437 - info: hm-rpc.1 (26614) Got terminate signal TERMINATE_YOURSELF
              2022-11-26 16:55:52.438 - info: hm-rpc.1 (26614) binrpc -> 192.168.133.59:8701/ init ["xmlrpc_bin://192.168.133.102:8701",""]
              2022-11-26 16:55:52.442 - info: hm-rpc.1 (26614) Disconnected
              2022-11-26 16:55:52.448 - info: hm-rpc.1 (26614) terminating
              2022-11-26 16:55:52.450 - info: hm-rpc.1 (26614) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-11-26 16:55:52.474 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.1 send kill signal
              2022-11-26 16:55:53.002 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-11-26 16:55:53.335 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.2 (force=false, process=true)
              2022-11-26 16:55:53.341 - info: hm-rpc.2 (2381) Got terminate signal TERMINATE_YOURSELF
              2022-11-26 16:55:53.343 - info: hm-rpc.2 (2381) xmlrpc -> 192.168.133.59:2010/ init ["http://192.168.133.102:2010",""]
              2022-11-26 16:55:53.375 - info: hm-rpc.2 (2381) Disconnected
              2022-11-26 16:55:53.379 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.2 send kill signal
              2022-11-26 16:55:53.376 - info: hm-rpc.2 (2381) terminating
              2022-11-26 16:55:53.386 - info: hm-rpc.2 (2381) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-11-26 16:55:53.935 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.2 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-11-26 16:55:54.050 - info: host.buanet-iobroker1 instance system.adapter.hm-rega.0 started with pid 2645
              2022-11-26 16:55:55.249 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.0 started with pid 2665
              2022-11-26 16:55:56.100 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.1 started with pid 2676
              2022-11-26 16:55:56.497 - info: hm-rega.0 (2645) starting. Version 3.0.40 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v16.15.1, js-controller: 4.0.23
              2022-11-26 16:55:56.891 - info: hm-rega.0 (2645) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
              2022-11-26 16:55:56.988 - info: hm-rega.0 (2645) ReGaHSS 192.168.133.59 up
              2022-11-26 16:55:57.240 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.2 started with pid 2691
              2022-11-26 16:55:57.352 - info: hm-rega.0 (2645) time difference local-ccu 0s
              2022-11-26 16:55:58.895 - info: hm-rpc.0 (2665) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23
              2022-11-26 16:55:59.283 - info: hm-rpc.0 (2665) xmlrpc server is trying to listen on 0.0.0.0:2001
              2022-11-26 16:55:59.285 - info: hm-rpc.0 (2665) xmlrpc client is trying to connect to 192.168.133.59:2001/ with ["http://192.168.133.102:2001","buanet-iobroker1:hm-rpc.0:d904531dff5457663aeb0822b1eba18d"]
              2022-11-26 16:55:59.363 - info: hm-rpc.0 (2665) xmlrpc <- system.listMethods ["buanet-iobroker1:hm-rpc.0:d904531dff5457663aeb0822b1eba18d"]
              2022-11-26 16:55:59.378 - info: hm-rpc.0 (2665) xmlrpc <- listDevices ["buanet-iobroker1:hm-rpc.0:d904531dff5457663aeb0822b1eba18d"]
              2022-11-26 16:55:59.428 - info: hm-rpc.1 (2676) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23
              2022-11-26 16:55:59.501 - info: hm-rpc.0 (2665) xmlrpc -> 111 devices
              2022-11-26 16:55:59.568 - info: hm-rpc.0 (2665) Connected
              2022-11-26 16:55:59.721 - info: hm-rpc.1 (2676) binrpc server is trying to listen on 0.0.0.0:8701
              2022-11-26 16:55:59.723 - info: hm-rpc.1 (2676) binrpc client is trying to connect to 192.168.133.59:8701/ with ["xmlrpc_bin://192.168.133.102:8701","buanet-iobroker1:hm-rpc.1:cd63876645f45ebeee01d2cb2ad307f5"]
              2022-11-26 16:55:59.990 - info: hm-rpc.1 (2676) binrpc -> listDevices 57
              2022-11-26 16:56:00.110 - info: hm-rpc.1 (2676) new CUxD devices/channels after filter: 0
              2022-11-26 16:56:00.112 - info: hm-rpc.1 (2676) Connected
              2022-11-26 16:56:00.273 - info: hm-rpc.2 (2691) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23
              2022-11-26 16:56:00.430 - info: hm-rpc.2 (2691) xmlrpc server is trying to listen on 0.0.0.0:2010
              2022-11-26 16:56:00.433 - info: hm-rpc.2 (2691) xmlrpc client is trying to connect to 192.168.133.59:2010/ with ["http://192.168.133.102:2010","buanet-iobroker1:hm-rpc.2:d1925a274f2e8b0574e647b136e71637"]
              2022-11-26 16:56:00.546 - info: hm-rpc.2 (2691) Connected
              2022-11-26 16:56:01.501 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.1 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:1"
              2022-11-26 16:56:01.514 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.2 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:2"
              2022-11-26 16:56:01.527 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.3 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:3"
              2022-11-26 16:56:01.543 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.4 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:4"
              2022-11-26 16:56:01.558 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.5 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:5"
              2022-11-26 16:56:01.580 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.6 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:6"
              2022-11-26 16:56:01.595 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.7 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:7"
              2022-11-26 16:56:01.599 - info: hm-rega.0 (2645) request state values
              2022-11-26 16:56:02.407 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200004.0.RSSI_PEER" has value "-256" less than min "-255"
              2022-11-26 16:56:02.803 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200005.0.RSSI_PEER" has value "-256" less than min "-255"
              2022-11-26 16:56:03.032 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200001.0.RSSI_PEER" has value "-256" less than min "-255"
              2022-11-26 16:56:03.163 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200002.0.RSSI_PEER" has value "-256" less than min "-255"
              2022-11-26 16:56:03.419 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200007.0.RSSI_PEER" has value "-256" less than min "-255"
              2022-11-26 16:56:03.605 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200003.0.RSSI_PEER" has value "-256" less than min "-255"
              2022-11-26 16:56:03.779 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200006.0.RSSI_PEER" has value "-256" less than min "-255"
              2022-11-26 16:56:04.841 - info: hm-rega.0 (2645) Updated all datapoints
              2022-11-26 16:56:04.864 - info: hm-rega.0 (2645) got 36 variables
              2022-11-26 16:56:05.224 - warn: hm-rega.0 (2645) State value to set for "hm-rega.0.6131" has value "-5.206074" less than min "0"
              2022-11-26 16:56:05.310 - warn: hm-rega.0 (2645) State value to set for "hm-rega.0.6914" has value "-0.026" less than min "0"
              2022-11-26 16:56:05.472 - info: hm-rega.0 (2645) added/updated 36 variables
              2022-11-26 16:56:05.473 - info: hm-rega.0 (2645) deleted 0 variables
              2022-11-26 16:56:05.493 - info: hm-rega.0 (2645) got 43 programs
              2022-11-26 16:56:06.713 - info: hm-rega.0 (2645) added/updated 43 programs
              2022-11-26 16:56:06.714 - info: hm-rega.0 (2645) deleted 0 programs
              2022-11-26 16:56:06.736 - info: hm-rega.0 (2645) update rooms to enum.rooms
              2022-11-26 16:56:06.799 - info: hm-rega.0 (2645) update functions to enum.functions
              2022-11-26 16:56:06.849 - info: hm-rega.0 (2645) update favorites to enum.favorites
              

              iobroker Docker on Synology 918+, jarvis V3.1.2

              GlasfaserG 1 Antwort Letzte Antwort
              0
              • A GunA A Gun

                @homoran

                Reicht das? Oder brauchst du noch mehr Infos?

                Homematic-CCU: 192.168.133.59
                iobroker (Docker Instanz auf Synology NAS): 192.168.133.102

                2022-11-26 16:55:50.967 - info: hm-rega.0 (22778) Got terminate signal TERMINATE_YOURSELF
                2022-11-26 16:55:51.004 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rega.0 send kill signal
                2022-11-26 16:55:51.023 - info: hm-rega.0 (22778) terminating
                2022-11-26 16:55:51.024 - info: hm-rega.0 (22778) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-11-26 16:55:51.600 - info: host.buanet-iobroker1 instance system.adapter.hm-rega.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-11-26 16:55:51.613 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
                2022-11-26 16:55:51.621 - info: hm-rpc.0 (26543) Got terminate signal TERMINATE_YOURSELF
                2022-11-26 16:55:51.627 - info: hm-rpc.0 (26543) xmlrpc -> 192.168.133.59:2001/ init ["http://192.168.133.102:2001",""]
                2022-11-26 16:55:51.635 - info: hm-rpc.0 (26543) Disconnected
                2022-11-26 16:55:51.636 - info: hm-rpc.0 (26543) terminating
                2022-11-26 16:55:51.638 - info: hm-rpc.0 (26543) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-11-26 16:55:51.676 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.0 send kill signal
                2022-11-26 16:55:52.203 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-11-26 16:55:52.430 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.1 (force=false, process=true)
                2022-11-26 16:55:52.437 - info: hm-rpc.1 (26614) Got terminate signal TERMINATE_YOURSELF
                2022-11-26 16:55:52.438 - info: hm-rpc.1 (26614) binrpc -> 192.168.133.59:8701/ init ["xmlrpc_bin://192.168.133.102:8701",""]
                2022-11-26 16:55:52.442 - info: hm-rpc.1 (26614) Disconnected
                2022-11-26 16:55:52.448 - info: hm-rpc.1 (26614) terminating
                2022-11-26 16:55:52.450 - info: hm-rpc.1 (26614) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-11-26 16:55:52.474 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.1 send kill signal
                2022-11-26 16:55:53.002 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-11-26 16:55:53.335 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.2 (force=false, process=true)
                2022-11-26 16:55:53.341 - info: hm-rpc.2 (2381) Got terminate signal TERMINATE_YOURSELF
                2022-11-26 16:55:53.343 - info: hm-rpc.2 (2381) xmlrpc -> 192.168.133.59:2010/ init ["http://192.168.133.102:2010",""]
                2022-11-26 16:55:53.375 - info: hm-rpc.2 (2381) Disconnected
                2022-11-26 16:55:53.379 - info: host.buanet-iobroker1 stopInstance system.adapter.hm-rpc.2 send kill signal
                2022-11-26 16:55:53.376 - info: hm-rpc.2 (2381) terminating
                2022-11-26 16:55:53.386 - info: hm-rpc.2 (2381) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-11-26 16:55:53.935 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.2 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-11-26 16:55:54.050 - info: host.buanet-iobroker1 instance system.adapter.hm-rega.0 started with pid 2645
                2022-11-26 16:55:55.249 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.0 started with pid 2665
                2022-11-26 16:55:56.100 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.1 started with pid 2676
                2022-11-26 16:55:56.497 - info: hm-rega.0 (2645) starting. Version 3.0.40 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v16.15.1, js-controller: 4.0.23
                2022-11-26 16:55:56.891 - info: hm-rega.0 (2645) subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
                2022-11-26 16:55:56.988 - info: hm-rega.0 (2645) ReGaHSS 192.168.133.59 up
                2022-11-26 16:55:57.240 - info: host.buanet-iobroker1 instance system.adapter.hm-rpc.2 started with pid 2691
                2022-11-26 16:55:57.352 - info: hm-rega.0 (2645) time difference local-ccu 0s
                2022-11-26 16:55:58.895 - info: hm-rpc.0 (2665) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23
                2022-11-26 16:55:59.283 - info: hm-rpc.0 (2665) xmlrpc server is trying to listen on 0.0.0.0:2001
                2022-11-26 16:55:59.285 - info: hm-rpc.0 (2665) xmlrpc client is trying to connect to 192.168.133.59:2001/ with ["http://192.168.133.102:2001","buanet-iobroker1:hm-rpc.0:d904531dff5457663aeb0822b1eba18d"]
                2022-11-26 16:55:59.363 - info: hm-rpc.0 (2665) xmlrpc <- system.listMethods ["buanet-iobroker1:hm-rpc.0:d904531dff5457663aeb0822b1eba18d"]
                2022-11-26 16:55:59.378 - info: hm-rpc.0 (2665) xmlrpc <- listDevices ["buanet-iobroker1:hm-rpc.0:d904531dff5457663aeb0822b1eba18d"]
                2022-11-26 16:55:59.428 - info: hm-rpc.1 (2676) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23
                2022-11-26 16:55:59.501 - info: hm-rpc.0 (2665) xmlrpc -> 111 devices
                2022-11-26 16:55:59.568 - info: hm-rpc.0 (2665) Connected
                2022-11-26 16:55:59.721 - info: hm-rpc.1 (2676) binrpc server is trying to listen on 0.0.0.0:8701
                2022-11-26 16:55:59.723 - info: hm-rpc.1 (2676) binrpc client is trying to connect to 192.168.133.59:8701/ with ["xmlrpc_bin://192.168.133.102:8701","buanet-iobroker1:hm-rpc.1:cd63876645f45ebeee01d2cb2ad307f5"]
                2022-11-26 16:55:59.990 - info: hm-rpc.1 (2676) binrpc -> listDevices 57
                2022-11-26 16:56:00.110 - info: hm-rpc.1 (2676) new CUxD devices/channels after filter: 0
                2022-11-26 16:56:00.112 - info: hm-rpc.1 (2676) Connected
                2022-11-26 16:56:00.273 - info: hm-rpc.2 (2691) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v16.15.1, js-controller: 4.0.23
                2022-11-26 16:56:00.430 - info: hm-rpc.2 (2691) xmlrpc server is trying to listen on 0.0.0.0:2010
                2022-11-26 16:56:00.433 - info: hm-rpc.2 (2691) xmlrpc client is trying to connect to 192.168.133.59:2010/ with ["http://192.168.133.102:2010","buanet-iobroker1:hm-rpc.2:d1925a274f2e8b0574e647b136e71637"]
                2022-11-26 16:56:00.546 - info: hm-rpc.2 (2691) Connected
                2022-11-26 16:56:01.501 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.1 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:1"
                2022-11-26 16:56:01.514 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.2 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:2"
                2022-11-26 16:56:01.527 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.3 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:3"
                2022-11-26 16:56:01.543 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.4 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:4"
                2022-11-26 16:56:01.558 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.5 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:5"
                2022-11-26 16:56:01.580 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.6 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:6"
                2022-11-26 16:56:01.595 - info: hm-rega.0 (2645) renamed hm-rpc.2.000A1F298C1BE8.7 to "SchlaZi-Keller-HmIP-eTRV-2 000A1F298C1BE8:7"
                2022-11-26 16:56:01.599 - info: hm-rega.0 (2645) request state values
                2022-11-26 16:56:02.407 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200004.0.RSSI_PEER" has value "-256" less than min "-255"
                2022-11-26 16:56:02.803 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200005.0.RSSI_PEER" has value "-256" less than min "-255"
                2022-11-26 16:56:03.032 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200001.0.RSSI_PEER" has value "-256" less than min "-255"
                2022-11-26 16:56:03.163 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200002.0.RSSI_PEER" has value "-256" less than min "-255"
                2022-11-26 16:56:03.419 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200007.0.RSSI_PEER" has value "-256" less than min "-255"
                2022-11-26 16:56:03.605 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200003.0.RSSI_PEER" has value "-256" less than min "-255"
                2022-11-26 16:56:03.779 - warn: hm-rega.0 (2645) State value to set for "hm-rpc.1.CUX1200006.0.RSSI_PEER" has value "-256" less than min "-255"
                2022-11-26 16:56:04.841 - info: hm-rega.0 (2645) Updated all datapoints
                2022-11-26 16:56:04.864 - info: hm-rega.0 (2645) got 36 variables
                2022-11-26 16:56:05.224 - warn: hm-rega.0 (2645) State value to set for "hm-rega.0.6131" has value "-5.206074" less than min "0"
                2022-11-26 16:56:05.310 - warn: hm-rega.0 (2645) State value to set for "hm-rega.0.6914" has value "-0.026" less than min "0"
                2022-11-26 16:56:05.472 - info: hm-rega.0 (2645) added/updated 36 variables
                2022-11-26 16:56:05.473 - info: hm-rega.0 (2645) deleted 0 variables
                2022-11-26 16:56:05.493 - info: hm-rega.0 (2645) got 43 programs
                2022-11-26 16:56:06.713 - info: hm-rega.0 (2645) added/updated 43 programs
                2022-11-26 16:56:06.714 - info: hm-rega.0 (2645) deleted 0 programs
                2022-11-26 16:56:06.736 - info: hm-rega.0 (2645) update rooms to enum.rooms
                2022-11-26 16:56:06.799 - info: hm-rega.0 (2645) update functions to enum.functions
                2022-11-26 16:56:06.849 - info: hm-rega.0 (2645) update favorites to enum.favorites
                
                GlasfaserG Offline
                GlasfaserG Offline
                Glasfaser
                schrieb am zuletzt editiert von Glasfaser
                #13

                @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

                Reicht das? Oder brauchst du noch mehr Infos?
                Homematic-CCU: 192.168.133.59
                iobroker (Docker Instanz auf Synology NAS): 192.168.133.102

                Das sollte am Thread -Start schon angegeben werden !

                Hast du die Ports freigegeben / weitergeleitet im Container

                Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                A GunA 1 Antwort Letzte Antwort
                2
                • GlasfaserG Glasfaser

                  @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

                  Reicht das? Oder brauchst du noch mehr Infos?
                  Homematic-CCU: 192.168.133.59
                  iobroker (Docker Instanz auf Synology NAS): 192.168.133.102

                  Das sollte am Thread -Start schon angegeben werden !

                  Hast du die Ports freigegeben / weitergeleitet im Container

                  A GunA Offline
                  A GunA Offline
                  A Gun
                  schrieb am zuletzt editiert von
                  #14

                  @glasfaser
                  Heureka!!! Danke, das war der entscheidende Tipp!

                  Wie blöd von mir! Hätte ich auch wirklich dazuschreiben sollen (schäm)


                  iobroker Docker on Synology 918+, jarvis V3.1.2

                  GlasfaserG 1 Antwort Letzte Antwort
                  0
                  • A GunA A Gun

                    @glasfaser
                    Heureka!!! Danke, das war der entscheidende Tipp!

                    Wie blöd von mir! Hätte ich auch wirklich dazuschreiben sollen (schäm)

                    GlasfaserG Offline
                    GlasfaserG Offline
                    Glasfaser
                    schrieb am zuletzt editiert von
                    #15

                    @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

                    Heureka!!! Danke, das war der entscheidende Tipp!

                    Nee ...

                    war schon viel früher , steht alles im Link ;)

                    5c41bb01-5ab8-40d8-9b19-699b565d8039-grafik.png

                    Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                    A GunA 1 Antwort Letzte Antwort
                    1
                    • GlasfaserG Glasfaser

                      @a-gun sagte in Homematic IP - keine Werte (HmIP-eTRV-2):

                      Heureka!!! Danke, das war der entscheidende Tipp!

                      Nee ...

                      war schon viel früher , steht alles im Link ;)

                      5c41bb01-5ab8-40d8-9b19-699b565d8039-grafik.png

                      A GunA Offline
                      A GunA Offline
                      A Gun
                      schrieb am zuletzt editiert von
                      #16

                      @glasfaser
                      Hab ich tatsächlich gelesen - aber wohl ÜBERlesen :man-facepalming:


                      iobroker Docker on Synology 918+, jarvis V3.1.2

                      1 Antwort Letzte Antwort
                      0
                      Antworten
                      • In einem neuen Thema antworten
                      Anmelden zum Antworten
                      • Älteste zuerst
                      • Neuste zuerst
                      • Meiste Stimmen


                      Support us

                      ioBroker
                      Community Adapters
                      Donate

                      710

                      Online

                      32.7k

                      Benutzer

                      82.4k

                      Themen

                      1.3m

                      Beiträge
                      Community
                      Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                      ioBroker Community 2014-2025
                      logo
                      • Anmelden

                      • Du hast noch kein Konto? Registrieren

                      • Anmelden oder registrieren, um zu suchen
                      • Erster Beitrag
                        Letzter Beitrag
                      0
                      • Home
                      • Aktuell
                      • Tags
                      • Ungelesen 0
                      • Kategorien
                      • Unreplied
                      • Beliebt
                      • GitHub
                      • Docu
                      • Hilfe