jpcornil-git

I just saw this as well. This is because remote_homeassistant creates local states for remote devices but no local platforms are associated to these. Therefore when a service is called...

To workaround this issue, I added the following lines before [helpers/service.py#L634](https://github.com/home-assistant/core/blob/dev/homeassistant/helpers/service.py#L634): ```python if not target_all_entities: assert referenced is not None # Only report on explicit referenced entities missing = set(referenced.referenced)...

Workaround for this one is to use digitalWrite(pin, HIGH) (following a pinMode(pin, OUTPUT) to address #58) but it is not very clean

Issue is probably simple to solve if you replace [L817 of cores/arduino/analog.cpp](https://github.com/arduino/ArduinoCore-renesas/blob/main/cores/arduino/analog.cpp#L817): ``` c ptr->pulse_perc((float)value * 100.0 / (1 pulse_perc((float)value * 100.0 / (1

I had a similar issue when upgrading my HA instance from 2024.1.5 to 2024.7.2 yesterday and was about to open a PR when I saw this one that looks similar....

Possible options: - use a configuration entry string specifiying the encoding directly (default to UTF-8) - use the root.Properties.System.Language property and a dictionnary mapping encoding to langages.

Whart about adding a new ConfigFlow or OptionFlow option to specify encoding ('utf-8' as default) for each devices and pass this to the axis.AxisDevice constructor ? This seems to be...

Just reiterating what I proposed above. An `encoding` parameter could be added to the axis object to fix the homeassistant (HA) side already, i.e.: - add an `encoding` parameter to...

Issue (encoding locale) hasn't been adressed yet. I can contribute/submit a PR for this one if there is an agreement about the way to proceed, e.g. see proposal above

It is possible to extract langage/locale but not related encoding afaik (a table could be created to find the latter based on the former) Now, I'm not sure how **bytes_data**...