New binding suggestion: Wavin AHC 9000 / Jablotron AC-116

So for the ones losing sleep over this question, the answer is yes it works as is. :slight_smile:

1 Like

Thanks, also confirm it works in oh3.3.

Anybody also have those errors in log?

2023-05-19 09:05:13.887 [ERROR] [odbus.internal.factory.ModbusHandler] - Response TimeOut: Recv timeout 20025 : minLength=5 respIndex=0 #921287 cmd=01430104000405FB
2023-05-19 09:05:36.411 [ERROR] [odbus.internal.factory.ModbusHandler] - Response TimeOut: Recv timeout 20002 : minLength=5 respIndex=0 #921312 cmd=014301090503D6AA
2023-05-19 09:05:56.883 [ERROR] [odbus.internal.factory.ModbusHandler] - Response TimeOut: Recv timeout 20005 : minLength=5 respIndex=0 #921317 cmd=01430207050136EC

I have the same errors.

Recently Updated from OH3.4.0 to 3.4.4 But I am not shure, when the problem came …

some symptoms in random order:

  • (I also have small problems with IHC, but it is LAN, so should not be related)

  • My normal Wavin LCD display works fine

  • Binding seems ok

  • The bridge (ModBusSerialController) shows no error, and are online

  • when i install Wavin AHC9000 it shows as online.

  • but I cant autodetect my telestats and thermostats

  • When i reboot it shows Offline, with message: “BRIDGE_OFFLINE”

  • But Thing ModBusSerialController has status Online

  • When i try to change parameters (like connectTimeoutMillis: 30000) both things stay UNINITIALIZED:
    AHC9000 = HANDLER_MISSING_ERROR
    ModBusSerialController = HANDLER_CONFIGURATION_PENDING,

    • and it is not accepting my custom port name /dev/ttyUSBwavin (set in 99-com.rules)
  • I change port to /dev/ttyUSB0

  • Bridge goes Online. AHC9000 changes to OFFLINE (Controller is offline)

  • i delete AHC9000 thing - and install thing again. Now it shows immidiately as offline.

  • my ComfoAir binding also uses USB, and working.

  • Serial and normal modbus binding (controlling a lot of Arduinos through rs485 (also through USB) also working.

I’m clueless and frustated

Debug-Logs:

2023-05-25 11:18:45.519 [DEBUG] [us.internal.factory.ModbusActionFeed] - execFastActions (3)

2023-05-25 11:18:47.520 [DEBUG] [org.eclipse.jetty.server.HttpOutput ] - write(array) s=OPEN,api=BLOCKING,sc=false,e=null aggregated !flush DirectByteBuffer@190d1b0[p=0,l=49,c=32768,r=49]={<<<event: alive\ndata: {"type...:"ALIVE","interval":10}>>>rtmodbus:...\x00\x00\x00\x00\x00\x00\x00}

2023-05-25 11:18:47.521 [DEBUG] [org.eclipse.jetty.server.HttpChannel] - sendResponse info=null content=DirectByteBuffer@190d1b0[p=0,l=49,c=32768,r=49]={<<<event: alive\ndata: {"type...:"ALIVE","interval":10}>>>rtmodbus:...\x00\x00\x00\x00\x00\x00\x00} complete=false committing=false callback=Blocker@ee4a07{null}

2023-05-25 11:18:47.523 [DEBUG] [org.eclipse.jetty.io.WriteFlusher ] - write: WriteFlusher@1e316ba{IDLE}->null [HeapByteBuffer@10ea155[p=0,l=6,c=1024,r=6]={<<<\r\n31\r\n>>>\n\n\x00\x00\x00\x00\x00\x00\x00...\x00\x00\x00\x00\x00\x00\x00},DirectByteBuffer@190d1b0[p=0,l=49,c=32768,r=49]={<<<event: alive\ndata: {"type...:"ALIVE","interval":10}>>>rtmodbus:...\x00\x00\x00\x00\x00\x00\x00}]

2023-05-25 11:18:48.832 [ERROR] [odbus.internal.factory.ModbusHandler] - Response TimeOut: Recv timeout 10024 : minLength=5 respIndex=0 #50 cmd=0143000000030404