Skip to content

Latest commit

 

History

History
71 lines (54 loc) · 7.66 KB

historic_changelog.md

File metadata and controls

71 lines (54 loc) · 7.66 KB
Raw

  • (07/03/18) NEW Feature - Pending and Trigger time can be determined per state. For example arming the alarm in away mode can be set to 60 seconds pending time, yet arming in home mode can be set to 30 seconds. This can also be overriden as per the feature below which has been expanded to include home/perimiter. See guidance here

  • (23/02/18) NEW FEATURE - Override the pending time when arming away mode so that the alarm arms instantly. To do this pass a code parameter of '-1' to the service, this could be in the form of an automation such as:

  alias: '[Alarm] Instantly Arm Away Mode'
  trigger:
  ... place your trigger here ...
  action:
  - service: alarm_control_panel.alarm_arm_away
    entity_id: alarm_control_panel.house
    data:
      code: '-1'

  • (16/02/18) NEW FEATURE - PERSISTENCE!!!!!!!! Enabling persistence in the alarm.yaml file allows this component to save the alarm state everytime it changes. This means if there is a power outage or server crash/failure then upon restart HA will auto load the previous alarm state. This has not been tested in windows but in theory should work. Ensure HA has permission to write to the config folder as this creates a new file named alarm.json.

  • (16/02/18) NEW FEATURE - Custom Panel allowing custom html/polymer code!!!!!! Use this to bring any other features you would like to see for example displaying live camera feeds, a rotating image gallery, custom HA buttons and sensors. To use this enable the custom panel in alarm.yaml (custom_panel: True) then ensure you take a copy of custom-element.html and add it to you www/alarm/ folder. Edit the html code between the template tags. I'm have added a custom sample folder where I will upload examples of 'things' which can be added here. Please contribute!!!

  • (16/02/18) NEW FEATURE - Added the ability to hide the sensor groups (all sensors, immediate sensors, delayed sensors, inactive sensors) from the display. Open sensors will still appear on the display. (hide_sensor_groups:True) see alarm.yaml for details.

  • (16/02/18) NEW FEATURE - Added the ability to mask the passcode during diasarm. The feature will be enabled by deault. See the alarm.yaml for extra information. Credit @mikefero

  • (16/02/18) BUG FIX - Added further code to force the sidebar to hide when the alarm is armed. This prevents a simple refresh showing the sidebar.

  • (16/02/18) BUG FIX - Given the time label has caused folk issues I have decided to drop the javascript implementation and use the time derived from HA. Ensure you have a time sensor setup in your sensors.yaml:

  - platform: time_date
    display_options:
      - 'time'

  • (15/02/18) BUG FIX - Fixed the code disarm issue.

  • (19/01/18) NEW FEATURE - MQTT now allows you to disarm your alarm using the your code. MQTT panels will need to support the format of the payload which is 'DISARM CODE' for example 'DISARM 0000'. To override this so that MQTT can disarm the alarm without passing across the code then set override_code: True in the alarm.yaml. Status feedback to MQTT coming soon...

  • (19/01/18) NEW FEATURE - The panel now allows you to hide the sidebar when the alarm is activated preventing in intruder to simply go to configuration and shut down HA. A suitable locked down browser will also be required to prevent the intruder simply changing the URL. You could check out kiosk on android. To activate this feature simply enable hide_sidebar: True in the alarm.yaml NOTE!! Ensure you copy alarm_scripts.js into the appropriate folder 'www/alarm'. This was a tricky feature to implement and future HA updates may break this. If anyone has a better idea on how to code this then be my guest.

  • (19/01/18) ADDITIONAL STATE - Added 'motion_detected' as a supported state

  • (15/01/18) NOTE!!!!!!! - There are a lot of changes, update all files to ensure everything works. (alarm.yaml, panels/alarm.html, custom_components/alarm_control_panel/bwalarm.py, www/lib/countdown360.js, www/lib/jquery-3.2.1.min.js, www/alarm/alarm.css) Also don't forget to clear your browser cache. Raise any issues you come across

  • (15/01/18) NEW FEATURE - Set a maximum number of Passcode attempts with a lockout period. See the alarm.yaml for setup.

  • (15/01/18) NEW FEATURE - There is now support for custom and unknown device states. Add your new on/off states into the alarm.yaml file and this component will track them!

  • (15/01/18) NEW GUI - The code panel slides in or out depending on the mode. Let me know what you think.

  • (15/01/18) BUG FIX - Weather alignment on different modes and devices.

  • (15/01/18) BUG FIX - Timer mode now appears in warning mode so you know how long before the alarm triggers.

  • (15/01/18) BUG FIX - MQTT now allows custom state/command topics via the alarm.yaml.

  • (15/01/18) BUG FIX - Re-aligned buttons for smaller devices.

  • (15/01/18) OTHER - Work progressing to clean up the python code.

  • (15/01/18) OTHER - CSS is now split from the main http file for readability, still requires a cleanse.

  • (15/01/18) COMING SOON - MQTT Support to valid passcodes.

  • (15/01/18) COMING SOON - MQTT Support to provide extended feedback to other alarm interfaces i.e. open sensor arrays, lockout feedback.

  • (15/01/18) COMING SOON - Persistance support for rebooted systems.

  • (15/01/18) COMING SOON - Disabling of the sidebar when armed. Trickier than I thought due to the use of polymer and its sandboxing.

  • (15/01/18) COMING SOON - User Guide/Help pages

  • (15/01/18) COMING SOON - Customizable settings such as gui colours, collapsable sensor groups

  • (15/01/18) COMING SOON - Screensaver mode

  • (15/01/18) COMING SOON - Granular times on home/arm mode

  • (15/01/18) COMING SOON - Screenshots + Videos

  • (08/01/17) NEW FEATURE - MQTT Integration. Enable this by setting mqtt to True in the yaml. See alarm.yaml for optional settings. This is based on the manual mqtt code. MQTT Needs to be enabled in your HA setup and configured appropriately then you should be able to use custom panels such as this

  • (28/12/17) Added a new feature 'Panic Mode' this allows you to set a panic code in the alarm.yaml. When using this code to deactivate the alarm, the alarm is deactivated however a special attribute panic_mode is set to ACTIVE. Use this backed with your automations to trigger custom messages to those who can assist.

  • (28/12/17) Added support for override sensors. When sensors are placed in this group any which are open when activing the alarm are ignored.

  • (27/12/17) Added support for devices with open/closed, true/false, locked/unlocked, detected/undetected statuses. There are some heavy changes on the code in readiness for a settings page and an optional screensaver.

  • (19/11/17) Added optional perimeter mode (activates a 'perimeter' group only) which could also ne known as 'Home Day' mode. Added weather sensor into status bar (You must have dark sky weather component enabled specifically sensor.dark_sky_summary), added 0 to code panel.

  • (13/11/17) Added sample automation.yaml. Fixed GUI issues with groups. Outlined base code for 'Perimeter mode'

  • (12/11/17) You can now use either homemodeignore or notathome group title for sensors that need to be ignored during home mode

  • (12/11/17) Added a check (displays open sensors in highlighted group) for open sensors when setting alarm (changes button text to override alarm). NOTE override in alarm.yaml isn't quite ready yet and you will still need to manually override via the button in the interface for now.