The recommended way to import a plug into your ESPHome dashboard is through the dashboard import feature. The plug should show up in the ESPHome dashboard as being available to adopt. Below is the minimum necessary yaml, which can be used to manually add your device instead. Change the name and friendly_name substitutions to fit your use case. Adding a use_address: under wifi: will allow you to point the ESPHome dashboard to the device on your network for flashing OTA.
The friendly_name substitution is recommended and will not be automatically created by the ESPHome dashboard import. If you use the ESPHome dashboard import feature, we recommend that you add a friendly_name substitution to rename all of the entities in Home Assistant in one line of yaml.
substitutions:
name: bedroom-lamp
friendly_name: Bedroom Lamp
packages:
kauf.plf10: github://KaufHA/PLF10/kauf-plug.yaml
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
This repo contains files for the PLF10 Power Monitoring Smart Plug.
kauf-plug.yaml - The yaml file recommended to import a plug into your ESPHome dashboard and keep all custom KAUF functionality. This is the yaml file incorporated automatically when the dashboard import feature is used.
kauf-plug-lite.yaml - A yaml file without any Kauf custom components but otherwise keeping as much functionality from kauf-plug.yaml as possible.
kauf-plug-minimal.yaml - A yaml file to import a plug into your ESPHome dashboard with only basic power monitoring smart plug functionality using stock ESPHome.
kauf-plug-update.yaml - The yaml file to build the update bin file. Generally not useful to end users.
kauf-plug-factory.yaml - The yaml file to build the factory bin file. Generally not useful to end users.
Kauf Plug switch entity - The main switch that controls the plug's relay. It will be named just Kauf Plug, or whatever you set the friendly_name substitution to in yaml. All other entities will be prefixed with the name of this entity plus whatever is indicated below for the particular other entity.
Blue LED switch entity - Controls the blue LED on and off.
Red LED switch entity - Controls the red LED on and off.
If using the precompiled binary or kauf-plug.yaml as a package in the ESPHome dashboard, the following configuration entities are automatically created. Entities listed as disabled by default can be enabled in Home Assistant, or simply modified through the web interface by clicking "Visit Device" in Home Assistant or typing the plug's IP address into a web browser. Adding the substitution disable_entities: "false" in your yaml file will cause all entities to be automatically enabled in Home Assistant.
Blue LED Brightness number entity - sets the brightness of the blue LED when on.
Blue LED Config select entity - Configures the behavior of the blue LED. Has the following options. Defaults to Power Status.
- Power Status: LED follows relay state.
- No Automation: The plug will never automatically change the LED, but the LED can still be user-controlled via the light entity.
- Invert Power Status: LED follows the inverse of the relay's state (LED on when relay is off).
- Error Status: The LED will blink when an error is detected. The most common errors are being unable to connect to Wi-Fi or Home Assistant.
- Error and Power: The LED will follow the relay state, but then also blink when an error is detected.
- Error and Invert Power: The LED will follow the inverse of the relay state, but then also blink when an error is detected.
Red LED Brightness number entity - sets the brightness of the red LED when on.
Red LED Config select entity - Same as the Blue LED select entity, but for the Red LED. Defaults to Error Status.
Button Config select entity - Defines when the button toggles the relay. To disable the button toggling the relay, select the Don't Toggle option. Otherwise, you can select the relay to toggle either on press or on release of the button. Toggle on release might be desired in order to have a different action performed when the button is held for a certain amount of time. For instance, the precompiled binary defaults to toggling on release so that the toggle can be blocked in case the button is held for 30 seconds to reenable the Wi-Fi AP.
Boot State select entity - Defines the relay's behavior on boot.
- Restore Power Off State: The relay will restore its state from the last time the plug was changed before power off or reboot.
- Invert Power Off State: The relay will toggle every time it is reboot or powered off and back on.
- Always On: The relay will always turn on when the plug boots.
- Always Off: The relay will always remain off when the plug boots.
- YAML Configured: The boot state is set using the
sub_restore_mode:substitution to any valid value for a GPIO switch's restore mode.
Monitoring Update Interval select entity - Disabled by default. Defines the update frequency for the power monitoring sensor entities. Defaults to 10s. Hard coded options are 2s, 5s, 10s, 30s, and 60s. The YAML Configured option uses the value defined by the sub_update_interval: substitution in YAML. For the precompiled binaries, this is set to 20s to provide an additional option. Changing this value will cause the plug to automatically reboot to effect the change.
Early Publish switch entity - controls whether the plug will report power usage before the configured update interval if a change greater than configured thresholds is detected. Defaults to on. Default thresholds are +/- 3w or 25%.
Debounce Time number entity - Disabled by default. Defines an amount of time that the button needs to be held before toggling the relay. Defaults to 100ms and has a minimum value of 50ms. The PLF10's button needs at least a minimum of 40ms debounce, but the actual necessary value depends on the amount of EMI in the environment where the plug is being used. Changing this value will cause the plug to automatically reboot to effect the change.
No Hass switch entity - Disabled by default. Turn this switch on if not using Home Assistant with the plug. Prevents the plug from flashing an error due to no API connection and rebooting every 15 minutes.
Scale Current number entity - Disabled by default. Scales the current sensor. Can be used to calibrate the plug.
Scale Power number entity - Disabled by default. Scales the power sensor. Can be used to calibrate the plug.
Scale Voltage number entity - Disabled by default. Scales the voltage sensor. Can be used to calibrate the plug.
Use Threshold number entity - Disabled by default. Sets a threshold for the Device in Use binary sensor. The binary sensor turns on if the power detected by the plug exceeds the threshold.
If using the precompiled binary or kauf-plug.yaml as a package in the ESPHome dashboard, the following diagnostic entities are automatically created. All diagnostic entities are disabled by default. Adding the substitution disable_entities: "false" in your yaml file will cause all entities to be automatically enabled in Home Assistant.
Restart Firmware button entity - Press this button to reboot the plug.
Button Press Duration sensor entity - Indicates the amount of time in milliseconds that the button was last pressed for. Reads zero while the button is being pressed.
IP Address sensor entity - Gives the plug's IP address.
Uptime number entity - Gives the plug's uptime in seconds.
When using kauf-plug.yaml as a package in the ESPHome dashboard, you can configure the following aspects by adding substitutions. The substitutions section of kauf-plug.yaml has comments with more explanation as well. Adding one of these in your local yaml will overwrite the corresponding value in kauf-plug.yaml.
name - Defines the plug's name in the ESPHome dashboard, the device name in Home Assistant, mDNS URL, and other various aspects. The name should use only lower-case letters and dashes. Do not use spaces or underlines.
friendly_name - The friendly name will be used to name every entity in Home Assistant. Add a substitution to change this to something descriptive for each device. Capital letters and spaces are good for the friendly name.
sub_restore_mode - defines the state of the relay on boot-up. See more about the options under restore_mode here: GPIO Switch. The boot mode select entity must remain in the YAML Configured option for this substitution to be effective.
disable_entities - Adding a substitution to redefine this to "false" will result in all entities being automatically enabled in Home Assistant.
disable_webserver - Adding a substitution to redefine this to "true" will result in the plug's webserver not listening on port 80.
button actions - The sub_on_press and sub_on_release substitutions can be used to define scripts that will run based on button press and release if you want something different than the default actions to happen.
plug state actions - The sub_on_turn_on and sub_on_turn_off substitutions can be used to define scripts that will run when the plug's relay turns on and off, respectively.
sub_toggle_check - defines a script that, if running, will stop the button from toggling on release. Can be used to stop a button press action from occurring when a hold action executed instead.
default_button_config - defines the default option for the button config select entity.
sub_default_scale_* - defines default values for the power, current, and voltage scaling.
power monitoring calibration - all of the values used to calibrate the power monitoring calibration can be overwritten using substitutions to make the calibration more accurate (current_resistor_val, voltage_divider_val, sub_hlw_model, power_cal_*, current_cal_*, voltage_cal_*).
power monitoring update interval (sub_update_interval:) - Defines the time delay between updates of the power monitoring sensors. The power monitoring update interval select entity needs to be set to YAML Configured for this substitution to take effect.
sub_pm_initial_option - Defines the default option for the power monitoring update interval select entity.
sub_early_publish_percent - Defines a percentage change, relative to the current power output, at which time the plug will ignore the configured update interval and immediately report a new power output to the sensor. Defaults to 25%.
sub_early_publish_percent_min_power - Defines a minimum power, under which the early publish percent configuration will be ignored. The plug will never publish early based on percentage change if under this value. Defaults to 0.5W.
sub_early_publish_absolute - Defines an absolute power change after which the plug will ignore the configured update interval and update immediately. The unit for this is NOT WATTS but rather a raw value used under the hood for processing. To figure out what value you need here, you can enable verbose logging and the HLW component will output the needed raw value. For the PLF10 plug, 1W translates to 5.56. Defaults to 16.68, which is an approximately 3w change.
sub_hlw_timeout - sets an amount of time to wait for a signal from the power monitoring chip before assuming the power being used is 0w. Defaults to 3s.
Multiple Wi-Fi networks can now be configured with the networks: key under wifi:. By default, the configured networks: will be added in addition to the default initial_ap network. If you want to only include the networks: you added in your local yaml without initial_ap as well, then you need to set only_networks: true under wifi:. If you set your SSID/password without the networks: key, then that will automatically overwrite the default initial_ap network.
Note: With multiple networks configured, you will need to disable fast_connect, which is on by default, with fast_connect: false.
The following substitutions can be set to the name of a script to execute automatically in certain circumstances. You need to write the script in your yaml file.
sub_on_press - executes right when button is initially pressed
sub_on_release - executes right when button is released
sub_on_hold_30s - executes right when button has been held for 30s, while button is still being held
sub_on_turn_on - executes right when relay turns on
sub_on_turn_off - executes right when relay turns off
Going to the plug's URL in a web browser and adding /reset will completely wipe all settings from flash memory. Note that this will wipe the plug's memory of whether the relay was on or off, and therefore the plug may turn off.
Holding the plug's button for 30 seconds will clear any programmed Wi-Fi credentials, including any hard coded via yaml configuration, and cause the plug to put its Wi-Fi AP back up. Going to the plug's URL in a web browser and adding /clear will do the same thing. No other settings or data will be lost.
ESPHome began adding API encryption by default, which may make the plug binary files too big to OTA update. kauf-plug.yaml v2.03 removed the light entities and replaced them with switch entities to toggle lights and number entities to control brightness. This change reduced the binary size and OTA should now work with API encryption without a problem.
If you are still getting the message ERROR Error binary size: Error: ESP does not have enough space to store OTA file., we recommend that you remove API encryption by commenting out or deleting the following lines:
# api:
# encryption:
# key: ...
If you want to keep API encryption, you can flash first with the kauf-plug-minimal.yaml file each time you need to update or upgrade, and then revert back to the kauf-plug.yaml.
Our latest batch of smart plugs has a hardware issue making them susceptible to radio interference, which can make the ESP think that the button was pressed when it really wasn't. To filter out these spurious presses, a debounce of 100ms was added to the button in the latest firmware release. Please contact us if the plug is still turning itself on and off even after updating to the latest firmware version and we will warranty the plug.
General troubleshooting ideas applicable to all products are located in the Common repo's readme.
{"NAME":"KAUF Plug","GPIO":[576,0,320,0,224,2720,0,0,2624,32,2656,0,0,0],"FLAG":0,"BASE":18, "CMND":"SwitchDebounce 100", "CMND":"ButtonDebounce 100"}
This page explains how to use the template if you need help: https://templates.blakadder.com/howto.html
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent