I was considering STHM the alarm. If I have a bypassable contact sensor, I would expect the alarm system to ignore that sensor.
Is it your understanding that it should mean the contact sensor would no longer report anything? Open/close isn’t an alarm. It’s just an event. STHM is determining that it is an “alarm” worthy event.
That is how I see it, but there are other interpretations.
Does a device/zone place itself into bypass, or does it get bypassed? What if a device is used by more than one security app?
What is the meaning of ‘The device has been bypassed and won’t trigger an alarm’? Does it mean the device won’t do anything that could trigger an alarm (my interpretation)? Or does it mean that anything the device does shouldn’t result in an alarm if everything is behaving properly?
I think it largely boils down to STHM needing to implicitly select sensors and explicitly deselect them. It is the other way around at the moment. As well as being unnecessarily tedious when you have lots of devices, it is just wrong. A select/deselect all option would also help.
Yes, fair enough. The problem I have there is that if the device sets the bypassStatus to bypassed and STHM, or any other app, doesn’t ignore it when arming then it isn’t actually bypassed.
Yes, because it is the only way the bypassStatus makes sense to me.
It could also be argued that the bypassStatus is only bypassed once STHM (or another app) has armed and ignored it. This actually better fits in with the idea of the device being ‘bypassable’. In which how would that be communicated to the app without a command?
I suspect the reality is that bypassable doesn’t really make much sense if you try to apply it outside the context of an integrated security system.
I have to respectfully disagree on this one. It’s not wrong. It’s just one of two possible options.
In our house, for example, at least 3/4 of the sensors are used for light control. NOT security alert. That goes for both contact and motion sensors. So if every sensor is automatically added to STHM by default, then the majority of sensors have to have that undone. Annoying for us, but useful for someone else who uses the majority of their sensors for security.
Moreover I don’t know about in the UK, but in many places in the US there is a significant financial penalty for a false alarm on a security system, as much as $500. That’s a hefty price to pay for installing a new closet door sensor and forgetting to remove it from STHM. Or just having the sirens go off and wake the baby the first night after you installed it.
So either default option will be good for some households and annoying for others. Personally, I prefer the one they chose, but that’s just me.
There is another possibility, and I mention it because it is one that is offered on many Samsung smart appliances, and that’s that bypassable is another way of implementing “Sabbath mode.”
This is a question that has come up in the forum in the past, so if you’re unfamiliar with the option, here’s an old thread that goes into details:
And Samsung appliances features:
The other common example is of letting the dog out at night and wanting to temporarily turn off an individual sensor, usually with a button nearby. This is a common feature request. 
But of course that one is part of a security system. Sabbath mode applies to the lighting control sensors as well.
What I really don’t like is that STHM takes both options. If you install STHM with the default settings then all your locks and sensors will automatically be used. However if you switch from using all sensors to using selected sensors then sensors aren’t selected by default.
This is the perfect example for bypassing a contact sensor. Everything is armed. I just want to temporarily open the door.