Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add unique ID field to identify the panel and its sensors #25

Open
jsb5151 opened this issue Nov 1, 2021 · 0 comments
Open

Add unique ID field to identify the panel and its sensors #25

jsb5151 opened this issue Nov 1, 2021 · 0 comments

Comments

@jsb5151
Copy link

jsb5151 commented Nov 1, 2021

Since it seems we can't pull uniquely identifiable information from the INFO packet, perhaps one way of fixing this would be to pass the panel IP address, or any other customizeable field in apps.yaml, to uniquely identify the discovered entities and bring them under one device.

This would make entities much easier to manage; all reported sensors would have the device: payload with all the parent panel's information. Paradox Alarm Interface (PAI) and many other MQTT integrations are using this.

Example of a discovered binary_sensor under PAI (pay attention to the "device" section):

{"name": "Z1", "unique_id": "abcd1234_zone_Z1_open", "state_topic": "paradox/states/zones/Z1/open", "device_class": "motion", "availability_topic": "paradox/interface/availability", "payload_on": "True", "payload_off": "False", "device": {"manufacturer": "Paradox", "model": "SP5500", "identifiers": ["Paradox", "SP5500", "abcd1234"], "name": "SP5500", "sw_version": "7.14 build 2" } }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant