I think at some time in the past the 'command_throttle' parameter changed from a unit of 'milliseconds' to the unit of 'time'.
If you try to compile with a value of 1000 (supposedly milliseconds), compilation fails with the following error:
```
Don't know what '1000' means as it has no time *unit*! Did you mean '1000s'?.
command_throttle: 1000
```
If I put a value of '1s' then compilation works and also this is the time I see that is being used.
* Add/Rename item in Cookbook
Made a "Lambda Magic" cookbook item, where we can gather interesting Lambda implementations.
* Update lambda_magic.rst
* Update lambda_magic.rst
* Update lcd_display.rst
* remove migrated documentation
All of these are present now on our https://devices.esphome.io/ site.
The missing ones were pushed with https://github.com/esphome/esphome-devices/pull/385, and the rest ones were already in, thus removing here the duplicates.
* Update modbus.rst
* Update modbus.rst
* Update modbus_controller.rst
* Update ltr390.rst
* Update ltr390.rst
* Update modbus_controller.rst
* fix broken links
* Update index.rst
* Update index.rst
* Update doc to add multiple dallas hubs
If you have multiple dallas hubs
* Update dallas.rst
* Fix
* Title underline too short
* Update dallas.rst
---------
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
For seasonal changes, it’s easier to use the multiplier to adjust the watering time instead of adjusting the run durations directly. Set your run duration to the time you want for ‘mild’ weather (spring/autumn) and then use the multiplier to increase (summer) or decrease (winter) the calculated run times.
* Document what remote "raw format" is
Add a note explaining that raw format is pulse widths (in microseconds) with sign indicating mark or space. This understanding is based on RemoteReceiverComponent::decode_rmt_, RemoteReceiverComponentStore::gpio_intr and RawDumper::dump.
* Update remote_receiver.rst
* Update remote_receiver.rst
---------
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
* Update ads1115.rst
Edited document title to align with other adc components
* Update ads1115.rst
Increased size of title underlie
* Update ads1115.rst
---------
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
* Update bme280.rst
Small addition - added a sentence in the first para to explain that Forced Mode per datasheet section 3.3 is used for measurement.
* Update bme280.rst
---------
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
* include i2s requirement in docs
mention the requirement for i2s to be set up for this sensor to function
* Update mics_4514.rst
* Update mics_4514.rst
Adding ID reference cos I spent 3 hours trying to find why I got this error
Couldn't find ID 'my_custom_switch'. Please check you have defined an ID with that name in your configuration.
* Update resistance.rst
Spent many hours to figure it out why my NTC reading are incorrect. Found out that ADC readings must be multiplied by 3.3 because built-in voltage divider on ADC pin on some boards.
* Update resistance.rst
* Clarify what IAQ is
Since standards are only for companies that lack a marketing department, I clarified some of the documentation around Bosch's definition of what IAQ means in their universe. There is a lot here and it was taken from their datasheet directly that I provided a link to anyway. I just wanted to include the important stuff to save people from surprises because like me they didn't bother to follow the links. I can remove the b-VOC stuff if it's too much noise, but I thought it clarified to the users what it might be measuring for. I also changed `2` to `₂` in `CO2` for the non-code snippets soothe the emotional damage incurred from doing too many school papers in LaTeX.
* fix table
* Sprinkler docs v2 update
* Correction
* Polishing up
* Fixing some links
* Add 'Understanding the Sprinkler Controller's State' section
* Shorten text in examples
* Fix example, syntax highlighting
* Add divider to action index, other copy tweaks
* Document unit_of_measurement use
Co-authored-by: Your Name <you@example.com>
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>
Co-authored-by: Richard North <rich.north@gmail.com>
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>
Raspberry pico W is supported, but the vanilla raspberry pico clearly is not. After trying "rpipico" as a board this error shows up "Error: Unknown board ID 'rpipico'". It is bit misleading, because from what I know about esphome you cannot just have a device that communicates through USB and doesn't connect to WiFi.
I think it is important to understand that RP2040 isn't like ESP. Every RP2040 board doesn't support esphome, but basically any ESP device can support esphome.
* Update daly_bms.rst
Add a couple of examples of Daly BMS control using uart.write
* Examples of Daly BMS control using uart.write
fixed lint errors
* Examples of Daly BMS control using uart.write
probably fixed lint errors
* Fixed every boot up battery level setup
* Update st7789v.rst
Modified to allow dimmable control of the backlight (using GPIO4)
* Update st7789v.rst
---------
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
I have a Costco Feit A19 that is similar but different. It is actually a RGBCT. I was wondering if we could post it here or otherwise make clear that there are alternate configs for Feit A19 bulbs. Maybe just warning people that there are several models of Feit A19 RGB/white bulbs is enough to not confuse people like me that used the sample code. Also, whoTF makes 2 nearly identical bulbs but with different pinouts WTF is that about, Feit electric?
My change is to the pins of the sm16716 and changing it to an RGBCT bulb.
* Update deep_sleep.rst
Added note to explain that onboard USB chip may interfere with deep sleep.
* Update deep_sleep.rst
Added note to explain potential with deep sleep on some ESP8266
* Update deep_sleep.rst
