Hargassner NanoPk Modbus

[BenMarloe]

Liebe Gemeinde,
ich habe eine Hargassner Nano PK mit Modbus Modul.
Leider weiß ich nicht, wohin ich die Modbus Adressen zu richten habe und habe auch keine Anleitung dazu gefunden. Hargassner schweigt sich dazu bisher aus.
Kann mir jemand helfen?
Ich habe mal bei ein paar verdächtigen gesucht aber ohne Erfolg:

Code Auswählen Erweitern

define Afrit ModbusAttr 1 30 192.168.178.254:502 TCP
attr Afrit dev-h-defPoll 1
attr Afrit dev-h-defShowGet 1
attr Afrit obj-h10000-expr $val
attr Afrit obj-h10000-len 1
attr Afrit obj-h10000-reading Kessel10k
attr Afrit obj-h40000-expr $val/10
attr Afrit obj-h40000-len 1
attr Afrit obj-h40000-reading KesselTemp
attr Afrit obj-h40001-expr $val/10
attr Afrit obj-h40001-len 1
attr Afrit obj-h40001-reading KesselTem0
attr Afrit room Keller
attr Afrit verbose 5
#  CFGFN     
#  DEF        1 30 192.168.178.254:502 TCP
#  DeviceName 192.168.178.254:502
#  EXPECT    idle
#  FD        105
#  FUUID      68b9bc56-f33f-c6bc-f48a-188fae7f2a06b98a
#  IODev      Afrit
#  Interval  30
#  LASTOPEN  1757017853.26887
#  MODBUSID  1
#  MODE      master
#  MODULEVERSION Modbus 4.5.6 - 7.11.2023
#  NAME      Afrit
#  NOTIFYDEV  global
#  NR        331290
#  NTFY_ORDER 50-Afrit
#  PARTIAL   
#  PROTOCOL  TCP
#  STATE      opened
#  TCPConn    1
#  TYPE      ModbusAttr
#  devioLoglevel 3
#  devioNoSTATE 1
#  eventCount 116
#  nextOpenDelay 60
#  DICACHE:
#    131:
#      UNPACK   
#      EXPRS:
#      EXTRAS:
#      FNAMES:
#  QUEUE:
#  READ:
#    BUFFER   
#  READINGS:
#    2025-09-04 22:30:53  state          opened
#  REMEMBER:
#    lid        1
#    lname      Afrit
#    lrecv      1757018771.04917
#    lsend      1757018771.04087
#  UPDATECACHE:
#    h10000:
#      adr        10000
#      len        1
#      objCombi  h10000
#      reading    Kessel10k
#      span      1
#      type      h
#    h40000:
#      adr        40000
#      len        1
#      objCombi  h40000
#      reading    KesselTemp
#      span      1
#      type      h
#    h40001:
#      adr        40001
#      len        1
#      objCombi  h40001
#      reading    KesselTem0
#      span      1
#      type      h
#  defptr:
#    Afrit      1
#  gotReadings:
#  lastRead:
#
setstate Afrit opened
setstate Afrit 2025-09-04 22:30:53 state opened
Im Log sieht es auch nicht nach Erfolg aus:

Code Auswählen Erweitern

2025.09.04 22:53:10 4: Afrit: HandleResponse got response with error code 83 / 02, illegal data address
2025.09.04 22:53:10 4: Afrit: HandleResponse done, current frame / read buffer: 00f400000003018302, id 1, fCode 131, tid 244,
request: id 1, read fc 3 h10000, len 1, tid 244, master device Afrit, reading Kessel10k (getUpdate for Kessel10k len 1), queued 0.02 secs ago, sent 0.01 secs ago,
2025.09.04 22:53:10 5: Afrit: ResetExpect for HandleResponse from response to idle
2025.09.04 22:53:10 5: Afrit: StartQueueTimer called from HandleResponse sets internal timer to process queue in 0.000 seconds
2025.09.04 22:53:10 5: Afrit: DropFrame called from ReadFn - drop 00f400000003018302
2025.09.04 22:53:10 5: Afrit: readFn end buffer:  mode master, expect idle
2025.09.04 22:53:10 5: Afrit: ProcessRequestQueue called from Fhem internal timer as queue:Afrit, qlen 2, request: request: id 1, read fc 3 h40000, len 1, tid 212, master device Afrit, reading KesselTemp (getUpdate for KesselTemp len 1), queued 0.02 secs ago
2025.09.04 22:53:10 5: Afrit: checkDelays sendDelay, last send to same device was 0.013 secs ago, required delay is 0.1
2025.09.04 22:53:10 5: Afrit: checkDelays commDelay, last communication with same device was 0.005 secs ago, required delay is 0.1
2025.09.04 22:53:10 5: Afrit: checkDelays clientSwitchDelay is not relevant
2025.09.04 22:53:10 5: Afrit: checkDelays busDelayRead is not required
2025.09.04 22:53:10 4: Afrit: checkDelays found commDelay not over, set timer to try again in 0.095
2025.09.04 22:53:10 5: Afrit: ProcessRequestQueue called from Fhem internal timer as queue:Afrit, qlen 2, request: request: id 1, read fc 3 h40000, len 1, tid 212, master device Afrit, reading KesselTemp (getUpdate for KesselTemp len 1), queued 0.12 secs ago
2025.09.04 22:53:10 5: Afrit: checkDelays sendDelay, last send to same device was 0.111 secs ago, required delay is 0.1
2025.09.04 22:53:10 5: Afrit: checkDelays commDelay, last communication with same device was 0.103 secs ago, required delay is 0.1
2025.09.04 22:53:10 5: Afrit: checkDelays clientSwitchDelay is not relevant
2025.09.04 22:53:10 5: Afrit: checkDelays busDelayRead is not required
2025.09.04 22:53:10 4: Afrit: ProcessRequestQueue (V4.5.6 - 7.11.2023) qlen 2, sending 00d40000000601039c400001 via 192.168.178.254:502, read buffer empty,
request: id 1, read fc 3 h40000, len 1, tid 212, master device Afrit, reading KesselTemp (getUpdate for KesselTemp len 1), queued 0.12 secs ago
2025.09.04 22:53:10 5: Afrit: Send called from ProcessRequestQueue
2025.09.04 22:53:10 5: DevIo_SimpleWrite Afrit: 00d40000000601039c400001
2025.09.04 22:53:10 5: Afrit: StartQueueTimer called from ProcessRequestQueue sets internal timer to process queue in 1.000 seconds
2025.09.04 22:53:10 5: Afrit: readFn buffer: 00d400000003018302 mode master, expect response
2025.09.04 22:53:10 5: Afrit: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2025.09.04 22:53:10 4: Afrit: ParseFrameStart (TCP, master) extracted id 1, fCode 131, tid 212, dlen 3 and potential data 02
2025.09.04 22:53:10 5: Afrit: HandleResponse called from ReadFn
2025.09.04 22:53:10 5: Afrit: HandleResponse is now creating response hash, masterHash is HASH(0x49f0868)
2025.09.04 22:53:10 5: Afrit: HandleResponse is now calling ParseResponse, masterHash is HASH(0x49f0868)
2025.09.04 22:53:10 5: Afrit: ParseResponse called from HandleResponse, fc 131
2025.09.04 22:53:10 4: Afrit: HandleResponse got response with error code 83 / 02, illegal data address


[Nobbynews]

Vielleicht hilft das hier weiter:
https://forum.iobroker.net/assets/uploads/files/1615657901472-bedienungsanleitung_modbus_de_v06_11058240-002.pdf