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

enhancement request: device type extension #20

Open
jpadie opened this issue Jan 24, 2024 · 0 comments
Open

enhancement request: device type extension #20

jpadie opened this issue Jan 24, 2024 · 0 comments

Comments

@jpadie
Copy link

jpadie commented Jan 24, 2024

would it be possible to enhance the readme to include an example of how users might go about adding new device types to the endpoint templates (and corresponding entries in the node-red flows)? a mini-tutorial perhaps?

I've tried to add an air-quality-monitor to implement humidity sensors with some success (the Alexa GUI is very ugly which makes me think I have not done this well). I also cannot get nonControllable to work.

I've also tried to implement scheduling for thermostats but on this have completely failed. I think I've correctly described the discovery response but there is no change in the GUI. This may be a locale thing (the .schedule interface is only supported by en-US and my locale is en-GB and en-FR).

I'm happy to document my thought process if that might be a useful springboard.

as a more general enhancement: would it be possible to implement an abstracted range controller device type for read-only values? the instance name, units, min/max etc would be parameters in the node-red interface for that type.

thanks in advance.

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