Integration interprets fire trouble as fire alarm

[LanceNickel]

Hello,

I am currently running v0.9.6 (latest non pre-release as of writing this) and ran into an odd issue. When creating automations, I use these states to trigger the automation:

• In Alarm
• In Fire Alarm

However, if a smoke detector goes into trouble, causing the "FIRE TROUBLE XX" reading on a keypad, the automation fires anyway. Of course, this isn't a fire alarm.

Let me know if there's any more detail needed from me. I'd love to help get this resolved.

[ufodone]

Is this for a Honeywell, DSC, or UNO panel? I'm guessing Honeywell?

If you're able to reproduce this with debug logging on that would be helpful.

Could you also share the triggers you are using for your automation? I'm not quite sure which states you are referring to and on which entity.

Looking at the code I think it's just mapping things wrong. There are also two attributes on the keypad sensor called fire and alarm_fire_zone. I think they should represent the fire trouble and fire alarm respectively but I don't have a Honeywell panel myself so cannot confirm. If you could confirm their behaviour I should be able to fix it up.