Ankündigung

Einklappen
Keine Ankündigung bisher.

Init read knx problem

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

    Init read knx problem

    Hello,

    I have a problem when i start / restart my smarthome. I would like to read some knx status at init.

    My item config :

    Code:
    [cuisine]
          [[lum]]
                    [[[spot]]]
                            type = bool
                            knx_dpt = 1
                            knx_send = 4/0/10
                            knx_listen = 4/1/10
                            knx_init = 4/1/10
    but at start SH didn't read 4/1/10 status ... if i try a manual "groupsocketread at 4/1/10" my item is update correctly.
    Can you tell me how to force the read init status ?

    Thanks a lot
    Zuletzt geändert von chrissou; 26.03.2015, 08:28.

    #2
    Hi,

    please provide more information. Complete debuglog, plugin.conf, KNX interface type/model.

    so long

    Marcus

    Kommentar


      #3
      My plugin.conf :

      Code:
      [knx]
              class_name = KNX
              class_path = plugins.knx
              send_time = 600
              date_ga = 0/1/1
              time_ga = 0/1/2
              busmonitor = false
      I use eibd server on the same linux as smarthome.
      My KNX interface is a Siemens N148/22.

      My full debug log at startup :
      http://paste.debian.net/163149/

      And here the debug log when i send "groupsocketread ip:127.0.0.1 4/1/10"
      Code:
      2015-03-25 13:11:02,262 DEBUG    Main         KNX: 0.0.0 read 4/1/10 -- __init__.py:parse_telegram:211
      2015-03-25 13:11:02,311 DEBUG    Main         knx: 0.0.2 set 4/1/10 to True -- __init__.py:parse_telegram:198
      2015-03-25 13:11:02,312 DEBUG    Main         Item cuisine.lum.spot = True via KNX 0.0.2 4/1/10 -- item.py:__update:369

      Thanks a lot for your help
      Zuletzt geändert von chrissou; 25.03.2015, 13:12.

      Kommentar


        #4
        Hi,

        I think the problem is with the eibd and your interface. Try starting the eibd with "--no-tunnel-client-queuing".

        so long

        Marcus

        Kommentar


          #5
          I just try and it works !
          Thanks a lot for your help

          Kommentar

          Lädt...
          X