Raspberry Pi 3 und RS-485 wollen nicht

shizzleslick · December 13, 2016, 2:06pm

Vielen Dank, daß Du Dir noch die Mühe machst!
So wie ich das sehe, horcht nur ein process auf die serielle Schnittstelle:

lsof /dev/ttyS0
COMMAND   PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
homegear 5052 homegear    8u   CHR   4,64      0t0 1108 /dev/ttyS0

Gruß,
shizzleslick

sathya · December 13, 2016, 3:23pm

ok, super. Zeigt Homegear ein Paket im Log an wenn du den Schalter drückst?

shizzleslick · December 14, 2016, 8:35pm

Hallo @sathya,

In der Tat :-):

12/14/16 21:27:57.366 Debug: SSDP server: Binding to address: 192.168.0.66
12/14/16 21:27:57.366 Debug: Searching for SSDP devices ...
12/14/16 21:28:00.713 Debug (HM-RS485): Packet FDFFFFFFFF9800005A2D064B0000AAE998 enters raisePacketReceived.
12/14/16 21:28:00.713 Debug (HM-RS485): Packet FDFFFFFFFF9800005A2D064B0000AAE998 is now passed to the EventHandler.
12/14/16 21:28:00.713 HomeMatic Wired packet received: FDFFFFFFFF9800005A2D064B0000AAE998
12/14/16 21:28:00.713 Debug (HM-RS485): Packet processing of packet FDFFFFFFFF9800005A2D064B0000AAE998 took 0 ms.
12/14/16 21:28:00.735 Debug (HM-RS485): Packet FDFFFFFFFF9A00005A2D124100120003066865713032343037393339B6 enters raisePacketReceived.
12/14/16 21:28:00.735 Debug (HM-RS485): Packet FDFFFFFFFF9A00005A2D124100120003066865713032343037393339B6 is now passed to the EventHandler.
12/14/16 21:28:00.735 HomeMatic Wired packet received: FDFFFFFFFF9A00005A2D124100120003066865713032343037393339B6
12/14/16 21:28:00.735 Debug (HM-RS485): Packet processing of packet FDFFFFFFFF9A00005A2D124100120003066865713032343037393339B6 took 0 ms.
12/14/16 21:28:00.735 Module HomeMatic Wired: Info: New device detected on bus.
12/14/16 21:28:00.762 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1C0000000106520000108360)
12/14/16 21:28:00.763 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1C0000000106520000108360
12/14/16 21:28:00.872 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1C0000000106520000108360)
12/14/16 21:28:00.872 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1C0000000106520000108360
12/14/16 21:28:00.982 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1C0000000106520000108360)
12/14/16 21:28:00.982 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1C0000000106520000108360
12/14/16 21:28:01.092 Module HomeMatic Wired: Error: HomeMatic Wired Central: Could not pair device with address 0x00005A2D. Could not read master config from EEPROM.
12/14/16 21:28:01.093 RPC client: Info: Calling RPC method "system.multicall" on server 127.0.0.1.
12/14/16 21:28:01.093 RPC client: Parameters:
(Array length=1)
{
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) Homegear
        (String) heq0240793
        (String) 
        (Struct length=2)
        {
          [CODE]
          {
            (Integer) 1
          }
          [TYPE]
          {
            (Integer) 1
          }
        }
      }
    }
  }
}
12/14/16 21:28:01.093 Debug: Calling getFileDescriptor...
12/14/16 21:28:01.093 Debug: Connecting to host 127.0.0.1 on port 9123...
12/14/16 21:28:01.094 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 87688
12/14/16 21:28:01.095 RPC client: Debug: Sending packet: 42696E00000000A70000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D7300000100000000040000000300000008486F6D6567656172000000030000000A686571303234303739330000000300000000000001010000000200000004434F4445000000010000000100000004545950450000000100000001
Warning: Connection to client number 87688 closed (3).
12/14/16 21:28:01.104 Debug: Calling getFileDescriptor...
12/14/16 21:28:01.104 Debug: Connecting to host 127.0.0.1 on port 9123...
12/14/16 21:28:01.105 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 87689
12/14/16 21:28:01.105 RPC client: Debug: Sending packet: 42696E00000000A70000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D7300000100000000040000000300000008486F6D6567656172000000030000000A686571303234303739330000000300000000000001010000000200000004434F4445000000010000000100000004545950450000000100000001
Warning: Connection to client number 87689 closed (3).
12/14/16 21:28:01.114 Debug: Calling getFileDescriptor...
12/14/16 21:28:01.114 Debug: Connecting to host 127.0.0.1 on port 9123...
12/14/16 21:28:01.115 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 87690
12/14/16 21:28:01.115 RPC client: Debug: Sending packet: 42696E00000000A70000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D7300000100000000040000000300000008486F6D6567656172000000030000000A686571303234303739330000000300000000000001010000000200000004434F4445000000010000000100000004545950450000000100000001
Warning: Connection to client number 87690 closed (3).
Removing server "Homegear". Server has to send "init" again.
12/14/16 21:28:02.543 Debug (HM-RS485): Packet FDFFFFFFFF9C00005A2D064B0000AE5B80 enters raisePacketReceived.
12/14/16 21:28:02.543 Debug (HM-RS485): Packet FDFFFFFFFF9C00005A2D064B0000AE5B80 is now passed to the EventHandler.
12/14/16 21:28:02.543 HomeMatic Wired packet received: FDFFFFFFFF9C00005A2D064B0000AE5B80
12/14/16 21:28:02.544 Debug (HM-RS485): Packet processing of packet FDFFFFFFFF9C00005A2D064B0000AE5B80 took 0 ms.
12/14/16 21:28:02.565 Debug (HM-RS485): Packet FDFFFFFFFF9E00005A2D1241001200030668657130323430373933CBC0 enters raisePacketReceived.
12/14/16 21:28:02.565 Debug (HM-RS485): Packet FDFFFFFFFF9E00005A2D1241001200030668657130323430373933CBC0 is now passed to the EventHandler.
12/14/16 21:28:02.565 HomeMatic Wired packet received: FDFFFFFFFF9E00005A2D1241001200030668657130323430373933CBC0
12/14/16 21:28:02.565 Debug (HM-RS485): Packet processing of packet FDFFFFFFFF9E00005A2D1241001200030668657130323430373933CBC0 took 0 ms.
12/14/16 21:28:02.565 Module HomeMatic Wired: Info: New device detected on bus.
12/14/16 21:28:02.591 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1E000000010652000010FA68)
12/14/16 21:28:02.592 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1E000000010652000010FA68
12/14/16 21:28:02.701 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1E000000010652000010FA68)
12/14/16 21:28:02.701 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1E000000010652000010FA68
12/14/16 21:28:02.811 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1E000000010652000010FA68)
12/14/16 21:28:02.811 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1E000000010652000010FA68
12/14/16 21:28:02.921 Module HomeMatic Wired: Error: HomeMatic Wired Central: Could not pair device with address 0x00005A2D. Could not read master config from EEPROM.
12/14/16 21:28:04.521 Debug (HM-RS485): Packet FD000000011A00005A2D06690CC8006EC4 enters raisePacketReceived.
12/14/16 21:28:04.521 Debug (HM-RS485): Packet FD000000011A00005A2D06690CC8006EC4 is now passed to the EventHandler.
12/14/16 21:28:04.521 HomeMatic Wired packet received: FD000000011A00005A2D06690CC8006EC4
12/14/16 21:28:04.521 Debug (HM-RS485): Packet processing of packet FD000000011A00005A2D06690CC8006EC4 took 0 ms.
12/14/16 21:28:04.589 Debug (HM-RS485): Packet FD000000011A00005A2D06690CC8006EC4 enters raisePacketReceived.
12/14/16 21:28:04.589 Debug (HM-RS485): Packet FD000000011A00005A2D06690CC8006EC4 is now passed to the EventHandler.
12/14/16 21:28:04.589 HomeMatic Wired packet received: FD000000011A00005A2D06690CC8006EC4
12/14/16 21:28:04.590 Debug (HM-RS485): Packet processing of packet FD000000011A00005A2D06690CC8006EC4 took 1 ms.
12/14/16 21:28:04.650 Debug (HM-RS485): Packet FD000000011A00005A2D06690CC8006EC4 enters raisePacketReceived.
12/14/16 21:28:04.650 Debug (HM-RS485): Packet FD000000011A00005A2D06690CC8006EC4 is now passed to the EventHandler.
12/14/16 21:28:04.650 HomeMatic Wired packet received: FD000000011A00005A2D06690CC8006EC4
12/14/16 21:28:04.651 Debug (HM-RS485): Packet processing of packet FD000000011A00005A2D06690CC8006EC4 took 1 ms.
12/14/16 21:28:12.848 UPnP Server: Debug: Sending notify packets.
12/14/16 21:28:23.082 Debug: SSDP server: Binding to address: 192.168.0.66
12/14/16 21:28:23.082 Debug: Searching for SSDP devices ...
12/14/16 21:28:47.155 RPC Server (Port 2001): Info: Connection from 127.0.0.1:59540 accepted. Client number: 87692
12/14/16 21:28:47.156 RPC Server (Port 2001): Info: RPC server client id for client number 87692 is: 52650
12/14/16 21:28:47.156 RPC Server (Port 2001): Listening for incoming packets from client number 87692.
12/14/16 21:28:47.158 RPC Server (Port 2001): Debug: Packet received: 42696E000000002B00000004696E697400000001000000030000001762696E6172793A2F2F3132372E302E302E313A39313233
12/14/16 21:28:47.158 RPC Server (Port 2001): Info: Client number 87692 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
12/14/16 21:28:47.158 Info: Removing server "binary://127.0.0.1".
12/14/16 21:28:47.159 RPC Server (Port 2001): Response: 
(void)
12/14/16 21:28:47.159 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
12/14/16 21:28:47.162 RPC Server (Port 2001): Info: Connection to client number 87692 closed (3).
12/14/16 21:28:47.166 RPC Server (Port 2001): Info: Connection from 127.0.0.1:59542 accepted. Client number: 87693
12/14/16 21:28:47.166 RPC Server (Port 2001): Info: RPC server client id for client number 87693 is: 52651
12/14/16 21:28:47.167 RPC Server (Port 2001): Listening for incoming packets from client number 87693.
12/14/16 21:28:47.168 RPC Server (Port 2001): Debug: Packet received: 42696E000000002D000000146765744465766963654465736372697074696F6E000000010000000300000009426964436F532D5246
12/14/16 21:28:47.168 RPC Server (Port 2001): Info: Client number 87693 is calling RPC method: getDeviceDescription (2) Parameters:
(String) BidCoS-RF
12/14/16 21:28:47.169 RPC Server (Port 2001): Response: 
(Struct length=2)
{
  [FIRMWARE]
  {
    (String) 0.6.7-1545
  }
  [TYPE]
  {
    (String) Homegear
  }
}
12/14/16 21:28:47.169 RPC Server (Port 2001): Response binary:
42696E010000003E0000010100000002000000084649524D57415245000000030000000A302E362E372D3135343500000004545950450000000300000008486F6D6567656172
12/14/16 21:28:47.172 RPC Server (Port 2001): Info: Connection to client number 87693 closed (3).
12/14/16 21:28:47.175 RPC Server (Port 2001): Info: Connection from 127.0.0.1:59544 accepted. Client number: 87694
12/14/16 21:28:47.175 RPC Server (Port 2001): Info: RPC server client id for client number 87694 is: 52652
12/14/16 21:28:47.176 RPC Server (Port 2001): Listening for incoming packets from client number 87694.
12/14/16 21:28:47.176 RPC Server (Port 2001): Debug: Packet received: 42696E00000000190000000C676574416C6C56616C756573000000010000000201
12/14/16 21:28:47.176 RPC Server (Port 2001): Info: Client number 87694 is calling RPC method: getAllValues (2) Parameters:
(Boolean) 1
12/14/16 21:28:47.192 RPC Server (Port 2001): Response: 
(Array length=0)
{
}
12/14/16 21:28:47.192 RPC Server (Port 2001): Response binary:
42696E01000000080000010000000000
12/14/16 21:28:47.195 RPC Server (Port 2001): Info: Connection to client number 87694 closed (3).
12/14/16 21:28:47.197 RPC Server (Port 2001): Info: Connection from 127.0.0.1:59546 accepted. Client number: 87695
12/14/16 21:28:47.198 RPC Server (Port 2001): Info: RPC server client id for client number 87695 is: 52653
12/14/16 21:28:47.199 RPC Server (Port 2001): Listening for incoming packets from client number 87695.
12/14/16 21:28:47.199 RPC Server (Port 2001): Debug: Packet received: 42696E000000001D00000015676574416C6C53797374656D5661726961626C657300000000
12/14/16 21:28:47.199 RPC Server (Port 2001): Info: Client number 87695 is calling RPC method: getAllSystemVariables (2) Parameters:
12/14/16 21:28:47.199 RPC Server (Port 2001): Response: 
(Struct length=0)
{
}
12/14/16 21:28:47.200 RPC Server (Port 2001): Response binary:
42696E01000000080000010100000000
12/14/16 21:28:47.204 RPC Server (Port 2001): Info: Connection to client number 87695 closed (3).
12/14/16 21:28:47.206 RPC Server (Port 2001): Info: Connection from 127.0.0.1:59548 accepted. Client number: 87696
12/14/16 21:28:47.207 RPC Server (Port 2001): Info: RPC server client id for client number 87696 is: 52654
12/14/16 21:28:47.208 RPC Server (Port 2001): Listening for incoming packets from client number 87696.
12/14/16 21:28:47.208 RPC Server (Port 2001): Debug: Packet received: 42696E000000003B00000004696E697400000002000000030000001762696E6172793A2F2F3132372E302E302E313A393132330000000300000008486F6D6567656172
12/14/16 21:28:47.208 RPC Server (Port 2001): Info: Client number 87696 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
(String) Homegear
12/14/16 21:28:47.208 Info: Adding server "binary://127.0.0.1".
12/14/16 21:28:47.209 RPC Server (Port 2001): Response: 
(void)
12/14/16 21:28:47.209 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
12/14/16 21:28:47.209 Info: Calling init methods on server "binary://127.0.0.1".
12/14/16 21:28:47.213 RPC Server (Port 2001): Info: Connection to client number 87696 closed (3).
12/14/16 21:28:47.710 RPC client: Info: Calling RPC method "system.listMethods" on server binary://127.0.0.1.
12/14/16 21:28:47.710 RPC client: Parameters:
12/14/16 21:28:47.711 Debug: Calling getFileDescriptor...
12/14/16 21:28:47.711 Debug: Connecting to host 127.0.0.1 on port 9123...
12/14/16 21:28:47.713 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 87697
12/14/16 21:28:47.713 RPC client: Debug: Sending packet: 42696E000000001A0000001273797374656D2E6C6973744D6574686F647300000000
12/14/16 21:28:47.714 RPC client: Debug: Packet received: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
12/14/16 21:28:47.715 RPC client: Debug: Received packet from server 127.0.0.1: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
12/14/16 21:28:47.715 RPC client: Response was:
(Array length=2)
{
  (String) system.multicall
  (String) event
}
12/14/16 21:28:47.715 Debug: Adding method system.multicall
12/14/16 21:28:47.715 Debug: Adding method event
12/14/16 21:28:48.208 RPC Server (Port 2001): Debug: Joining read thread of client 52650
12/14/16 21:28:48.209 RPC Server (Port 2001): Debug: Client 52650 removed.
12/14/16 21:28:48.209 RPC Server (Port 2001): Debug: Joining read thread of client 52651
12/14/16 21:28:48.209 RPC Server (Port 2001): Debug: Client 52651 removed.
12/14/16 21:28:48.209 RPC Server (Port 2001): Debug: Joining read thread of client 52652
12/14/16 21:28:48.209 RPC Server (Port 2001): Debug: Client 52652 removed.
12/14/16 21:28:48.209 RPC Server (Port 2001): Debug: Joining read thread of client 52653
12/14/16 21:28:48.210 RPC Server (Port 2001): Debug: Client 52653 removed.
12/14/16 21:28:48.210 RPC Server (Port 2001): Debug: Joining read thread of client 52654
12/14/16 21:28:48.210 RPC Server (Port 2001): Debug: Client 52654 removed.
12/14/16 21:28:48.795 Debug: SSDP server: Binding to address: 192.168.0.66
12/14/16 21:28:48.795 Debug: Searching for SSDP devices ...

Ich denke mal dies ist interessant:
12/14/16 21:28:01.092 Module HomeMatic Wired: Error: HomeMatic Wired Central: Could not pair device with address 0x00005A2D. Could not read master config from EEPROM.

Gruß,
shizzleslick

sathya · December 20, 2016, 9:43am

Hallo @shizzleslick,

ok, es sieht so aus, als würden wir alles empfangen können aber es wird offenbar nichts gesendet. Wenn alles korrekt verkabelt ist, habe ich auf Anhieb keine Idee, woran es liegen könnte. In so einer Situation schließe ich einen Logikanalysator an und schaue, ob ich Pakete auf der Leitung sehe. Aber einen solchen oder ein Oszilloskop hast du vermutlich nicht zur Verfügung?

Ich haue noch einmal Christian an, vielleicht hat er noch eine Idee.

Viele Grüße

Sathya

shizzleslick · December 20, 2016, 10:13am

Hallo @sathya,

Aha, softwareseitig kann man aber das “nichts senden” ausschließen?
Was heißt denn “Could not read master config from EEPROM.” ? Liest sich ja für den Laien eher wie ein Empfangsproblem (aber wahrscheinlich ist das aus dem Zusammenhang gerissen).
D.h. ich werde die Verkablung nochmals kontrollieren.

Tja, ich habe zwar Zugriff auf ein Oszi, kann aber ehrlich gesagt damit gar nicht umgehen
Oder gibt es irgendwo nen Buch “Oszilloskope für Dummies” ?

Gruß,
shizzleslick

sathya · December 20, 2016, 9:01pm

Das stimmt. Die Meldung bedeutet, dass keine Antwort auf das EEPROM-Lese-Paket erhalten wurde. Das liegt aber mit sehr großer Wahrscheinlichkeit daran, dass das Lese-Paket vom Gerät nicht empfangen wurde. In Homegear werden ja Pakete empfangen. Es gibt aber keinerlei Reaktion auf Pakete, welche softwareseitig gesendet werden.

Im Oszilloskop reicht es im Prinzip, wenn du auf der Sendeleitung mit jedem Paket ein Signal siehst. Die Interpretation ist zunächst einmal egal. Ich kann dir auch anbieten, dein RS485-Modul einmal bei mir zu testen.

Viele Grüße

Sathya

shizzleslick · December 29, 2016, 10:11am

Hallo @sathya,

Ich habe ein neues Modul ausprobiert, leider mit dem gleichen Ergebnis.

D.h. homegear schickt ein EEPROM-Lese-Packet an die wired-Komponenten und Du vermutest, daß dieses Paket von den wired-Komponenten nicht empfangen wurde, oder meinst Du, daß die Komponenten fleissig antworten und homegear es “nicht mitbekommt”?
Wäre es möglich kurz diesen Part der Konfig zu erklären?

## Should be "13" for serial modules, "20" for USB modules and "8" for HMW-LGW.
responseDelay = 13

## Set to "true" for USB modules
oneWay = false

## GPIO to enable RX (RE)
gpio1 = 17

## Set GPIO to this value to enable RX
enableRXValue = 0

## GPIO to enable TX (DE)
gpio2 = 18

## Set GPIO to this value to enable TX
enableTXValue = 1

Ich verstehe nämlich nicht ganz wie das “Senden und Empfangen” funktioniert. So wie ich es laienhaft verstehe, sollte ja eigentlich der GPIO1 auf “IN” stehen, da es ja für RX ist und der GPIO2 auf “OUT” für TX.
So sieht es allerdings bei mir aus:
| 17 | 0 | GPIO. 0 | OUT | 0 | 11 || 12 | 1 | OUT | GPIO. 1 | 1 | 18 |

Besteht denn die Möglichkeit, daß das “Senden” der Pakete von homegear an die Komponenten nie ankommt?

Vielen Dank im Voraus!
Ich wünsch euch allen einen guten Rutsch ins neue Jahr!

PS: Ich muss mir erst neue Tastköpfe für das Oszi holen, die von meinem betagten Gerät (HP 546450) haben Wackelkontakte

Gruß,
shizzleslick

shizzleslick · January 3, 2017, 1:28pm

Hallo,

Ich wünsche euch allen ein frohes neues Jahr. Ich habe noch nicht aufgeben, habe mir aber jetzt zwei andere RS-485 ICs (keine kompletten Module) bestellt und werde es mal damit probieren

Gruß,
shizzleslick

sathya · January 5, 2017, 1:22pm

Ersteres. Das Paket wird von den Komponenten gar nicht empfangen. Sonst würden wir das Paket auch sehen (wir empfangen ja Pakete).

klar.

responseDelay = 13: Die Zeit die gewartet wird, bis auf ein empfangenes Paket eine Antwort gesendet wird - nicht ändern.

oneWay = false: Nicht über USB angeschlossene Module können auf Rx ihr eigenes gesendetes Paket sehen und kontrollieren. So wird auch das vollständige Senden des Paketes erkannt. Mit USB-Modulen geht das nicht. Dieser Paremter MUSS korrekt gesetzt sein (also false für USB und true für UART).

Nachtrag: Korrekt ist “true” für USB und “false” für UART.

gpio1 = 17: Über diesen GPIO wird das Senden aktiviert (nicht gesendet!). Entsprechend muss dieser auf “OUT” stehen.

enableRXValue = 0: Diesen Wert muss der GPIO haben, damit gesendet wird. 0 sollte eigentlich stimmten, du kannst aber mal 1 ausprobieren.

gpio2 = 18: Das gleiche nur für Empfang.

enableTXValue = 1: Der Empfang funktioniert ja, daher muss an dieser Stelle nichts geändert werden.

Wie oben beschrieben, wird über diese GPIOs nicht gesendet. Gesendet wird über die UART-Rx (GPIO 15)!

Ja, das ist sehr wahrscheinlich das Problem.

Viele Grüße

Sathya

shizzleslick · January 4, 2017, 3:42pm

Hallo @sathya,

Vielen Dank für Deine Erklärung!

Ich habe da ein kleines Verständnisproblem (bin zumindest verwirrt). Du hast geschrieben:

In der homematicwired.conf steht:

Daher habe ich es auf FALSE gelassen (an dem Parameter hatte ich noch nicht rumgespielt )
Also ist jetzt FALSE für UART oder TRUE?

Gruß,
shizzleslick

sathya · January 5, 2017, 1:22pm

Ich hab’s im Post vertauscht: “true” für USB-Geräte und “false” für UART ist korrekt.

shizzleslick · January 5, 2017, 1:26pm

Danke @sathya,

Ich löte mir dann mal die Tage einen neuen Adapter und melde mich

Gruß,
shizzleslick

shizzleslick · January 6, 2017, 3:50pm

So, Modul ist gelötet.

Nun bekomme ich diese Meldungen

01/06/17 16:46:39.249 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 0E20AC26008EF40F202C40242022A14A8B6A0BF1
01/06/17 16:46:41.209 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 607A00C6622402C0
01/06/17 16:46:41.272 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 607A00C6622402C0
01/06/17 16:46:41.335 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 607A00C6622402C0
01/06/17 16:46:42.761 Debug: SSDP server: Binding to address: 192.168.0.66
01/06/17 16:46:42.761 Debug: Searching for SSDP devices ...
01/06/17 16:46:44.918 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 0E20AC260087EC0F202C40242022A14A8B6A0BF1
01/06/17 16:46:46.818 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 607A00C6622403A2
01/06/17 16:46:46.879 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 607A00C6622403A2
01/06/17 16:46:46.945 Module HomeMatic Wired: HomeMatic Wired packet has unknown type: 607A00C6622403A2
01/06/17 16:46:48.979 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34448 accepted. Client number: 115
01/06/17 16:46:48.980 RPC Server (Port 2001): Info: RPC server client id for client number 115 is: 50
01/06/17 16:46:48.980 RPC Server (Port 2001): Listening for incoming packets from client number 115.
01/06/17 16:46:48.980 RPC Server (Port 2001): Debug: Packet received: 42696E000000002B00000004696E697400000001000000030000001762696E6172793A2F2F3132372E302E302E313A39313233
01/06/17 16:46:48.980 RPC Server (Port 2001): Info: Client number 115 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
01/06/17 16:46:48.981 Info: Removing server "binary://127.0.0.1".
01/06/17 16:46:48.981 RPC Server (Port 2001): Response:
(void)
01/06/17 16:46:48.981 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
01/06/17 16:46:48.984 RPC Server (Port 2001): Info: Connection to client number 115 closed (3).
01/06/17 16:46:48.988 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34450 accepted. Client number: 116
01/06/17 16:46:48.988 RPC Server (Port 2001): Info: RPC server client id for client number 116 is: 51
01/06/17 16:46:48.989 RPC Server (Port 2001): Listening for incoming packets from client number 116.
01/06/17 16:46:48.989 RPC Server (Port 2001): Debug: Packet received: 42696E000000002D000000146765744465766963654465736372697074696F6E000000010000000300000009426964436F532D5246
01/06/17 16:46:48.989 RPC Server (Port 2001): Info: Client number 116 is calling RPC method: getDeviceDescription (2) Parameters:
(String) BidCoS-RF
01/06/17 16:46:48.989 RPC Server (Port 2001): Response:
(Struct length=2)
{
  [FIRMWARE]
  {
    (String) 0.6.7-1545
  }
  [TYPE]
  {
    (String) Homegear
  }
}
01/06/17 16:46:48.989 RPC Server (Port 2001): Response binary:
42696E010000003E0000010100000002000000084649524D57415245000000030000000A302E362E372D3135343500000004545950450000000300000008486F6D6567656172
01/06/17 16:46:48.992 RPC Server (Port 2001): Info: Connection to client number 116 closed (3).
01/06/17 16:46:48.997 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34452 accepted. Client number: 117
01/06/17 16:46:48.997 RPC Server (Port 2001): Info: RPC server client id for client number 117 is: 52
01/06/17 16:46:48.998 RPC Server (Port 2001): Listening for incoming packets from client number 117.
01/06/17 16:46:48.998 RPC Server (Port 2001): Debug: Packet received: 42696E00000000190000000C676574416C6C56616C756573000000010000000201
01/06/17 16:46:48.998 RPC Server (Port 2001): Info: Client number 117 is calling RPC method: getAllValues (2) Parameters:
(Boolean) 1
01/06/17 16:46:49.014 RPC Server (Port 2001): Response:
(Array length=0)
{
}
01/06/17 16:46:49.014 RPC Server (Port 2001): Response binary:
42696E01000000080000010000000000
01/06/17 16:46:49.017 RPC Server (Port 2001): Info: Connection to client number 117 closed (3).
01/06/17 16:46:49.020 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34454 accepted. Client number: 118
01/06/17 16:46:49.021 RPC Server (Port 2001): Info: RPC server client id for client number 118 is: 53
01/06/17 16:46:49.021 RPC Server (Port 2001): Listening for incoming packets from client number 118.
01/06/17 16:46:49.022 RPC Server (Port 2001): Debug: Packet received: 42696E000000001D00000015676574416C6C53797374656D5661726961626C657300000000
01/06/17 16:46:49.022 RPC Server (Port 2001): Info: Client number 118 is calling RPC method: getAllSystemVariables (2) Parameters:
01/06/17 16:46:49.022 RPC Server (Port 2001): Response:
(Struct length=0)
{
}
01/06/17 16:46:49.022 RPC Server (Port 2001): Response binary:
42696E01000000080000010100000000
01/06/17 16:46:49.025 RPC Server (Port 2001): Info: Connection to client number 118 closed (3).
01/06/17 16:46:49.030 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34456 accepted. Client number: 119
01/06/17 16:46:49.030 RPC Server (Port 2001): Info: RPC server client id for client number 119 is: 54
01/06/17 16:46:49.031 RPC Server (Port 2001): Listening for incoming packets from client number 119.
01/06/17 16:46:49.031 RPC Server (Port 2001): Debug: Packet received: 42696E000000003B00000004696E697400000002000000030000001762696E6172793A2F2F3132372E302E302E313A393132330000000300000008486F6D6567656172
01/06/17 16:46:49.031 RPC Server (Port 2001): Info: Client number 119 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
(String) Homegear
01/06/17 16:46:49.032 Info: Adding server "binary://127.0.0.1".
01/06/17 16:46:49.032 RPC Server (Port 2001): Response:
(void)
01/06/17 16:46:49.032 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
01/06/17 16:46:49.033 Info: Calling init methods on server "binary://127.0.0.1".
01/06/17 16:46:49.035 RPC Server (Port 2001): Info: Connection to client number 119 closed (3).
01/06/17 16:46:49.533 RPC client: Info: Calling RPC method "system.listMethods" on server binary://127.0.0.1.
01/06/17 16:46:49.533 RPC client: Parameters:
01/06/17 16:46:49.533 Debug: Calling getFileDescriptor...
01/06/17 16:46:49.533 Debug: Connecting to host 127.0.0.1 on port 9123...
01/06/17 16:46:49.534 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 120
01/06/17 16:46:49.534 RPC client: Debug: Sending packet: 42696E000000001A0000001273797374656D2E6C6973744D6574686F647300000000
01/06/17 16:46:49.536 RPC client: Debug: Packet received: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
01/06/17 16:46:49.536 RPC client: Debug: Received packet from server 127.0.0.1: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
01/06/17 16:46:49.536 RPC client: Response was:
(Array length=2)
{
  (String) system.multicall
  (String) event
}
01/06/17 16:46:49.537 Debug: Adding method system.multicall
01/06/17 16:46:49.537 Debug: Adding method event
01/06/17 16:46:56.814 UPnP Server: Debug: Sending notify packets.

@sathya, nen kleinen Tipp vielleicht?

Gruß,
shizzleslick

shizzleslick · January 6, 2017, 4:10pm

Das ist vielleicht aussagekräftiger:

01/06/17 16:58:00.716 Debug (HM-RS485): Packet FDFFFFFFFFDA00005A2D064B0000FA1124 enters raisePacketReceived.
01/06/17 16:58:00.716 Debug (HM-RS485): Packet FDFFFFFFFFDA00005A2D064B0000FA1124 is now passed to the EventHandler.
01/06/17 16:58:00.716 HomeMatic Wired packet received: FDFFFFFFFFDA00005A2D064B0000FA1124
01/06/17 16:58:00.716 Debug (HM-RS485): Packet processing of packet FDFFFFFFFFDA00005A2D064B0000FA1124 took 0 ms.
01/06/17 16:58:00.738 Debug (HM-RS485): Packet FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84 enters raisePacketReceived.
01/06/17 16:58:00.738 Debug (HM-RS485): Packet FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84 is now passed to the EventHandler.
01/06/17 16:58:00.738 HomeMatic Wired packet received: FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84
01/06/17 16:58:00.738 Module HomeMatic Wired: Info: New device detected on bus.
01/06/17 16:58:00.738 Debug (HM-RS485): Packet processing of packet FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84 took 0 ms.
01/06/17 16:58:00.864 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: Waiting for RS485 bus to become free... (Packet: FD00005A2D1C0000000106520000108360)
01/06/17 16:58:00.965 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is free now. Waiting randomly for 51ms... (Packet: FD00005A2D1C0000000106520000108360)
01/06/17 16:58:01.016 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is still free... sending... (Packet: FD00005A2D1C0000000106520000108360)
01/06/17 16:58:01.017 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1C0000000106520000108360)
01/06/17 16:58:01.017 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1C0000000106520000108360
01/06/17 16:58:01.126 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1C0000000106520000108360)
01/06/17 16:58:01.126 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1C0000000106520000108360
01/06/17 16:58:01.236 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1C0000000106520000108360)
01/06/17 16:58:01.236 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1C0000000106520000108360
01/06/17 16:58:01.346 Module HomeMatic Wired: Error: HomeMatic Wired Central: Could not pair device with address 0x00005A2D. Could not read master config from EEPROM.
01/06/17 16:58:01.346 RPC client: Info: Calling RPC method "system.multicall" on server 127.0.0.1.
01/06/17 16:58:01.346 RPC client: Parameters:
(Array length=1)
{
  (Struct length=2)
  {
    [methodName]
    {
      (String) event
    }
    [params]
    {
      (Array length=4)
      {
        (String) Homegear
        (String) heq0240793
        (String)
        (Struct length=2)
        {
          [CODE]
          {
            (Integer) 1
          }
          [TYPE]
          {
            (Integer) 1
          }
        }
      }
    }
  }
}
01/06/17 16:58:01.347 Debug: Calling getFileDescriptor...
01/06/17 16:58:01.347 Debug: Connecting to host 127.0.0.1 on port 9123...
01/06/17 16:58:01.348 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 36
01/06/17 16:58:01.348 RPC client: Debug: Sending packet: 42696E00000000A70000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D7300000100000000040000000300000008486F6D6567656172000000030000000A686571303234303739330000000300000000000001010000000200000004434F4445000000010000000100000004545950450000000100000001
Warning: Connection to client number 36 closed (3).
01/06/17 16:58:01.360 Debug: Calling getFileDescriptor...
01/06/17 16:58:01.361 Debug: Connecting to host 127.0.0.1 on port 9123...
01/06/17 16:58:01.361 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 37
01/06/17 16:58:01.362 RPC client: Debug: Sending packet: 42696E00000000A70000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D7300000100000000040000000300000008486F6D6567656172000000030000000A686571303234303739330000000300000000000001010000000200000004434F4445000000010000000100000004545950450000000100000001
Warning: Connection to client number 37 closed (3).
01/06/17 16:58:01.369 Debug: Calling getFileDescriptor...
01/06/17 16:58:01.370 Debug: Connecting to host 127.0.0.1 on port 9123...
01/06/17 16:58:01.370 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 38
01/06/17 16:58:01.371 RPC client: Debug: Sending packet: 42696E00000000A70000001073797374656D2E6D756C746963616C6C00000001000001000000000100000101000000020000000A6D6574686F644E616D6500000003000000056576656E7400000006706172616D7300000100000000040000000300000008486F6D6567656172000000030000000A686571303234303739330000000300000000000001010000000200000004434F4445000000010000000100000004545950450000000100000001
Warning: Connection to client number 38 closed (3).
Removing server "Homegear". Server has to send "init" again.
01/06/17 16:58:02.636 Debug (HM-RS485): Packet FD000000015E00005A2D06690C00009540 enters raisePacketReceived.
01/06/17 16:58:02.636 Debug (HM-RS485): Packet FD000000015E00005A2D06690C00009540 is now passed to the EventHandler.
01/06/17 16:58:02.636 HomeMatic Wired packet received: FD000000015E00005A2D06690C00009540
01/06/17 16:58:02.636 Debug (HM-RS485): Packet processing of packet FD000000015E00005A2D06690C00009540 took 0 ms.
01/06/17 16:58:02.700 Debug (HM-RS485): Packet FD000000015E00005A2D06690C00009540 enters raisePacketReceived.
01/06/17 16:58:02.700 Debug (HM-RS485): Packet FD000000015E00005A2D06690C00009540 is now passed to the EventHandler.
01/06/17 16:58:02.699 HomeMatic Wired packet received: FD000000015E00005A2D06690C00009540
01/06/17 16:58:02.700 Debug (HM-RS485): Packet processing of packet FD000000015E00005A2D06690C00009540 took 0 ms.
01/06/17 16:58:02.767 Debug (HM-RS485): Packet FD000000015E00005A2D06690C00009540 enters raisePacketReceived.
01/06/17 16:58:02.767 Debug (HM-RS485): Packet FD000000015E00005A2D06690C00009540 is now passed to the EventHandler.
01/06/17 16:58:02.767 HomeMatic Wired packet received: FD000000015E00005A2D06690C00009540
01/06/17 16:58:02.767 Debug (HM-RS485): Packet processing of packet FD000000015E00005A2D06690C00009540 took 0 ms.
01/06/17 16:58:05.337 UPnP Server: Debug: Discovery packet received from 239.255.255.250:1900
01/06/17 16:58:05.357 Debug: Sleeping 341ms before sending response.
01/06/17 16:58:05.699 UPnP Server: Debug: Sending discovery response packets to 239.255.255.250 on port 1900
01/06/17 16:58:05.799 UPnP Server: Debug: Sending notify packets.
01/06/17 16:58:07.864 Debug (HM-RS485): Packet FDFFFFFFFFDA00005A2D064B0000FC7E512C enters raisePacketReceived.
01/06/17 16:58:07.864 Debug (HM-RS485): Packet FDFFFFFFFFDA00005A2D064B0000FC7E512C is now passed to the EventHandler.
01/06/17 16:58:07.863 HomeMatic Wired packet received: FDFFFFFFFFDA00005A2D064B0000FC7E512C
01/06/17 16:58:07.864 Debug (HM-RS485): Packet processing of packet FDFFFFFFFFDA00005A2D064B0000FC7E512C took 0 ms.
01/06/17 16:58:07.885 Debug (HM-RS485): Packet FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84 enters raisePacketReceived.
01/06/17 16:58:07.886 Debug (HM-RS485): Packet FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84 is now passed to the EventHandler.
01/06/17 16:58:07.885 HomeMatic Wired packet received: FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84
01/06/17 16:58:07.886 Module HomeMatic Wired: Info: New device detected on bus.01/06/17 16:58:07.886
 Debug (HM-RS485): Packet processing of packet FDFFFFFFFFDC00005A2D1241001200030668657130323430373933ED84 took 1 ms.
01/06/17 16:58:08.008 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: Waiting for RS485 bus to become free... (Packet: FD00005A2D1E000000010652000010FA68)
01/06/17 16:58:08.109 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is free now. Waiting randomly for 8ms... (Packet: FD00005A2D1E000000010652000010FA68)
01/06/17 16:58:08.117 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is still free... sending... (Packet: FD00005A2D1E000000010652000010FA68)
01/06/17 16:58:08.117 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1E000000010652000010FA68)
01/06/17 16:58:08.117 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1E000000010652000010FA68
01/06/17 16:58:08.227 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1E000000010652000010FA68)
01/06/17 16:58:08.227 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1E000000010652000010FA68
01/06/17 16:58:08.337 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD00005A2D1E000000010652000010FA68)
01/06/17 16:58:08.337 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD00005A2D1E000000010652000010FA68
01/06/17 16:58:08.446 Module HomeMatic Wired: Error: HomeMatic Wired Central: Could not pair device with address 0x00005A2D. Could not read master config from EEPROM.
01/06/17 16:58:09.849 Debug (HM-RS485): Packet FD000000015E00005A2D06690CC8004DCA enters raisePacketReceived.
01/06/17 16:58:09.849 Debug (HM-RS485): Packet FD000000015E00005A2D06690CC8004DCA is now passed to the EventHandler.
01/06/17 16:58:09.849 HomeMatic Wired packet received: FD000000015E00005A2D06690CC8004DCA
01/06/17 16:58:09.849 Debug (HM-RS485): Packet processing of packet FD000000015E00005A2D06690CC8004DCA took 0 ms.
01/06/17 16:58:09.916 Debug (HM-RS485): Packet FD000000015E00005A2D06690CC8004DCA enters raisePacketReceived.
01/06/17 16:58:09.916 Debug (HM-RS485): Packet FD000000015E00005A2D06690CC8004DCA is now passed to the EventHandler.
01/06/17 16:58:09.916 HomeMatic Wired packet received: FD000000015E00005A2D06690CC8004DCA
01/06/17 16:58:09.917 Debug (HM-RS485): Packet processing of packet FD000000015E00005A2D06690CC8004DCA took 0 ms.
01/06/17 16:58:09.978 Debug (HM-RS485): Packet FD000000015E00005A2D06690CC8004DCA enters raisePacketReceived.
01/06/17 16:58:09.978 Debug (HM-RS485): Packet FD000000015E00005A2D06690CC8004DCA is now passed to the EventHandler.
01/06/17 16:58:09.978 HomeMatic Wired packet received: FD000000015E00005A2D06690CC8004DCA
01/06/17 16:58:09.978 Debug (HM-RS485): Packet processing of packet FD000000015E00005A2D06690CC8004DCA took 0 ms.
01/06/17 16:58:15.545 Debug: SSDP server: Binding to address: 192.168.0.66
01/06/17 16:58:15.546 Debug: Searching for SSDP devices ...
01/06/17 16:58:32.794 RPC Server (Port 2001): Debug: Joining read thread of client 5
01/06/17 16:58:32.794 RPC Server (Port 2001): Debug: Client 5 removed.
01/06/17 16:58:32.794 RPC Server (Port 2001): Debug: Joining read thread of client 6
01/06/17 16:58:32.794 RPC Server (Port 2001): Debug: Client 6 removed.
01/06/17 16:58:32.794 RPC Server (Port 2001): Debug: Joining read thread of client 7
01/06/17 16:58:32.794 RPC Server (Port 2001): Debug: Client 7 removed.
01/06/17 16:58:32.795 RPC Server (Port 2001): Debug: Joining read thread of client 8
01/06/17 16:58:32.795 RPC Server (Port 2001): Debug: Client 8 removed.
01/06/17 16:58:32.795 RPC Server (Port 2001): Debug: Joining read thread of client 9
01/06/17 16:58:32.795 RPC Server (Port 2001): Debug: Client 9 removed.
01/06/17 16:58:41.259 Debug: SSDP server: Binding to address: 192.168.0.66
01/06/17 16:58:41.259 Debug: Searching for SSDP devices ...
01/06/17 16:58:49.764 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34596 accepted. Client number: 41
01/06/17 16:58:49.765 RPC Server (Port 2001): Info: RPC server client id for client number 41 is: 10
01/06/17 16:58:49.766 RPC Server (Port 2001): Listening for incoming packets from client number 41.
01/06/17 16:58:49.766 RPC Server (Port 2001): Debug: Packet received: 42696E000000002B00000004696E697400000001000000030000001762696E6172793A2F2F3132372E302E302E313A39313233
01/06/17 16:58:49.766 RPC Server (Port 2001): Info: Client number 41 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
01/06/17 16:58:49.766 Info: Removing server "binary://127.0.0.1".
01/06/17 16:58:49.767 RPC Server (Port 2001): Response:
(void)
01/06/17 16:58:49.767 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
01/06/17 16:58:49.770 RPC Server (Port 2001): Info: Connection to client number 41 closed (3).
01/06/17 16:58:49.773 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34598 accepted. Client number: 42
01/06/17 16:58:49.774 RPC Server (Port 2001): Info: RPC server client id for client number 42 is: 11
01/06/17 16:58:49.775 RPC Server (Port 2001): Listening for incoming packets from client number 42.
01/06/17 16:58:49.775 RPC Server (Port 2001): Debug: Packet received: 42696E000000002D000000146765744465766963654465736372697074696F6E000000010000000300000009426964436F532D5246
01/06/17 16:58:49.775 RPC Server (Port 2001): Info: Client number 42 is calling RPC method: getDeviceDescription (2) Parameters:
(String) BidCoS-RF
01/06/17 16:58:49.775 RPC Server (Port 2001): Response:
(Struct length=2)
{
  [FIRMWARE]
  {
    (String) 0.6.7-1545
  }
  [TYPE]
  {
    (String) Homegear
  }
}
01/06/17 16:58:49.776 RPC Server (Port 2001): Response binary:
42696E010000003E0000010100000002000000084649524D57415245000000030000000A302E362E372D3135343500000004545950450000000300000008486F6D6567656172
01/06/17 16:58:49.778 RPC Server (Port 2001): Info: Connection to client number 42 closed (3).
01/06/17 16:58:49.783 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34600 accepted. Client number: 43
01/06/17 16:58:49.784 RPC Server (Port 2001): Info: RPC server client id for client number 43 is: 12
01/06/17 16:58:49.785 RPC Server (Port 2001): Listening for incoming packets from client number 43.
01/06/17 16:58:49.785 RPC Server (Port 2001): Debug: Packet received: 42696E00000000190000000C676574416C6C56616C756573000000010000000201
01/06/17 16:58:49.785 RPC Server (Port 2001): Info: Client number 43 is calling RPC method: getAllValues (2) Parameters:
(Boolean) 1
01/06/17 16:58:49.801 RPC Server (Port 2001): Response:
(Array length=0)
{
}
01/06/17 16:58:49.801 RPC Server (Port 2001): Response binary:
42696E01000000080000010000000000
01/06/17 16:58:49.804 RPC Server (Port 2001): Info: Connection to client number 43 closed (3).
01/06/17 16:58:49.807 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34602 accepted. Client number: 44
01/06/17 16:58:49.808 RPC Server (Port 2001): Info: RPC server client id for client number 44 is: 13
01/06/17 16:58:49.809 RPC Server (Port 2001): Listening for incoming packets from client number 44.
01/06/17 16:58:49.809 RPC Server (Port 2001): Debug: Packet received: 42696E000000001D00000015676574416C6C53797374656D5661726961626C657300000000
01/06/17 16:58:49.809 RPC Server (Port 2001): Info: Client number 44 is calling RPC method: getAllSystemVariables (2) Parameters:
01/06/17 16:58:49.809 RPC Server (Port 2001): Response:
(Struct length=0)
{
}
01/06/17 16:58:49.809 RPC Server (Port 2001): Response binary:
42696E01000000080000010100000000
01/06/17 16:58:49.812 RPC Server (Port 2001): Info: Connection to client number 44 closed (3).
01/06/17 16:58:49.817 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34604 accepted. Client number: 45
01/06/17 16:58:49.817 RPC Server (Port 2001): Info: RPC server client id for client number 45 is: 14
01/06/17 16:58:49.818 RPC Server (Port 2001): Listening for incoming packets from client number 45.
01/06/17 16:58:49.818 RPC Server (Port 2001): Debug: Packet received: 42696E000000003B00000004696E697400000002000000030000001762696E6172793A2F2F3132372E302E302E313A393132330000000300000008486F6D6567656172
01/06/17 16:58:49.818 RPC Server (Port 2001): Info: Client number 45 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
(String) Homegear
01/06/17 16:58:49.819 Info: Adding server "binary://127.0.0.1".
01/06/17 16:58:49.819 RPC Server (Port 2001): Response:
(void)
01/06/17 16:58:49.819 RPC Server (Port 2001): Response binary:
01/06/17 16:58:49.819 Info: Calling init methods on server "binary://127.0.0.1".
42696E01000000080000000300000000
01/06/17 16:58:49.822 RPC Server (Port 2001): Info: Connection to client number 45 closed (3).
01/06/17 16:58:50.320 RPC client: Info: Calling RPC method "system.listMethods" on server binary://127.0.0.1.
01/06/17 16:58:50.320 RPC client: Parameters:
01/06/17 16:58:50.320 Debug: Calling getFileDescriptor...
01/06/17 16:58:50.320 Debug: Connecting to host 127.0.0.1 on port 9123...
01/06/17 16:58:50.321 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 46
01/06/17 16:58:50.321 RPC client: Debug: Sending packet: 42696E000000001A0000001273797374656D2E6C6973744D6574686F647300000000
01/06/17 16:58:50.322 RPC client: Debug: Packet received: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
01/06/17 16:58:50.323 RPC client: Debug: Received packet from server 127.0.0.1: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
01/06/17 16:58:50.324 RPC client: Response was:
(Array length=2)
{
  (String) system.multicall
  (String) event
}
01/06/17 16:58:50.324 Debug: Adding method system.multicall
01/06/17 16:58:50.324 Debug: Adding method event
01/06/17 16:58:55.886 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is still free... sending... (Packet: FDFFFFFFFF9800000001037A6D72)
01/06/17 16:58:55.886 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FDFFFFFFFF9800000001037A6D72)
01/06/17 16:58:55.886 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FDFFFFFFFF9800000001037A6D72
01/06/17 16:58:56.195 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is still free... sending... (Packet: FDFFFFFFFF9A00000001037AC10E)
01/06/17 16:58:56.196 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FDFFFFFFFF9A00000001037AC10E)
01/06/17 16:58:56.196 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FDFFFFFFFF9A00000001037AC10E
01/06/17 16:58:56.505 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD0000000003026C76)
01/06/17 16:58:56.506 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD0000000003026C76
01/06/17 16:58:56.526 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD0000000003026C76)
01/06/17 16:58:56.526 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD0000000003026C76
01/06/17 16:58:56.547 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FD0000000003026C76)
01/06/17 16:58:56.547 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FD0000000003026C76
01/06/17 16:58:56.598 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: Waiting for RS485 bus to become free... (Packet: FDFFFFFFFF9C00000001035A05CC)
01/06/17 16:58:56.799 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is free now. Waiting randomly for 65ms... (Packet: FDFFFFFFFF9C00000001035A05CC)
01/06/17 16:58:56.864 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is still free... sending... (Packet: FDFFFFFFFF9C00000001035A05CC)
01/06/17 16:58:56.865 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FDFFFFFFFF9C00000001035A05CC)
01/06/17 16:58:56.865 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FDFFFFFFFF9C00000001035A05CC
01/06/17 16:58:57.174 Module HomeMatic Wired: Debug: HomeMatic Wired Device 0x6: RS485 bus is still free... sending... (Packet: FDFFFFFFFF9E00000001035AA9B0)
01/06/17 16:58:57.175 Module HomeMatic Wired: RS485 Module "HM-RS485": Debug: RS485 device: Got lock for sending... (Packet: FDFFFFFFFF9E00000001035AA9B0)
01/06/17 16:58:57.175 Module HomeMatic Wired: RS485 Module "HM-RS485": Info: Sending: FDFFFFFFFF9E00000001035AA9B0
01/06/17 16:58:57.484 Module HomeMatic Wired: Info: Search completed. Found 0 devices.
01/06/17 16:59:05.405 UPnP Server: Debug: Sending notify packets.
01/06/17 16:59:06.975 Debug: SSDP server: Binding to address: 192.168.0.66
01/06/17 16:59:06.975 Debug: Searching for SSDP devices ...
01/06/17 16:59:32.692 Debug: SSDP server: Binding to address: 192.168.0.66
01/06/17 16:59:32.692 Debug: Searching for SSDP devices ...
01/06/17 16:59:32.862 RPC Server (Port 2001): Debug: Joining read thread of client 10
01/06/17 16:59:32.862 RPC Server (Port 2001): Debug: Client 10 removed.
01/06/17 16:59:32.862 RPC Server (Port 2001): Debug: Joining read thread of client 11
01/06/17 16:59:32.862 RPC Server (Port 2001): Debug: Client 11 removed.
01/06/17 16:59:32.862 RPC Server (Port 2001): Debug: Joining read thread of client 12
01/06/17 16:59:32.862 RPC Server (Port 2001): Debug: Client 12 removed.
01/06/17 16:59:32.862 RPC Server (Port 2001): Debug: Joining read thread of client 13
01/06/17 16:59:32.863 RPC Server (Port 2001): Debug: Client 13 removed.
01/06/17 16:59:32.863 RPC Server (Port 2001): Debug: Joining read thread of client 14
01/06/17 16:59:32.863 RPC Server (Port 2001): Debug: Client 14 removed.
01/06/17 16:59:49.830 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34608 accepted. Client number: 49
01/06/17 16:59:49.831 RPC Server (Port 2001): Info: RPC server client id for client number 49 is: 15
01/06/17 16:59:49.832 RPC Server (Port 2001): Listening for incoming packets from client number 49.
01/06/17 16:59:49.832 RPC Server (Port 2001): Debug: Packet received: 42696E000000002B00000004696E697400000001000000030000001762696E6172793A2F2F3132372E302E302E313A39313233
01/06/17 16:59:49.832 RPC Server (Port 2001): Info: Client number 49 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
01/06/17 16:59:49.832 Info: Removing server "binary://127.0.0.1".
01/06/17 16:59:49.832 RPC Server (Port 2001): Response:
(void)
01/06/17 16:59:49.833 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
01/06/17 16:59:49.835 RPC Server (Port 2001): Info: Connection to client number 49 closed (3).
01/06/17 16:59:49.839 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34610 accepted. Client number: 50
01/06/17 16:59:49.840 RPC Server (Port 2001): Info: RPC server client id for client number 50 is: 16
01/06/17 16:59:49.840 RPC Server (Port 2001): Listening for incoming packets from client number 50.
01/06/17 16:59:49.841 RPC Server (Port 2001): Debug: Packet received: 42696E000000002D000000146765744465766963654465736372697074696F6E000000010000000300000009426964436F532D5246
01/06/17 16:59:49.841 RPC Server (Port 2001): Info: Client number 50 is calling RPC method: getDeviceDescription (2) Parameters:
(String) BidCoS-RF
01/06/17 16:59:49.841 RPC Server (Port 2001): Response:
(Struct length=2)
{
  [FIRMWARE]
  {
    (String) 0.6.7-1545
  }
  [TYPE]
  {
    (String) Homegear
  }
}
01/06/17 16:59:49.841 RPC Server (Port 2001): Response binary:
42696E010000003E0000010100000002000000084649524D57415245000000030000000A302E362E372D3135343500000004545950450000000300000008486F6D6567656172
01/06/17 16:59:49.846 RPC Server (Port 2001): Info: Connection to client number 50 closed (3).
01/06/17 16:59:49.850 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34612 accepted. Client number: 51
01/06/17 16:59:49.851 RPC Server (Port 2001): Info: RPC server client id for client number 51 is: 17
01/06/17 16:59:49.851 RPC Server (Port 2001): Listening for incoming packets from client number 51.
01/06/17 16:59:49.852 RPC Server (Port 2001): Debug: Packet received: 42696E00000000190000000C676574416C6C56616C756573000000010000000201
01/06/17 16:59:49.852 RPC Server (Port 2001): Info: Client number 51 is calling RPC method: getAllValues (2) Parameters:
(Boolean) 1
01/06/17 16:59:49.867 RPC Server (Port 2001): Response:
(Array length=0)
{
}
01/06/17 16:59:49.867 RPC Server (Port 2001): Response binary:
42696E01000000080000010000000000
01/06/17 16:59:49.870 RPC Server (Port 2001): Info: Connection to client number 51 closed (3).
01/06/17 16:59:49.873 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34614 accepted. Client number: 52
01/06/17 16:59:49.874 RPC Server (Port 2001): Info: RPC server client id for client number 52 is: 18
01/06/17 16:59:49.875 RPC Server (Port 2001): Listening for incoming packets from client number 52.
01/06/17 16:59:49.875 RPC Server (Port 2001): Debug: Packet received: 42696E000000001D00000015676574416C6C53797374656D5661726961626C657300000000
01/06/17 16:59:49.875 RPC Server (Port 2001): Info: Client number 52 is calling RPC method: getAllSystemVariables (2) Parameters:
01/06/17 16:59:49.875 RPC Server (Port 2001): Response:
(Struct length=0)
{
}
01/06/17 16:59:49.875 RPC Server (Port 2001): Response binary:
42696E01000000080000010100000000
01/06/17 16:59:49.878 RPC Server (Port 2001): Info: Connection to client number 52 closed (3).
01/06/17 16:59:49.882 RPC Server (Port 2001): Info: Connection from 127.0.0.1:34616 accepted. Client number: 53
01/06/17 16:59:49.883 RPC Server (Port 2001): Info: RPC server client id for client number 53 is: 19
01/06/17 16:59:49.883 RPC Server (Port 2001): Listening for incoming packets from client number 53.
01/06/17 16:59:49.884 RPC Server (Port 2001): Debug: Packet received: 42696E000000003B00000004696E697400000002000000030000001762696E6172793A2F2F3132372E302E302E313A393132330000000300000008486F6D6567656172
01/06/17 16:59:49.884 RPC Server (Port 2001): Info: Client number 53 is calling RPC method: init (2) Parameters:
(String) binary://127.0.0.1:9123
(String) Homegear
01/06/17 16:59:49.884 Info: Adding server "binary://127.0.0.1".
01/06/17 16:59:49.885 RPC Server (Port 2001): Response:
(void)
01/06/17 16:59:49.885 Info: Calling init methods on server "binary://127.0.0.1".
01/06/17 16:59:49.885 RPC Server (Port 2001): Response binary:
42696E01000000080000000300000000
01/06/17 16:59:49.887 RPC Server (Port 2001): Info: Connection to client number 53 closed (3).
01/06/17 16:59:50.385 RPC client: Info: Calling RPC method "system.listMethods" on server binary://127.0.0.1.
01/06/17 16:59:50.385 RPC client: Parameters:
01/06/17 16:59:50.385 Debug: Calling getFileDescriptor...
01/06/17 16:59:50.385 Debug: Connecting to host 127.0.0.1 on port 9123...
01/06/17 16:59:50.386 Debug: Connected to host 127.0.0.1 on port 9123. Client number is: 54
01/06/17 16:59:50.386 RPC client: Debug: Sending packet: 42696E000000001A0000001273797374656D2E6C6973744D6574686F647300000000
01/06/17 16:59:50.388 RPC client: Debug: Packet received: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
01/06/17 16:59:50.388 RPC client: Debug: Received packet from server 127.0.0.1: 42696E010000002D0000010000000002000000030000001073797374656D2E6D756C746963616C6C00000003000000056576656E74
01/06/17 16:59:50.388 RPC client: Response was:
(Array length=2)
{
  (String) system.multicall
  (String) event
}

Sagt zwar er hätte ein “new device” gefunden (ist mir beim anderen Modul nicht aufgefallen), kann aber trotzdem das EEPROM nicht lesen.

Mal ne dumme Frage, kann es nicht sein, daß das EEPROM nicht ausgelesen werden kann, weil es an eine andere CCU angelernt ist?

Gruß,
shizzleslick

sathya · January 6, 2017, 4:41pm

Hallo @shizzleslick,

leider gleiches Problem, wie vorher… Es scheinen keine von Homegear gesendeten Pakete von den Geräten empfangen zu werden.

Das spielt hier keine Rolle. Die Zentralenadresse ist immer gleich. Es können entsprechend auch an eine andere Zentrale angelernte Geräte ohne Zurücksetzen in den Werkszustand angelernt werden.

Ich werde nächste Woche auch selbst noch einmal eines meiner Module testen. Nicht, dass sich ein Fehler in den Quelltext eingeschlichen hat - wobei ich mich nicht entsinnen kann, an dieser Stelle irgendetwas geändert zu haben.

Nach wie vor steht auch mein Angebot, dein Modul einmal bei mir zu testen ;-).

Viele Grüße

Sathya

shizzleslick · January 6, 2017, 5:18pm

Hallo @sathya,

Danke für das Angebot, schick mir einfach Deine Adresse per PN oder wie auch immer, dann schicke ich Dir gerne eines.

Noch eine Frage. Müssen die wired-Komponenten irgendeine besondere Firmware haben? Eventuell kann homegear sie nicht lesen, weil die zu alt ist? Habe die 3.04 Firmware auf den 12/7 Aktoren.
Ich hoffe mal nicht, daß ich mir meinen Rpi3 “zersägt” habe
Ich werde parallel mal einen Bpi bemühen, kann aber etwas dauern.

Gruß,
shizzleslick

sathya · January 6, 2017, 7:02pm

Hallo @shizzleslick,

Nein. Die hat sich auch seit Ewigkeiten nicht geändert.

Viele Grüße

Sathya

shizzleslick · January 17, 2017, 8:42am

Hallo,

Ich möchte mich vorab bei allen hier für die Hilfe und Rat/Tat bedanken. Ich konnte gestern mein selbstgelötetes Modul zum Laufen bringen (die gekauften laufen wahrscheinlich auch).
Es lag weder an homegear noch an den Modulen und/oder Verkabelung.

Durch das ewige Probieren, Ändern, neu Installieren und “rumpfuschen” hatte ich mir anscheinend alles verstellt

Gestern habe ich (nachdem ich ein Update auf homegear 0.6.13-864 und Kernel 4.4.43 durchgeführt hatte), alles “from scratch” neu eingerichtet.

Was ich gelernt habe:

RPi 3 hat ein großes Problem mit seriellen Schnittstellen und dem Bluetooth-Modul.

Hier die Einstellungen seitens des Jessies:

# cat /boot/config.txt
arm_freq=900
sdram_freq=450
over_voltage=2
enable_uart=1
#force_turbo=1
dtparam=spi=on
dtparam=i2c_arm=on
dtoverlay=pi3-miniuart-bt

Der letzte Eintrag ist wichtig, da standardmäßig das Bluetooth-Modul den UART belegt. Mit dem Eintrag wird das BT-Modul auf den mini-UART “verschoben”

# cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 kgdboc=ttyUSB0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline isolcpus=2,3 rootwait

Unter /etc/systemd/system/getty.target.wants sollte nur noch getty@tty1.service stehen.

Andere ttys z.B. mit:

# systemctl disable serial-getty@ttyAMA0.service

entfernen.

Nach diesen Änderungen muss der RPi neu gestartet werden.

Jetzt kann man die /etc/homegear/families/homematicwired.conf nach Belieben konfigurieren.
Als device muss nun aber /dev/ttyAMA0 benutzt werden, da das BT-Modul nun auf /dev/ttyS0 liegt.

Hier wird es halbwegs erklärt:
https://wiki.fhem.de/wiki/Raspberry_Pi_3:_GPIO-Port_Module_und_Bluetooth

Gruß,
shizzleslick

pmayer · January 17, 2017, 2:54pm

Super Erklärung. Sehr gut!!

@sathya, kannst du das vielleicht irgendwie in die Doku mit aufnehmen?

sathya · January 26, 2017, 3:41pm

https://doc.homegear.eu/data/homegear-homematicwired/configuration.html#config-rs485-serial