Steffen Vogel

I had a look at @xxorde and consequently @Stoney49th implementation of the code. I think we should try to reduce the duplicated code in the communicator classes. Basically only `Packet.parse_msg()`...

I have another proposal: Maybe its easier to keep the `Packet` class untouched. Instead we could convert ESP2 messages to ESP3 and back within the `Communicator` class.

I contacted the EnOcean Alliance and asked for some up-to-date EEPs. On their website, they state the the XMLs are member only. But maybe they are open source friendly.. Lets...

> at least then the response was a clear "no". They simply ignored my mail :(

See discussion in #72

I am trying to understand how we could decouple `Packet.build()` and `Packet.parse_msg()` as they are different for ESP2 (see #72). I guess this would be also related to this issue..

Agreed, this would be a nice feature. I would be willing to merge it if somebody contributes a PR.

I guess we could fix the issue by adding a new parameter to withings-sync which filters the synced data to a single Withings User in the configured Withings Account. First...

I quickly checked the available data provided by the WIthings API: https://developer.withings.com/oauth2/#operation/measure-getmeas There is no field in the response providing us which user the measurement is associated with. However, there...

Hi @DoctorEw, Yes, I am planning to support this. We currently dont have a continuous integration pipeline for this project. So will start with a script first to re-deploy the...