Leo Bergolth

> I’m sorry I don’t understand. Sorry. I accidently submitted the issue while still typing the description. :-) I have now updated the text.

No. They are old-style wired IR sensors with 12V power and NO/NC contacts. Power and signal lines are connected to this expansion card https://www.jablotron.com/underwood/download/pdf/en/JA-116H.pdf

`/etc/homeassistant/.storage/core.device_registry` ``` { "config_entries": [ "86c9a4785a2314ad8eab82cae3ce14af" ], "connections": [], "identifiers": [ [ "jablotron100", "device_24" ] ], "manufacturer": "Jablotron", "model": null, "name": "Motion detector (device 24)", "sw_version": null, "hw_version": null, "entry_type":...

It looks like the forked daemon processes get killed asyncronously a few seconds after the start script exited: ``` 12-22 14:00:23.072 3802 3874 I libprocessgroup: Killing pid 12181 in uid...

> The output of this command could be very large if users have lots of entities - and it's likely either the json serialization or web server library can't handle...

> Should be resolved in https://github.com/kukulich/home-assistant-jablotron100/releases/tag/3.14.0 Confirmed. Thanks!

Is there anything I can do to increase the chance of this PR being considered for merge?

I'd also vote for a JSON object as an alternative output format for representing lock states. A lock state change has several attributes like `binaryState`, `trigger`, `authorizationId`, `authorizationName` that should...

> I'd also vote for a JSON object as an alternative output format for representing lock states. > @kvj We can support both I think, I just need to know...

I am using a REST API that fetches different types of messages as XML. Depending on the type of the message, the root element might be one of several possible...