Have changed "type" from Optional, to "Required for some models". I don't know if this is non-standard for documentation...
Regardless, my SP3 would not work without this field configured. I spent a lot of time reading various threads on what to troubleshoot.
This post: https://community.home-assistant.io/t/broadlink-rm-pro-and-a1-sensor/3678/305 also implied the friendly_name is required but I found this not to be the case, and instead "Broadlink Switch" was simply displayed.
After much googling and trying various things, I believe the following two pip packages were required for broadlink.py to work:
sudo pip3 install pycrypto voluptuous
Should I also add this to the documentation?
Thanks,
Matt
The hint about enabling "Less secure apps" access to your Gmail account is a bit outdated; most people with the technical know-how to set up Home Assistant and edit the configuration files will likely have two-step verification enabled on their Gmail accounts. I added a small clarification about using application-specific passwords in that instance to hopefully save people an internet search.
* Updating development environment setup guide
Added more complete instructions for setting up a development environment for Home Assistant. Including details of dependencies, setting up venv. This is based on notes captured from setting up a dedicated hass dev environment on Debian 8.6.0
* Update development_environment.markdown
Updated as a result of feedback on pull request: https://github.com/home-assistant/home-assistant.github.io/pull/1804
Adding reminder to activate virtual environment before running setup along with adding reference to indicate apt-get may not be applicable to distro in use.
* Revert change to instruction to run hass
Remove statement about running hass with --open-ui and what it does (wrongly stated). Based on feedback from @balloob.
* Updated setting up venv as pyvenv is being deprecated
As of Python 3.6 pyvenv has been deprecated in favour of python3 -m venv.
Further changes may be required following resolution of discussion around setting up venv in a sub directory vs at the top level of the project.
* Remove details of Frontend requirements for NVM and Node
Given change [#5507](https://github.com/home-assistant/home-assistant/pull/5507) only attempts to setup the frontend if nvm is present. It makes sense to remove the details from here, since that was mainly around avoiding errors in the first time setup scenario. Instead I've adjusted the text to point to the FrontEnd Dev section.
* Updated centos instructions
yum install commands needs to be split so that EPEL repo is added first ahead of attempting to install other dependencies.
* Create configuration_yaml_by_shortbloke.markdown
