added new sensor type #997
Conversation
| description: "Zone temperature monitoring for MDF room with high & low temperature alarms, sensor failed alarm " | ||
| is_abstract: true | ||
| uses: |
There was a problem hiding this comment.
Make alarms opt_uses
| - low_zone_air_temperature_alarm | ||
| - failed_zone_air_temperature_alarm | ||
| - failed_alarm |
There was a problem hiding this comment.
Don't need failed_alarm here. These should typically go on general types or on SS.
| - CONTROL | ||
|
|
||
| MAZTM: |
There was a problem hiding this comment.
What does the MA stand for? Should be ZTC rather than ZTM since you have setpoints (controlling rather than monitoring).
There was a problem hiding this comment.
I didnt think it was quite controlling though, the setpoints are to set the temperature at which the alarm is triggered?
There was a problem hiding this comment.
If you are including the alarm points themselves there is no need to include the thresholds at which the alarms are triggered.
There was a problem hiding this comment.
I would suggest using the existing ZTM type if possible, there is nothing special about zone temp monitoring in an MDF room that would require a new type.
There was a problem hiding this comment.
okay closing, thank you
| @@ -243,3 +243,10 @@ SENSOR_CO2M_VOCM: | |||
| - /SENSOR | |||
| - CO2M | |||
| - VOCM | |||
|
|
|||
| SENSOR_MAZTM: | |||
There was a problem hiding this comment.
It is not making sense to me to have an abstract type that contains setpoints on a sensor entity. This seems like just a zone temperature sensor to me, and the different setpoints should go on the AHU or whatever this sensor applies to.
There was a problem hiding this comment.
Okay yeah this probably makes more sense
| - CONTROL | ||
|
|
||
| MAZTM: |
There was a problem hiding this comment.
I would suggest using the existing ZTM type if possible, there is nothing special about zone temp monitoring in an MDF room that would require a new type.
No description provided.