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.

Sign up for GitHub

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

Jump to bottom

Add PGX and PGY devices and Service Code to config flow #98

Open
mattsaxon opened this issue Mar 6, 2022 · 1 comment
Open

Add PGX and PGY devices and Service Code to config flow #98

mattsaxon opened this issue Mar 6, 2022 · 1 comment
Assignees
@mattsaxon
Labels
enhancement New feature or request

Comments

@mattsaxon
Copy link
Collaborator

mattsaxon commented Mar 6, 2022 •
edited
Loading

Current these devices and codes are recognised, but cannot be amended during config flow.

There is no entity created for Service Code (source 127, code 63)
You cannot edit the names Control Panel, Communicator, Keypad either. (devices 51, 52, 53)
@mattsaxon mattsaxon added the enhancement New feature or request label Mar 6, 2022
@mattsaxon mattsaxon changed the title Add PGX and PGY and some other devices to config flow Add PGX and PGY devices and Service Code to config flow Mar 8, 2022
@mattsaxon mattsaxon added the question Further information is requested label Mar 8, 2022
@mattsaxon mattsaxon self-assigned this Mar 8, 2022
@mattsaxon mattsaxon added awaiting PR and removed awaiting PR question Further information is requested labels Mar 8, 2022
@mattsaxon
Copy link
Collaborator Author

These can be added as switches to activate them too rather than just adding as binary sensor entities

@mattsaxon mattsaxon removed their assignment Mar 10, 2022
@mattsaxon mattsaxon self-assigned this May 8, 2022
@mattsaxon mattsaxon mentioned this issue May 29, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattsaxon mattsaxon

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mattsaxon