Add support for Linptech Human Presence Sensor ES5 (ES5BB)

[kei81131]

https://home.miot-spec.com/spec/linp.sensor_occupy.es5b

[qjrxsoft02]

According to the debug log analysis, Linptech ES5B has never reported events such as 2.p.1081 / 2.p.1082, nor has it reported 5.e.1097. It is recommended to remove entities like "Has Someone Duration," "No One Duration," and "Event Type" to keep the HA interface clean. I think you are Chinese. If possible, we can communicate in our native language.

[kei81131]

According to the debug log analysis, Linptech ES5B has never reported events such as 2.p.1081 / 2.p.1082, nor has it reported 5.e.1097. It is recommended to remove entities like "Has Someone Duration," "No One Duration," and "Event Type" to keep the HA interface clean. I think you are Chinese. If possible, we can communicate in our native language.

I think it’s better to comment in English here, as it’s more helpful for others.
I’m also happy to communicate with you in Chinese via PM. ^_^

Back to the topic:
All 3 sensors do report data, however they are disabled by default in Mi app.
Once enabled, ES5BB will report status to the gateway.

I personally think the “Has Someone Duration” and “No One Duration” sensors are not useful in Home Assistant.
Some users may still find them useful, but since they are disabled by default in the Mi app, I also chose to disable them by default in the converter.

[kei81131]

you can reach them inside sensor setting, please see below image for your reference

[chiachunli08]

Please add the top-mount version as well.

28377: ["Linptech", "Presence Sensor ES5", "ES5DB", "linp.sensor_occupy.es4b"],

[chiachunli08]

Please add the top-mount version as well.

28377: ["Linptech", "Presence Sensor ES5", "ES5DB", "linp.sensor_occupy.es4b"],

I just realized it's already in the code.

[qjrxsoft02]

you can reach them inside sensor setting, please see below image for your reference

Thank you very much for your reminder. After enabling the corresponding option in the Mi Home app, I indeed obtained events such as 2.p.1081 and 2.p.1082 based on the analysis of the debug logs. Personally, I think events like 2.p.1081 and 2.p.1082 are not very useful in Home Assistant, and using a timer might be more reliable than them.