You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some additional states from the Concord to Home Assistant. Also to the HA log.
* Armed State (or maybe 'disarmed' state?) For what I'm thinking 'Armed (true, false)' would probably be enough. Altho if it's being sent from the Concord to HA may as well report them all? edit 11/28/2024: Already there
Alarm (and what kind?) For my purposes I'm only interested in the Alarms that mean the sirens are blaring and lights are flashing and that the police or fire dept are on the way. Gravy would be bringing back and reporting all the alarm states to HA.
Nice to have:
who (or what user code) armed or disarmed the Concord in the HA log.
Looking at the Automation Module Protocol it looks like all of these codes are available starting on page 14, with the actual alarm types starting on page 15. What is unclear is which direction they are going. Are these from the Concord going to HA? Or does the Concord expect these to come from the peripheral (HA in this case)?
From a quick look at
concord4ws-py/concord4ws/types.py
it looks like a lot of these are already in the data on the -ws side. I have not looked at the code on the -ha side yet.
I may take a look at this myself but it's been like 15 years since I did any real coding. Everything since
has been in a vendor-proprietary "language" (and I use that term -very- loosely), or bash. 'Rust' to me is something
I take a grinder to. So I don't have much hope for my own skills. What can I say? ¯_(ツ)_/¯
Other than what I reported earlier, this interface has been solid. Thanks!
The text was updated successfully, but these errors were encountered:
Some additional states from the Concord to Home Assistant. Also to the HA log.
* Armed State (or maybe 'disarmed' state?) For what I'm thinking 'Armed (true, false)' would probably be enough. Altho if it's being sent from the Concord to HA may as well report them all?edit 11/28/2024: Already thereAlarm (and what kind?) For my purposes I'm only interested in the Alarms that mean the sirens are blaring and lights are flashing and that the police or fire dept are on the way. Gravy would be bringing back and reporting all the alarm states to HA.
Nice to have:
who (or what user code) armed or disarmed the Concord in the HA log.
Looking at the Automation Module Protocol it looks like all of these codes are available starting on page 14, with the actual alarm types starting on page 15. What is unclear is which direction they are going. Are these from the Concord going to HA? Or does the Concord expect these to come from the peripheral (HA in this case)?
From a quick look at
it looks like a lot of these are already in the data on the -ws side. I have not looked at the code on the -ha side yet.
I may take a look at this myself but it's been like 15 years since I did any real coding. Everything since
has been in a vendor-proprietary "language" (and I use that term -very- loosely), or bash. 'Rust' to me is something
I take a grinder to. So I don't have much hope for my own skills. What can I say? ¯_(ツ)_/¯
Other than what I reported earlier, this interface has been solid. Thanks!
The text was updated successfully, but these errors were encountered: