maniac103

> Did you consider this parameter or hardcode an interval ? We hard coded it (to 200ms). I don't see a compelling reason for making this configurable - do you?

> The state is transmitted as HSB and the binding then has to parse brightness and color temperature from that single state. Color temperature channels are either Dimmers or Numbers...

I'll add it to the DB once #16187 is fixed.

If you want to help testing, you can also follow the instructions [here](https://www.openhab.org/addons/bindings/ecovacs/#adding-support-for-unsupported-models) to add your device for your local installation. The necessary contents of `custom_device_descs.json` would be ```json [...

Can you please - enable debug logging (`log:set DEBUG org.openhab.binding.ecovacs` in OH console) - install [this version of the binding](https://drive.google.com/file/d/1_KQvtOjX25zKPDvSE7o1M9TE7qIYTUt3/view?usp=sharing) (it includes #16466) [1] - create and enable bridge and...

> I've updated the bundle as mentioned above, but the version seems to be a bit newer now: Oh, right, oops ... I reused the same link to do debugging...

> The JsonSyntaxException is furthermore present in the log, see at 2024-03-16 19:25:07.247 That's a different (and harmless) one though: it's emitted from EcovacsIotMqDevice, not EcovacsApiImpl.

How do you connect to the target? In 'serial' mode command port doesn't work because TX isn't supported; in 'tcp' or 'tx-serial' modes it should work though.

Sounds like RX doesn't work (as in: receives incorrect characters) ... how does the IO log look like?

@timoon That data looks off in that it looks like raw EMS data, not preprocessed like expected by the collector. The expected framing (applies to both serial and TCP) is...