New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mqtt alarm code_arm_required #7940
Conversation
* 🚜 Merges/Redirect Egardia component pages * ✏️ Tweak list
* ✏️ Change ha_category for Iliad Italy component * ✏️ Change ha_category name
* Update homematicip_cloud.markdown HmIP Cloud Documentation update for 0.87.0 * Update homematicip_cloud.markdown
* 🚜 Merges/Redirect Canary component pages * ✏️ Remove hub category
* Create norway_air.markdown * Update norway_air.markdown * Update norway_air.markdown * ✏️ Tweak
Update to API Link (previous link invalid. Added details of cost introduced to use their cloud API. I was informed of this when I recently requested my client_secret. I was given the following from Smappee support but has yet to configure with local API via MQTT (Mosquitto & Node Red). If anyone knows how best to write this information into the page, would appreciate it. Here are the links they provided: How to find the UUID.pdf https://support.smappee.com/attachments/token/y7MJ5O6e9P2kzuniuNfP5glFw/?name=How+to+find+the+UUID.pdf Smappee local MQTT topics -20-09-2018.pdf https://support.smappee.com/attachments/token/o5gKlg0jqbK2mVh0B6yfHArCy/?name=Smappee+local+MQTT+topics+-20-09-2018.pdf Node Red, Smappee nodes: https://flows.nodered.org/node/@smappee/node-red-contrib-smappee
* Updates for python36 and scl Latest changes to installing the scl environment don't include the scl command, scl-utils is needed along w/ the proper repository in Centos7 to be enabled via RH and then downloaded to the environment which you are building and then SCL commands will work and setting python environment for bash will work too. * Minor changes
* Added informations for initial setup * ✏️ Tweak
The Aux commands work on my new D16XD. I haven't tested panic.
* Create enable_i2c.markdown * Update sensor.bme680.markdown * Update hassio_navigation.html * ✏️ Tweaks * ✏️ Tweaks
See also home-assistant/core#20260, the --init argument makes sure that the python service does not run with PID 1 which on some host systems can not be killed, i.e. restarting the service from within the UI is unreliable without that argument.
Explains that paths aren't supported in base_url so someone attempting to set settings doesn't expect something that isn't currently possible. Related: home-assistant/core#21113
* Document on_in and off_id * Space fix * Also add on_id and off_id to switch
Adds support for homekit devices with temperature, humidity, and light level characteristics (such as the iHome iSS50)
Added arm_code_required to avoid code enter when arming
# Conflicts: # source/_components/alarm_control_panel.mqtt.markdown
|
Damn, I'm not a git expert. Which is the best way to clear? |
This is a nice guide for next time: https://gist.github.com/Chaser324/ce0505fbed06b947d962#keeping-your-fork-up-to-date I think the easiest option now is to simply make a new branch and just add this change again: 44cd6ce |
@emontnemery thank you for your suggestion, after that I have to make a new pull request, right? |
Yeah. |
The new pr is #8822 |
Description:
Updates documentation about new configuration option lines value_template and code_arm_required.
Pull request in home-assistant (if applicable): home-assistant/core#19558
Checklist:
next
is for changes and new documentation that will go public with the next home-assistant release. Fixes, changes and adjustments for the current release should be created againstcurrent
.