M Valla

> The jSerialComm deploys but obviously doesn't start because it's missing the imports from the transport package: that is because this jserialcomm addon is meant to be run on a...

I think editing the manifest should do the trick: org.openhab.core.io.transport.serial;version="[4.2,5)" -> "[4.1,5)"

ok, if you set log level to DEBUG for `org.openhab.core.io.transport.serial.jserialcomm` and copy here the log when you try to open the serial device, that would help to solve incompatibility

I will have a look to this in the following days. What is the BTicino gateway you are connecting to? MH200N or MyHomeServer1 ? It may help if you also...

@hyzteric local offset is indeed not handled correctly. I think this case was not tested and probably a new `targetTemp` channel is needed. it is useful if you: - activate...

hi @hyzteric it would be useful to have some more log from your setup. can you: - activate DEBUG log level for the binding - initial condition before the test:...

hi @hyzteric one final check would be useful just to check some very strange behavior that appears in your previuous tests. It's useful if you repeat them but this time...

@lolodomo would be nice to add this one to 4.1.0 as well. Already tested in simulated+real system.

@lolodomo I updated this PR from early December to 4.2.x. Can you give a look?

@lolodomo and @wborn this PR was submitted already last November. Any chance you can review it? Or should I add/ask other reviewers? Thanks!