philipherbert

Working now also in MQTT. what does wwc3 stand for ? I believe these errors at startup are new: EMS-Telegramme gelesen (Tx) | 16 | 11 | 60% -- |...

I see those only at startup and not in any logs. Before running the .dev firmware or the old GW (not S3) or before connecting EM100 or SM 200 the...

TX-writes was 0.  After firmware upload, the error counter is now only 1 and one message in log 2023-11-04 18:29:56.766 W 18: [telegram] Tx queue overflow, skip one message

regarding the temperature entities wwc3 temperature 1 (wwtemp1): 21.7 wwc3 temperature 2 (wwtemp2): 0.0 wwc3 temperature 3 (wwtemp3): 21.8 wwc3 temperature 4 (wwtemp4): 22.9 wwc3 temperature 5 (wwtemp5): 45.3 wwc3...

another question: is the boiler setting circulation pump mode supposed to control the circulation pump on the FS27/3. ? "dhw circulation pump mode", or is this setting missing on the...

are there any plans to build a release with this important fix in the next days ?

now tried a setup without without docker. As soon as I set the trap receiver port to something other than 0, the binding no longer communicates and polls. I have...

changed port from 0 to 6163 and disabled and re-enabled one snmp thing that now fails to query: ``` 2024-11-01 17:27:24.222 [DEBUG] [ing.snmp.internal.SnmpHandlerFactory] - bundle org.openhab.binding.snmp:4.2.2 (284)[org.openhab.binding.snmp.internal.SnmpHandlerFactory(357)] : ImmediateComponentHolder Finished...

I tried the snmp binding a few weeks ago on openhabian(rpi5). The same issue. So this can not only be docker related. I changed the subject of this issue (remved...

the error message looks different, the result is the same. As soon as the binding starts with the port set, the bnding will fail. Once failed re-enabling an snmp thing...