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

Carbon Monoxide Detectors #83

Open
brandongallagher opened this issue Feb 11, 2016 · 2 comments · May be fixed by #93
Open

Carbon Monoxide Detectors #83

brandongallagher opened this issue Feb 11, 2016 · 2 comments · May be fixed by #93

Comments

@brandongallagher
Copy link

I don't see that there is a way to indicate that a CO detector is present and/or how many CO detectors are present. This seems like something we should add.

I think this should be an integer field to specify how many there are.

It seems like it should go under HealthAndSafety. It probably should go under the CombustionApplianceZone node, but since this is an array node, there could be multiple CAZ's, so it might be unclear which one a CO detector belongs under. Maybe the CODetector could go directly under the HealthAndSafety node? Or maybe there could be a general node for "Detectors" that could include CO, smoke, and Radon?

@nmerket
Copy link
Contributor

nmerket commented Jun 9, 2016

I like the idea of a general Detectors element that covers CO, smoke, and radon.

@nmerket nmerket added this to the v2.2 milestone Jun 9, 2016
nmerket added a commit that referenced this issue Jun 13, 2016
@nmerket nmerket linked a pull request Jun 13, 2016 that will close this issue
@nmerket nmerket modified the milestones: v3.0, v2.2 Jun 22, 2016
@Tedkidd
Copy link

Tedkidd commented Mar 6, 2019

We are primarily using Foobot to track IAQ. Sometimes Ecobee or other monitors.Knowing these devices are present in the home would probably be useful.

@nmerket nmerket removed this from the v3.0 milestone Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants