* Add tts.baidu platform
* Update tts.baidu.markdown
Change appid to api_id, apikey to api_key, and secretkey to secret_key, because the baidu.py platform program changed.
I banged my head against the table for hours trying to make the script work on this page and then I figured out something. When viewing the page on the HA site, the variable tags {{value1}}, etc...do not display. I only see two quotes.
This is what I was seeing. ```{"event":"TestHA_Trigger", "value1":"", "value2":"", "value3":""}```
And I should be seeing this: ```{"event":"TestHA_Trigger", "value1":"{{value1}}", "value2":"{{value2}}", "value3":"{{value3}}"}
Above this section in the automation, there's a tag called { % raw % } which I'm unfamiliar with, but I made a guess that this needs to be inserted. I may have been wrong. If so, I hope I've identified a valid problem. Thanks!
* Update media_player.universal.markdown
This state template is invalid...
{% if (is_state('media_player.kodi', 'idle')
causes the following error...
Error rendering template: TemplateSyntaxError: unexpected '}', expected ')'
It seems there is a rogue bracket. when deleted the template reads...
{% if is_state('media_player.kodi', 'idle')
the template now works
* Fix second part
* Document max retries for InfluxDB
Signed-off-by: Jan Losinski <losinski@wh2.tu-dresden.de>
* influxdb: Add queue limit parameter.
Signed-off-by: Jan Losinski <losinski@wh2.tu-dresden.de>
* Adding remark pertaining to secure devices
Per experience with Schlage locks, you need to 1st exclude them from the previous network/hub before you can enroll them in a new network. This seems to be true for secure zwave devices with anti-theft protection
* Clarification
Added clarification, that you may need to use the previous setup for the exclusion process,
* Minor changes
* Adds correction to Zooz switch manual
Adds correction to Zooz switch manual, which supplied incorrect instruction on how to include/exclude the switch from a Z-wave network.
* Fix name
* Mentioned the naming of the disk_use sensor
The disk_use parameter creates sensors named disk_used. This should be mentioned along the other differing entity names. This not being mentioned on release made me lose one month of data.
~Cheers
* Align with other entries
* Language clarification
Made it clearer that in 4.2 the client_id is the same as used before. Existing language is unclear and suggests that making them the same is optional.
* Also added clarity on the sync service
