Michaël Arnauts

I have never seen this: ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.0.35', 56747) I would guess your bridge is running an old Firmware, or you have some odd network issues...

> > I have never seen this: > > ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.0.35', 56747) > > [#9 (comment)](https://github.com/michaelarnauts/home-assistant-comfoconnect/issues/9#issuecomment-1526189226) last logline Thanks! But anyway, I have no clue...

That's a nice idea. I'll see if that's possible.

I have no clue what could be the cause of this. I don't do any manual database actions, so this seems like something that is caused by Home Assistant itself.

I agree with @denmaus, while you are technically correct that it's impossible to specify a negative number with an unsigned int, it does make it more clear what the values...

> Maybe: `-1 (0xFFFF)` ? That's also fine I guess :)

I can think of two reasons. * You have a non-default PIN * You are running an old firmware on the Comfoconnect LAN C and there is already an active...

I wonder if this was the cause: https://github.com/michaelarnauts/aiocomfoconnect/pull/50

Is it possible your orientation is Right? If you use this in Home Assistant, it will be easier to swap the sensors there (in sensor.py)

Sorry for not replying sooner. The unit reports different temperatures on some sensors depending on if you have a heat exchanger. Can you provide me a list of all sensor...