mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 07:17:14 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
c811733fae
@ -31,7 +31,7 @@ The same will work for automations.
|
||||
|
||||
### REST API
|
||||
|
||||
Using the [REST API](https://developers.home-assistant.io/docs/en/external_api_rest.html) to send a message to a given topic.
|
||||
Using the [REST API](https://developers.home-assistant.io/docs/api/rest/ to send a message to a given topic.
|
||||
|
||||
```bash
|
||||
$ curl -X POST \
|
||||
|
||||
@ -11,7 +11,7 @@ Home Assistant is NOT able to change the configuration of your router or firewal
|
||||
|
||||
## Server banner
|
||||
|
||||
Further [details about the fingerprint/server banner](/docs/security/webserver/) of a Home Assistant instance are available.
|
||||
Further [details about the fingerprint/server banner](/docs/security/webserver/) of a Home Assistant instance are available.
|
||||
|
||||
## Porosity
|
||||
|
||||
@ -23,11 +23,10 @@ Home Assistant is following the [Mozilla's Operations Security team recommendati
|
||||
|
||||
## SSH
|
||||
|
||||
The SSH connection for [debugging](https://developers.home-assistant.io/docs/en/hassio_debugging.html) on port 22222 is not enabled by default and can only be used with keys.
|
||||
The SSH connection for [debugging](https://developers.home-assistant.io/docs/operating-system/debugging.html) on port 22222 is not enabled by default and can only be used with keys.
|
||||
|
||||
If SSH is used with the [SSH server add-on](/addons/ssh/) then the user is responsible for the configuration and security.
|
||||
|
||||
## Source code
|
||||
|
||||
Due to the lack of resources we are not able to review all of our dependencies and inspect them for malicious behavior, leakage of information or compliance with GDPR. But we have a keen interest in the development of our dependencies and try to work closely with the upstream developer.
|
||||
|
||||
|
||||
@ -15,6 +15,7 @@ There have [been reports](https://www.raspberrypi.org/forums/viewtopic.php?f=28&
|
||||
|
||||
- Aeotec Z-Stick Series 5
|
||||
- Everspring USB stick - Gen 5
|
||||
- GoControl HUSBZB-1 stick
|
||||
- Sigma Designs UZB stick
|
||||
- Vision USB stick - Gen5
|
||||
- Zooz Z-Wave Plus S2 stick ZST10
|
||||
|
||||
@ -18,7 +18,7 @@
|
||||
<li>{% active_link /lovelace/yaml-mode/ YAML mode %}</li>
|
||||
<li>{% active_link /lovelace/dashboards-and-views/ Dashboards & Views %}</li>
|
||||
<li>{% active_link /lovelace/actions/ Actions %}</li>
|
||||
<li><a href='https://developers.home-assistant.io/docs/en/lovelace_custom_card.html'>Developing Custom Cards <i icon='icon-external-link'></i></a></li>
|
||||
<li><a href='https://developers.home-assistant.io/docs/frontend/custom-ui/lovelace-custom-card.html'>Developing Custom Cards <i icon='icon-external-link'></i></a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@
|
||||
<a href='https://github.com/coogie/oscailte'>Oscalite theme</a>.<br />
|
||||
<br />
|
||||
<a href="https://www.netlify.com">
|
||||
<img src="/images/frontpage/netlify.svg"/>
|
||||
<img src="/images/frontpage/netlify.svg" alt="Deploys by Netlify Badge"/>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -958,6 +958,7 @@ The following is a list of regions and the corresponding URL for the web-based A
|
||||
- India: `https://alexa.amazon.in`
|
||||
- Spain: `https://alexa.amazon.es`
|
||||
- France: `https://alexa.amazon.fr`
|
||||
- Italy: `https://alexa.amazon.it`
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
@ -14,16 +14,20 @@ ha_codeowners:
|
||||
|
||||
You can enable the Cast integration by going to the Integrations page inside the configuration panel.
|
||||
|
||||
## Setup
|
||||
|
||||
Support for mDNS discovery in your local network is mandatory. Make sure that your router has this feature enabled. This is even required if you entered the IP addresses of the Cast devices are manually in the configuration as mentioned below.
|
||||
|
||||
## Home Assistant Cast
|
||||
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
Home Assistant has its own Cast application to show the Home Assistant UI on any Chromecast device. You can use it by adding the [Cast entity row](/lovelace/entities/#cast) to your Lovelace UI, or by calling the `cast.show_lovelace_view` service. The service takes the path of a Lovelace view and an entity ID of a Cast device to show the view on. A `path` has to be defined in your Lovelace YAML for each view, as outlined in the [views documentation](/lovelace/views/#path). The `dashboard_path` is the part of the Lovelace UI URL that follows the defined `base_url` Typically "lovelace". The following is a full configuration for a script that starts casting the `downstairs` tab of the `lovelace-cast` path (note that `entity_id` is specified under `data` and not for the service call):
|
||||
|
||||
```yaml
|
||||
'cast_downstairs_on_kitchen':
|
||||
alias: Show Downstairs on kitchen
|
||||
sequence:
|
||||
- data:
|
||||
dashboard_path: lovelace-cast-
|
||||
dashboard_path: lovelace
|
||||
entity_id: media_player.kitchen
|
||||
view_path: downstairs
|
||||
service: cast.show_lovelace_view
|
||||
@ -105,7 +109,7 @@ media_player:
|
||||
type: list
|
||||
keys:
|
||||
host:
|
||||
description: IP-address of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS.
|
||||
description: IP address of a Cast device to add to Home Assistant. Use only if you don't want to add all available devices. The device won't be added until discovered through mDNS.
|
||||
required: false
|
||||
type: string
|
||||
ignore_cec:
|
||||
@ -128,3 +132,4 @@ If this is not possible, it's necessary to:
|
||||
|
||||
- Enable mDNS forwarding between the subnets.
|
||||
- Enable source NAT to make requests from Home Assistant to the Chromecast appear to come from the same subnet as the Chromecast.
|
||||
|
||||
|
||||
@ -39,17 +39,79 @@ You can use V_TEMP to send the current temperature from the node to Home Assista
|
||||
For more information, visit the [serial API](https://www.mysensors.org/download) of MySensors.
|
||||
|
||||
## Example sketch for MySensors 2.x
|
||||
|
||||
{% raw %}
|
||||
```cpp
|
||||
/*
|
||||
* Documentation: https://www.mysensors.org
|
||||
* Support Forum: https://forum.mysensors.org
|
||||
*/
|
||||
/**
|
||||
* The MySensors Arduino library handles the wireless radio link and protocol
|
||||
* between your home built sensors/actuators and HA controller of choice.
|
||||
* The sensors forms a self healing radio network with optional repeaters. Each
|
||||
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
|
||||
* network topology allowing messages to be routed to nodes.
|
||||
*
|
||||
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
|
||||
* Copyright (C) 2013-2015 Sensnology AB
|
||||
* Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
|
||||
*
|
||||
* Documentation: http://www.mysensors.org
|
||||
* Support Forum: http://forum.mysensors.org
|
||||
*
|
||||
* This program is free software; you can redistribute it and/or
|
||||
* modify it under the terms of the GNU General Public License
|
||||
* version 2 as published by the Free Software Foundation.
|
||||
*
|
||||
*******************************
|
||||
*
|
||||
* REVISION HISTORY
|
||||
* Version 1.0 - Toni A - https://github.com/ToniA/arduino-heatpumpir
|
||||
* Version 2.1 - Author unknown - example script from the Home Assistant website : https://www.home-assistant.io/integrations/climate.mysensors
|
||||
* Version 2.2 - Eric Van Bocxlaer - based on the example script from the Home Assistant website : https://www.home-assistant.io/integrations/climate.mysensors
|
||||
* - https://community.home-assistant.io/t/mysensors-hvac-not-showing-up/22540
|
||||
* Version 2.3 - Eric Van Bocxlaer - correction states send back to home assistant, is expecting text values and not numeric values
|
||||
*
|
||||
* DESCRIPTION
|
||||
* Heatpump controller
|
||||
*/
|
||||
|
||||
#define MY_RADIO_NRF24
|
||||
#define CHILD_ID_HVAC 0
|
||||
// Enable debug prints to serial monitor
|
||||
//#define MY_DEBUG
|
||||
// Enable specific RFM69 debug prints to serial monitor
|
||||
//#define MY_DEBUG_VERBOSE_RFM69
|
||||
|
||||
#define MY_NODE_ID 3 // set the node ID manually because a MQTT gateway will not assign automatically a node Id - this must be set before the mysensors.h call
|
||||
|
||||
// Enable and select radio type attached. Replace the defines if you use other radio type hardware.
|
||||
#define MY_RADIO_RFM69
|
||||
#define MY_RFM69_FREQUENCY RFM69_868MHZ // Set your frequency here
|
||||
#define MY_IS_RFM69HW // Omit if your RFM is not "H"
|
||||
#define MY_RFM69_NEW_DRIVER // soft spi for rfm69 radio works only with new driver
|
||||
|
||||
//enable radio communication encryption
|
||||
// more information can be found on https://forum.mysensors.org/topic/10382/security-signing-messages-and-encryption-of-messages-a-guide-or-more-a-summary-of-my-tests?_=1588348189475
|
||||
//#define MY_ENCRYPTION_SIMPLE_PASSWD "your16bitpassword"
|
||||
//enable simple signing
|
||||
//#define MY_SIGNING_SIMPLE_PASSWD "your32bitpassword"
|
||||
//#define MY_SIGNING_SIMPLE_PASSWD "your16bitpassword"
|
||||
//enable simple signing and encryption
|
||||
//#define MY_SECURITY_SIMPLE_PASSWORD "your16bitpassword"
|
||||
//enable simple signing and encryption
|
||||
#define MY_SECURITY_SIMPLE_PASSWORD "your32bitpassword"
|
||||
//enable soft signing
|
||||
//#define MY_SIGNING_SOFT
|
||||
//#define MY_SIGNING_REQUEST_SIGNATURES
|
||||
//#define MY_SIGNING_SOFT_RANDOMSEED_PIN A0
|
||||
// following hex codes are dummy hex codes, replace by your hexcodes (see the link above how to generate)
|
||||
//#define MY_SIGNING_NODE_WHITELISTING {{.nodeId = 0,.serial = {0x99,0x88,0x77,0x66,0x55,0x44,0x33,0x22,0x11}},{.nodeId = 1,.serial = {0x11,0x22,0x33,0x44,0x55,0x66,0x77,0x88,0x99}}}
|
||||
|
||||
#include <MySensors.h> // sketch tested with version 2.3.2, see http://librarymanager/all#MySensors
|
||||
|
||||
#define SENSOR_NAME "Heatpump Sensor"
|
||||
#define SENSOR_VERSION "2.3"
|
||||
|
||||
#define CHILD_ID_HVAC 0 // Each radio node can report data for up to 254 different child sensors. You are free to choose the child id yourself.
|
||||
// You should avoid using child-id 255 because it is used for things like sending in battery level and other (protocol internal) node specific information.
|
||||
|
||||
#define IR_PIN 3 // Arduino pin tied to the IR led using Arduino PWM
|
||||
|
||||
#include <MySensors.h>
|
||||
|
||||
// Uncomment your heatpump model
|
||||
//#include <FujitsuHeatpumpIR.h>
|
||||
@ -58,11 +120,11 @@ For more information, visit the [serial API](https://www.mysensors.org/download)
|
||||
//#include <CarrierHeatpumpIR.h>
|
||||
//#include <MideaHeatpumpIR.h>
|
||||
//#include <MitsubishiHeatpumpIR.h>
|
||||
//#include <SamsungHeatpumpIR.h>
|
||||
//#include <SamsungHeatpumpIR.h> // sketch tested with version 1.0.15, see http://librarymanager#HeatpumpIR by Toni Arte
|
||||
//#include <SharpHeatpumpIR.h>
|
||||
//#include <DaikinHeatpumpIR.h>
|
||||
|
||||
//Some global variables to hold the states
|
||||
//Some global variables to hold the numeric states sent to the airco unit
|
||||
int POWER_STATE;
|
||||
int TEMP_STATE;
|
||||
int FAN_STATE;
|
||||
@ -70,11 +132,15 @@ int MODE_STATE;
|
||||
int VDIR_STATE;
|
||||
int HDIR_STATE;
|
||||
|
||||
IRSenderPWM irSender(3); // IR led on Arduino digital pin 3, using Arduino PWM
|
||||
//Some global variables to hold the text states sent to the home assistant controller
|
||||
String FAN_STATE_TXT; // possible values ("Min", "Normal", "Max", "Auto")
|
||||
String MODE_STATE_TXT; // possible values ("Off", "HeatOn", "CoolOn", or "AutoChangeOver")
|
||||
|
||||
//Change to your Heatpump
|
||||
HeatpumpIR *heatpumpIR = new PanasonicNKEHeatpumpIR();
|
||||
|
||||
IRSenderPWM irSender(IR_PIN);
|
||||
|
||||
//Change to your own Heatpump
|
||||
//HeatpumpIR *heatpumpIR = new SamsungAQV12MSANHeatpumpIR();
|
||||
/*
|
||||
new PanasonicDKEHeatpumpIR()
|
||||
new PanasonicJKEHeatpumpIR()
|
||||
@ -84,7 +150,9 @@ new MideaHeatpumpIR()
|
||||
new FujitsuHeatpumpIR()
|
||||
new MitsubishiFDHeatpumpIR()
|
||||
new MitsubishiFEHeatpumpIR()
|
||||
new SamsungHeatpumpIR()
|
||||
new SamsungAQVHeatpumpIR()
|
||||
new SamsungFJMHeatpumpIR()
|
||||
// new SamsungHeatpumpIR() is a protected generic method, cannot be created directly
|
||||
new SharpHeatpumpIR()
|
||||
new DaikinHeatpumpIR()
|
||||
*/
|
||||
@ -96,7 +164,10 @@ MyMessage msgHVACFlowState(CHILD_ID_HVAC, V_HVAC_FLOW_STATE);
|
||||
bool initialValueSent = false;
|
||||
|
||||
void presentation() {
|
||||
sendSketchInfo("Heatpump", "2.1");
|
||||
// Send the sketch version information to the gateway and Controller
|
||||
sendSketchInfo(SENSOR_NAME, SENSOR_VERSION);
|
||||
|
||||
// Register all sensors to gw (they will be created as child devices) by their ID and S_TYPE
|
||||
present(CHILD_ID_HVAC, S_HVAC, "Thermostat");
|
||||
}
|
||||
|
||||
@ -106,9 +177,13 @@ void setup() {
|
||||
void loop() {
|
||||
// put your main code here, to run repeatedly:
|
||||
if (!initialValueSent) {
|
||||
send(msgHVACSetPointC.set(20));
|
||||
send(msgHVACSpeed.set("Auto"));
|
||||
send(msgHVACFlowState.set("Off"));
|
||||
FAN_STATE_TXT = "Auto"; // default fan start state
|
||||
TEMP_STATE = 20; // default start temperature
|
||||
MODE_STATE_TXT = "Off"; // default mode state
|
||||
|
||||
send(msgHVACSetPointC.set(TEMP_STATE));
|
||||
send(msgHVACSpeed.set(FAN_STATE_TXT.c_str()));
|
||||
send(msgHVACFlowState.set(MODE_STATE_TXT.c_str()));
|
||||
|
||||
initialValueSent = true;
|
||||
}
|
||||
@ -136,6 +211,7 @@ void receive(const MyMessage &message) {
|
||||
else if(recvData.equalsIgnoreCase("min")) FAN_STATE = 1;
|
||||
else if(recvData.equalsIgnoreCase("normal")) FAN_STATE = 2;
|
||||
else if(recvData.equalsIgnoreCase("max")) FAN_STATE = 3;
|
||||
FAN_STATE_TXT = recvData;
|
||||
break;
|
||||
|
||||
case V_HVAC_SETPOINT_COOL:
|
||||
@ -161,6 +237,7 @@ void receive(const MyMessage &message) {
|
||||
else if (recvData.equalsIgnoreCase("off")){
|
||||
POWER_STATE = 0;
|
||||
}
|
||||
MODE_STATE_TXT = recvData;
|
||||
break;
|
||||
}
|
||||
sendHeatpumpCommand();
|
||||
@ -168,12 +245,19 @@ void receive(const MyMessage &message) {
|
||||
}
|
||||
|
||||
void sendNewStateToGateway() {
|
||||
Serial.println("Status update send to HA:");
|
||||
Serial.println("*************************");
|
||||
Serial.println("Mode = " + MODE_STATE_TXT + "(" + (String)MODE_STATE + ")");
|
||||
Serial.println("Fan = " + FAN_STATE_TXT + "(" + (String)FAN_STATE + ")");
|
||||
Serial.println("Temp = " + (String)TEMP_STATE);
|
||||
send(msgHVACFlowState.set(MODE_STATE_TXT.c_str()));
|
||||
send(msgHVACSpeed.set(FAN_STATE_TXT.c_str()));
|
||||
send(msgHVACSetPointC.set(TEMP_STATE));
|
||||
send(msgHVACSpeed.set(FAN_STATE));
|
||||
send(msgHVACFlowState.set(MODE_STATE));
|
||||
}
|
||||
|
||||
void sendHeatpumpCommand() {
|
||||
Serial.println("Heatpump commands send to airco:");
|
||||
Serial.println("********************************");
|
||||
Serial.println("Power = " + (String)POWER_STATE);
|
||||
Serial.println("Mode = " + (String)MODE_STATE);
|
||||
Serial.println("Fan = " + (String)FAN_STATE);
|
||||
@ -182,6 +266,7 @@ void sendHeatpumpCommand() {
|
||||
heatpumpIR->send(irSender, POWER_STATE, MODE_STATE, FAN_STATE, TEMP_STATE, VDIR_AUTO, HDIR_AUTO);
|
||||
}
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
## Example sketch for MySensors 1.x
|
||||
|
||||
|
||||
@ -150,7 +150,8 @@ automation:
|
||||
level: ERROR
|
||||
action:
|
||||
service: counter.increment
|
||||
entity_id: counter.error_counter
|
||||
data:
|
||||
entity_id: counter.error_counter
|
||||
|
||||
counter:
|
||||
error_counter:
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Emoncms History
|
||||
description: Instructions on how to integrate Emoncms history into Home Assistant.
|
||||
logo: emoncms.png
|
||||
ha_category:
|
||||
- History
|
||||
ha_release: 0.31
|
||||
|
||||
@ -13,7 +13,7 @@ ha_domain: filter
|
||||
|
||||
The `filter` platform enables sensors that process the states of other entities.
|
||||
|
||||
`filter` applies a signal processing algorithm to a sensor, previous and current states, and generates a `new state` given the chosen algorithm. The next image depicts an original sensor and the filter sensor of that same sensor using the [History Graph]({{site_roor}}/integrations/history_graph/) component.
|
||||
`filter` applies a signal processing algorithm to a sensor, previous and current states, and generates a `new state` given the chosen algorithm. The next image depicts an original sensor and the filter sensor of that same sensor using the [History Graph](/lovelace/history-graph/) component.
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/filter-sensor.png' />
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Foursquare
|
||||
description: Instructions on how to the Foursquare API into Home Assistant.
|
||||
logo: foursquare.png
|
||||
ha_category:
|
||||
- Social
|
||||
ha_release: 0.26
|
||||
|
||||
@ -106,7 +106,7 @@ camera:
|
||||
|
||||
### Sharing a camera feed from one Home Assistant instance to another
|
||||
|
||||
If you are running more than one Home Assistant instance (let's call them the 'host' and 'receiver' instances) you may wish to display the camera feed from the host instance on the receiver instance. You can use the [REST API](/developers/rest_api/#get-apicamera_proxycameraltentity_id) to access the camera feed on the host (IP address 127.0.0.5) and display it on the receiver instance by configuring the receiver with the following:
|
||||
If you are running more than one Home Assistant instance (let's call them the 'host' and 'receiver' instances) you may wish to display the camera feed from the host instance on the receiver instance. You can use the [REST API](https://developers.home-assistant.io/docs/api/rest/#get-apicamera_proxycameraentity_id) to access the camera feed on the host (IP address 127.0.0.5) and display it on the receiver instance by configuring the receiver with the following:
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
|
||||
@ -133,8 +133,8 @@ In the configuration example below:
|
||||
alarm_control_panel:
|
||||
- platform: manual
|
||||
name: Home Alarm
|
||||
code: 1234
|
||||
arming_time: 30
|
||||
code: '1234'
|
||||
pending_time: 30
|
||||
delay_time: 20
|
||||
trigger_time: 4
|
||||
disarmed:
|
||||
|
||||
@ -15,7 +15,7 @@ The Mobile App integration allows Home Assistant mobile apps to easily integrate
|
||||
|
||||
If you are planning to use a mobile application that integrates with Home Assistant, we recommend that you keep this integration enabled.
|
||||
|
||||
If you are a mobile app developer, see the [developer documentation](https://developers.home-assistant.io/docs/en/app_integration_index.html) for instructions on how to build your app on top of the mobile app component.
|
||||
If you are a mobile app developer, see the [developer documentation](https://developers.home-assistant.io/docs/api/native-app-integration.html) for instructions on how to build your app on top of the mobile app component.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ Different families have different functionality and can measure different quanti
|
||||
| 12 | [DS2406(TAI-8570)](https://datasheets.maximintegrated.com/en/ds/DS2406.pdf) | Temperature (pressure when using TAI-8570) |
|
||||
| 1D | [DS2423](https://datasheets.maximintegrated.com/en/ds/DS2423.pdf) | Counter |
|
||||
| 22 | [DS1822](https://datasheets.maximintegrated.com/en/ds/DS1822.pdf) | |
|
||||
| 26 | [DS2438/B1-R1-A/S2-R1-A](https://datasheets.maximintegrated.com/en/ds/DS2438.pdf)| Temperature, Voltage, Current, (pressure and humidity when using TAI-8570) |
|
||||
| 26 | [DS2438/B1-R1-A/S2-R1-A](https://datasheets.maximintegrated.com/en/ds/DS2438.pdf)| Temperature, Voltage, Current, (pressure and humidity when using TAI-8570) |
|
||||
| 28 | [DS18B20](https://datasheets.maximintegrated.com/en/ds/DS18B20.pdf) | Temperature |
|
||||
| 3B | [DS1825](https://datasheets.maximintegrated.com/en/ds/DS1825.pdf) | Temperature |
|
||||
| 42 | [DS28EA00](https://datasheets.maximintegrated.com/en/ds/DS28EA00.pdf) | Temperature |
|
||||
@ -41,7 +41,7 @@ Notes:
|
||||
|
||||
## Interfacing with the 1-wire bus
|
||||
|
||||
The 1-Wire bus can be connected directly to the IO pins of Raspberry Pi or by using a dedicated interface adapter, for example
|
||||
The 1-Wire bus can be connected directly to the IO pins of Raspberry Pi or by using a dedicated interface adapter, for example
|
||||
[DS9490R](https://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf) or adapters based on [DS2482-100](https://datasheets.maximintegrated.com/en/ds/DS2482-100.pdf) that can be directly attached to the IO pins on the Raspberry Pi.
|
||||
|
||||
It is also possible for this platform to interface with a remote 1-wire host over a network connection using ofws and owserver.
|
||||
@ -49,9 +49,9 @@ It is also possible for this platform to interface with a remote 1-wire host ove
|
||||
## Raspberry Pi set up
|
||||
|
||||
In order to setup 1-Wire support on Raspberry Pi, you'll need to edit `/boot/config.txt` following [this documentation](https://www.waveshare.com/wiki/Raspberry_Pi_Tutorial_Series:_1-Wire_DS18B20_Sensor#Enable_1-Wire).
|
||||
To edit `/boot/config.txt` on the Home Assistant Operating System, use [this documentation](https://developers.home-assistant.io/docs/en/hassio_debugging.html) to enable SSH and edit `/mnt/boot/config.txt` via `vi`.
|
||||
To edit `/boot/config.txt` on the Home Assistant Operating System, use [this documentation](https://developers.home-assistant.io/docs/operating-system/debugging.html) to enable SSH and edit `/mnt/boot/config.txt` via `vi`.
|
||||
|
||||
When using the GPIO pins on Raspberry Pi directly as a 1-wire bus, the description above uses two kernel modules. `1w_gpio`, that implements the 1-wire protocol, and `1w_therm`, that understands the DS18B20 (family 28) components inner structure and reports temperature.
|
||||
When using the GPIO pins on Raspberry Pi directly as a 1-wire bus, the description above uses two kernel modules. `1w_gpio`, that implements the 1-wire protocol, and `1w_therm`, that understands the DS18B20 (family 28) components inner structure and reports temperature.
|
||||
There is no support for other device types (families) and hence this onewire platform only supports temperature measurements from family 28 devices.
|
||||
|
||||
## Interface adapter setup
|
||||
@ -108,7 +108,7 @@ sensor:
|
||||
|
||||
### Entities and attributes
|
||||
|
||||
Upon startup of the platform, the 1-wire bus is searched for available 1-wire devices. For each device that this platform handles (see list of supported devices above), the platform adds one sensor for each physical quantity it measures. The name of the sensor is the device ID with the physical quantity it measures appended.
|
||||
Upon startup of the platform, the 1-wire bus is searched for available 1-wire devices. For each device that this platform handles (see list of supported devices above), the platform adds one sensor for each physical quantity it measures. The name of the sensor is the device ID with the physical quantity it measures appended.
|
||||
|
||||
`sensor.28.FF5C68521604_temperature`
|
||||
|
||||
|
||||
@ -102,6 +102,7 @@ script:
|
||||
- TC-P65VT30
|
||||
- TX-32AS520E
|
||||
- TX-32DSX609
|
||||
- TX-40DX600
|
||||
- TX-40DX700B
|
||||
- TX-49DX650B
|
||||
- TX-50DX700B
|
||||
|
||||
@ -10,7 +10,7 @@ ha_codeowners:
|
||||
ha_domain: panel_custom
|
||||
---
|
||||
|
||||
The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized. See the developer documentation on [instructions how to build your own panels](https://developers.home-assistant.io/docs/en/frontend_creating_custom_panels.html).
|
||||
The `panel_custom` support allows you to add additional panels to your Home Assistant frontend. The panels are listed in the sidebar if wished and can be highly customized. See the developer documentation on [instructions how to build your own panels](https://developers.home-assistant.io/docs/frontend/custom-ui/creating-custom-panels/).
|
||||
|
||||
To enable customized panels in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ leds:
|
||||
description: The type of LED. Choose either `rgb`, `rgbw` or `simple`.
|
||||
required: true
|
||||
type: string
|
||||
freq:
|
||||
frequency:
|
||||
description: The PWM frequency.
|
||||
required: false
|
||||
default: 200
|
||||
|
||||
@ -32,7 +32,6 @@ scene:
|
||||
media_player.sony_bravia_tv:
|
||||
state: on
|
||||
source: HDMI 1
|
||||
state: on
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
|
||||
@ -158,36 +158,36 @@ Full configuration example (excluding forecasted conditions) where location is m
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
- platform: buienradar
|
||||
name: 'volkel'
|
||||
# Force 'Meetstation Volkel' to be used:
|
||||
latitude: 51.65
|
||||
longitude: 5.70
|
||||
monitored_conditions:
|
||||
- stationname
|
||||
- barometerfc
|
||||
- barometerfcname
|
||||
- conditioncode
|
||||
- condition
|
||||
- conditiondetailed
|
||||
- conditionexact
|
||||
- symbol
|
||||
- feeltemperature
|
||||
- humidity
|
||||
- temperature
|
||||
- groundtemperature
|
||||
- windspeed
|
||||
- windforce
|
||||
- winddirection
|
||||
- windazimuth
|
||||
- pressure
|
||||
- visibility
|
||||
- windgust
|
||||
- precipitation
|
||||
- irradiance
|
||||
- precipitation_forecast_average
|
||||
- precipitation_forecast_total
|
||||
- rainlast24hour
|
||||
- rainlasthour
|
||||
name: 'volkel'
|
||||
# Force 'Meetstation Volkel' to be used:
|
||||
latitude: 51.65
|
||||
longitude: 5.70
|
||||
monitored_conditions:
|
||||
- stationname
|
||||
- barometerfc
|
||||
- barometerfcname
|
||||
- conditioncode
|
||||
- condition
|
||||
- conditiondetailed
|
||||
- conditionexact
|
||||
- symbol
|
||||
- feeltemperature
|
||||
- humidity
|
||||
- temperature
|
||||
- groundtemperature
|
||||
- windspeed
|
||||
- windforce
|
||||
- winddirection
|
||||
- windazimuth
|
||||
- pressure
|
||||
- visibility
|
||||
- windgust
|
||||
- precipitation
|
||||
- irradiance
|
||||
- precipitation_forecast_average
|
||||
- precipitation_forecast_total
|
||||
- rainlast24hour
|
||||
- rainlasthour
|
||||
```
|
||||
|
||||
Configuration example with current condition and (some) forecasted values:
|
||||
|
||||
@ -248,8 +248,9 @@ This token (32 hexadecimal characters) is required for the Xiaomi Mi Robot Vacuu
|
||||
> If using an Android device to retrieve the Access Token only `v5.4.49` of Mi Home is confirmed working (December 2019).
|
||||
|
||||
1. To begin, set up your Robovac with the latest version of Mi Home on your primary Android device as you normally would.
|
||||
2. Using `v5.4.49` of Mi Home locate a text file under the `Smarthome/logs` folder where the 32 character token is stored.
|
||||
3. There will likely be several text files in this directory, search all of them for the word 'token' and you should find it there. Be advised that the latest version of Mi Home does not store the token in clear text.
|
||||
2. If your Robovac is already set up, you must reset its WiFi settings for it to get a new token.
|
||||
3. Using `v5.4.49` of Mi Home locate a text file under the `Smarthome/logs` folder where the 32 character token is stored.
|
||||
4. There will likely be several text files in this directory, search all of them for the word 'token' and you should find it there. Be advised that the latest version of Mi Home does not store the token in clear text.
|
||||
|
||||
### Linux and Rooted Android
|
||||
|
||||
|
||||
@ -176,6 +176,7 @@ logger:
|
||||
zigpy_xbee.zigbee.application: debug
|
||||
zigpy_xbee.api: debug
|
||||
zigpy_zigate: debug
|
||||
zhaquirks: debug
|
||||
```
|
||||
|
||||
### Add Philips Hue bulbs that have previously been added to another bridge
|
||||
|
||||
@ -385,7 +385,7 @@ style:
|
||||
{% endconfiguration %}
|
||||
|
||||
The process for creating and referencing custom elements is the same as for custom cards.
|
||||
Please see the [developer documentation](https://developers.home-assistant.io/docs/en/lovelace_custom_card.html)
|
||||
Please see the [developer documentation](https://developers.home-assistant.io/docs/frontend/custom-ui/lovelace-custom-card.html)
|
||||
for more information.
|
||||
|
||||
## How to use the style object
|
||||
|
||||
@ -72,7 +72,7 @@
|
||||
/developers/platform_example_sensor https://github.com/home-assistant/example-custom-config/tree/master/custom_components/example_sensor
|
||||
/developers/python_api https://developers.home-assistant.io/docs/en/external_api_rest_python.html
|
||||
/developers/releasing https://developers.home-assistant.io/docs/en/releasing.html
|
||||
/developers/rest_api https://developers.home-assistant.io/docs/en/external_api_rest.html
|
||||
/developers/rest_api https://developers.home-assistant.io/docs/api/rest.html
|
||||
/developers/server_sent_events https://developers.home-assistant.io/docs/en/external_api_server_sent_events.html
|
||||
/developers/websocket_api https://developers.home-assistant.io/docs/en/external_api_websocket.html
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ The following will take you through the steps required to install Home Assistant
|
||||
- [Odroid-XU4][odroid-xu4]
|
||||
- [Intel-Nuc][intel-nuc]
|
||||
|
||||
- As a virtual appliance:
|
||||
- As a virtual appliance (x86_64/UEFI):
|
||||
|
||||
- [VMDK][vmdk] (VMWare Workstation)
|
||||
- [VHDX][vhdx]
|
||||
@ -35,12 +35,12 @@ The following will take you through the steps required to install Home Assistant
|
||||
|
||||
2. Install Home Assistant:
|
||||
|
||||
- Flash the downloaded image to an SD card using [balenaEtcher][balenaEtcher]. If using a Pi, we recommend at least a 32 GB SD card to avoid running out of space. On Virtual machine platforms, provide at least 32 GB of disk space for the VM.
|
||||
- Load the appliance image into your virtual machine software. Choose 64-bit Linux and UEFI boot.
|
||||
- Flash the downloaded image to an SD card using [balenaEtcher][balenaEtcher]. If using a Pi, we recommend at least a 32 GB SD card to avoid running out of space.
|
||||
- Load the appliance image into your virtual machine software. Allow at least 32 GB of disk space for the virtual machine. Choose 64-bit Linux and UEFI boot. For a KVM-based setup with `virt-manager`, set **Firmware** to `UEFI x86_64: /usr/share/ovmf/x64/OVMF_CODE.fd`.
|
||||
|
||||
3. Optional - set up the Wi-Fi or static IP. There are two possible places for that:
|
||||
3. Optional - set up the Wi-Fi or a static IP address. There are two possible places for that:
|
||||
- on a blank USB stick with a FAT32 partition having partition label `CONFIG`, while in its root directory, create the `network/my-network` file, or
|
||||
- on the Home Assistant SD card's first, bootable partition (labeled `hassio-boot`, might not be auto mounted in Linux) create the `CONFIG/network/my-network` file.
|
||||
- on the Home Assistant SD card's first, bootable partition (labeled `hassos-boot`, might not be auto mounted in Linux) create the `CONFIG/network/my-network` file.
|
||||
|
||||
For the content of this file, follow the [Home Assistant Operating System howto][hassos-network].
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user