Closed Bostwickenator closed 2 years ago
The logic for the alarm will be present in SmartHome platform you hook it up to.
@awulff73 I don't think that addresses my request. If I'm mistaken can you please point me to the location in the code where the device will trigger an output without instruction from network device?
It's not in the code. Konnected is not made to work independently of a smarthome platform. That is where the logic for the alarm is.
Cool, this looks like a valid feature request then!
I don't think you are understanding the use case. We won't be building alarm functionality into the code. We are not looking to produce a standalone alarm system. That's for the integration of the smarthome platform to handle.
Just checking @awulff73 do you speak for @heythisisnate and the Konnected-IO team on this?
I work on the support side.
Andy is right. Konnected is not a standalone alarm system and we do not have plans to build arm/disarm logic or output triggering in the stock firmware. Philosophically, Konnected is a bridge for your wired devices to be monitored/controlled by one of our supported smart home platforms. That said, we're committed to making our hardware open and extensible and customizable to your needs. I'd encourage you to look at running ESPHome on your Konnected device if you have a need for locally triggered actions. See: https://help.konnected.io/support/solutions/folders/32000036472
Ah interesting I had assumed from the language on the product pages that at least minimal internal logic had to be provided if the system was being called a "retrofit" for existing alarm systems. As it stands a WiFi deauth attack would render the siren of a Konnected system inoperative. So it can't really hit a really major use case for traditional alarm systems. Having read through the code it seems extremely easy to add this functionality (which I'd happily contribute) but I don't suppose I should expect to convince you to change something that fundamental to your product offering. For my interest is (and please excuse my ignorance here) the Smart Things API fundamentally incompatible with the notion of a device which changes the state of the alarm siren autonomously?
It's not that the SmartThings API is "incompatible" per se. Konnected's design philosophy is to enable a smart home platform (SmartThings is just one option alongside Home Assistant, Hubitat, Alexa, etc) to act as the logic/brains of the alarm system so that you can leverage the power of home automation and all of your smart home devices in a security incident response. SmartThings in particular has the built-in SmartThings Home Monitor which manages the armed/disarmed/alert modes of the system, and Konnected simply relays sensor state and takes instructions from SmartThings to trigger actuators. This enables you do to things like:
Konnected is a "decentralized" system, which means that you could have multiple Konnected devices, in different parts of the house, all reporting into ST to create one single alarm system.
If you're concerned about WiFi deauth attacks, consider our Alarm Panel Pro which has Ethernet capability.
Thanks for the info. It still seems to me that it would be possible to have some internal state determination without interfering from the usecases which you have specified. I'll roll something of my own. Thanks for including the PIN mappings in the documentation that will be useful.
From my reading of the documentation and code there doesn't seem to be a system to "ARM" the device. That is have the device take an action independently when a sensor state changes. Is this something that is explicitly not supported for philosophical reasons or just not implemented?