Canada, Latin America, Europe, Africa. You don't have to go to Asia to have non ASCII characters in daily usage that are multibye characters in UTF-8. Even in Europe you can find 100% multibyte alphabets like Cyrillic or Greek. It's the norm, not the exception. Chances that byte 255 is half of a multibye character is certainly below 50%, but still quite probable.

From a US point of view, that 99.9% may be true, but the world uses multibyte. And maybe even inside the US. At least when most Apple users type a hyphen, that‘s not 0x2D but some multibyte thing.

@geiseri something like https://github.com/esphome/esphome/compare/dev...nohn:esphome:remove_incomplete_multibyte_chars_from_wifi_info?

implement pairing for bluetooth proxy (#4475)

• default to just-works encryption

This patch will turn on encryption when making active connections in order to comply with just-works BLE encryption.

• Revert "default to just-works encryption"

This reverts commit 05bc9e9f1cca9c41cbc7434379cbd5eb6dbb1034.

• implement pair method

• adhere to clang formatter

• fix oopsie

• bump bluetooth_proxy_version

• add auth callback

• generate new protos

• fix another oopsie

• add pairing status to connection

• clear paired on connect()

• lint

• add unpair ("forget") ble method

• compile protos

• fix oopsie

• add missing unpairing method

• add unpairing

• fix get_paired return type

• remove unused memcpy

Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

• change to is_paired

Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

• Update bluetooth_proxy.cpp

• actually add missing method

• send auth cb on set_encryption failure

• cleanup from havin the worst test setup

• lint

• match auth events to bd_addr

• add second addr check to auth cb

• add addr check to third auth cb

Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

Bump docker dependencies (#4526)

• Bump curl to 7.74.0-1.3+deb11u7

• Bump docker base images

Bump aioesphomeapi from 13.4.0 to 13.5.0 (#4525)

Bumps aioesphomeapi from 13.4.0 to 13.5.0.

• Release notes
• Commits

updated-dependencies:

• dependency-name: aioesphomeapi dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Ensure component is ready before update. (#4523)

Co-authored-by: Your Name you@example.com

climate: add on_control callbacks (#4511)

This lets downstream components respond to climate configuration changes, which take place through ClimateCall objects, without also being notified every time the state changes, which happens every time the input sensor announces a new value.

FIXES https://github.com/esphome/feature-requests/issues/2136

FS3000 sensor (#4502)

• Add support for FS3000 sensor.

• add fs3000 to test yaml

• Clean up code with clang.

• Clean up sensor.py file.

• Update CODEOWNERS file.

• Apply suggestions from code review regarding sensor.py

Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

• Apply suggestions from code review for basic issues regarding C++ code

• removed unnecessary default for FS3000Model
• use "this->" before any sensor update

Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

• Move model setup to overall setup function.

• Remove unneeded CONF_ID from sensor.py

• Run clang-format

• Move set_model code to header file now that it is simplified

• Update fs3000.h

Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

Bump esptool from 4.5 to 4.5.1 (#4497)

Bumps esptool from 4.5 to 4.5.1.

• Release notes
• Commits

updated-dependencies:

• dependency-name: esptool dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Add support for multiple devices in bme680_bsec (#3550)

• Add initial support for multiple devices

Re-introduce support for multiple I2C devices (it was suppressed in https://github.com/trvrnrth/esphome-bsec-bme680/commit/df37a7635f6acc3f7520f257d2645eda10b863a5). Devices are identified by their I2C address, and the BME680 can only have the 0x76 or 0x77 address, so this adds support for a maximum of two devices.

• Reintegrate commit ebf13a0b

Reintegrate commit https://github.com/esphome/esphome/commit/ebf13a0ba0a48453c2cc80bfc942d6a588859233 which was lost in my changes (I were working on old files)

• wrong commit

• wrong commit

• Reintegrate commit ebf13a0b

Reintegrate commit https://github.com/esphome/esphome/commit/ebf13a0ba0a48453c2cc80bfc942d6a588859233 which was lost due to me working on old files

• Reintroduce newlines at end of files

• Reintroduce newlines at end of files

• Adhere to codebase standards

Obey the "All uses of class members and member functions should be prefixed with this-> to distinguish them from global functions in code review" rule of the Codebase Standards

• Fix formatting according to clang-format

• Perform the BSEC library reinitialization+snapshot only when more than one device is present

• Fix formatting according to clang-format

• Degrade abort message in restore_state_() from warning to verbose

This always happen at initial setup, so it's not a really useful message; when some real problems arise, we'll have a more useful warning from snapshot_state_()

Co-authored-by: Trevor North trevor@freedisc.co.uk

• Reduce peak stack usage to avoid bootloops on ESP8266

Achieved mainly by moving the work_buffer needed by the BSEC library to the heap, as a single global work buffer shared by all instances. ::set_config_ has been reverted to a code path similar to the original, as that reduces peak stack usage enough to be OK on ESP8266 even without moving the work_buffer to the heap.

• Fix formatting according to clang-format

• Add support for devices with the same i2c address

Devices are now identified using their index in the BME680BSECComponent::instances member, which became a vector. This allows adding two devices with the same i2c address (which should be placed on different i2c buses). Since a BME680 can only have an address of 0x76 or 0x77, a maximum of 2 devices could be added before this commit. Now there is no theoretical limit on the number of devices which could be added.

• Fix formatting according to clang-format

• Fix formatting according to clang-format

Co-authored-by: Trevor North trevor@freedisc.co.uk Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

Bump pytest from 7.2.1 to 7.2.2 (#4505)

Bumps pytest from 7.2.1 to 7.2.2.

• Release notes
• Changelog
• Commits

updated-dependencies:

• dependency-name: pytest dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

Bump pylint from 2.16.2 to 2.16.4 (#4524)

Bumps pylint from 2.16.2 to 2.16.4.

• Release notes
• Commits

updated-dependencies:

• dependency-name: pylint dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Merge branch 'esphome:dev' into remove_incomplete_multibyte_chars_from_wifi_info

Bump version to 2022.2.4

Merge pull request #3245 from esphome/bump-2022.2.4

2022.2.4

Add support for MPU-6886 (#3183)

light: add RESTORE_AND_OFF/RESTORE_AND_ON LightRestoreMode (#3238)

Implement send_first_at for exponential_moving_average (#3240)

Respect ESPHOME_USE_SUBPROCESS in esp32 post_build script (#3246)

Add device support: MCP4728 (#3174)

• Added MCP4728 output component.

• Added tests to test1.yaml

• Added codeowners

• Lint fixes

• Implemented code review changes

• Lint fixes

• Added i2c communication check on setup()

• Fixed tests

• Lint fix

• Update esphome/components/mcp4728/mcp4728_output.cpp

Changed log function

Co-authored-by: Otto Winter otto@otto-winter.com

Co-authored-by: Otto Winter otto@otto-winter.com

support for waveshare 7.50in-hd-b (#3239)

Fix template button after abstract press_action (#3250)

Fix regression caused by TSL2591 auto gain (#3249)

Store platform as uppercase (#3251)

Add sensor support: Honeywell ABP (SPI version) (#3164)

Co-authored-by: RubyBailey ruby_bailey11@hotmail.com

Add optional display page for touchscreen binary sensors (#3247)

Respect ESPHOME_USE_SUBPROCESS in esp32 post_build script (#3246)

Fix regression caused by TSL2591 auto gain (#3249)

Bump version to 2022.2.5

Merge pull request #3252 from esphome/bump-2022.2.5

2022.2.5

Add Mopeka BLE and Mopeka Pro Check BLE Sensor (#2618)

Co-authored-by: Jesse Hills 3060199+jesserockz@users.noreply.github.com

Remove stray define (#3260)

Only get free memory size from internal (#3259)

Problem is likely the use of string.substr in https://github.com/esphome/esphome/blob/df3f13ded884682dfbcbba542d79aedb1e100b0a/esphome/components/wifi_info/wifi_info_text_sensor.h#L45.

string.substr is not aware of multibyte-charsets.

See also https://github.com/home-assistant/core/issues/88431

remove wifi_info sensor.

No. Device- and hostnames are all ASCII only. As described, the problem is a Wifi network having umlauts -https://en.m.wikipedia.org/wiki/Umlaut_(diacritic) - in it's SSID.

The problem

My ESPs use the wifi_info sensors like this: https://github.com/nohn/esphome-configs/blob/main/templates/sensors/wifi_info.yaml

One of the WLANs in vincinity of the ESPs uses umlauts in their SSID.

This results in the home assistant log being flodded (161257 times in 19 hours) with UTF-8 decoding errors:

2023-02-19 06:03:36.943 WARNING (MainThread) [aioesphomeapi.connection] schlafzimmer-fenster-s-particle @ 192.168.99.55: Connection error occurred: Invalid protobuf message: type=27 data=b'\r\x9c85}\x12\xff\x01sebetti-smarthome: -89dB\nsebetti-smarthome: -90dB\nsebetti-smarthome: -91dB\nJ.A.R.V.I.S: -72dB\nHackest\xc3\xbcpp: -81dB\nsebetti-psk: -82dB\nVodafone 1407: -85dB\nDIRECT-C5-HP OfficeJet 3830: -86dB\nVodafone 1407: -88dB\nWLAN-FCYRT2: -90dB\nsebetti-psk: -90dB\nHackest\xc3': 'utf-8' codec can't decode byte 0xc3 in position 254: 'utf-8' codec can't decode byte 0xc3 in position 254: unexpected end of data in field: TextSensorStateResponse.state
2023-02-19 06:03:36.947 ERROR (MainThread) [homeassistant] Error doing job: Fatal error: protocol.data_received() call failed.
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 868, in _read_ready__data_received
    self._protocol.data_received(data)
  File "/usr/local/lib/python3.10/site-packages/aioesphomeapi/_frame_helper.py", line 195, in data_received
    self._callback_packet(msg_type_int, bytes(packet_data))
  File "/usr/local/lib/python3.10/site-packages/aioesphomeapi/_frame_helper.py", line 110, in _callback_packet
    self._on_pkt(Packet(type_, data))
  File "/usr/local/lib/python3.10/site-packages/aioesphomeapi/connection.py", line 602, in _process_packet
    msg.MergeFromString(pkt.data)
  File "/usr/local/lib/python3.10/site-packages/google/protobuf/internal/python_message.py", line 1128, in MergeFromString
    if self._InternalParse(serialized, 0, length) != length:
  File "/usr/local/lib/python3.10/site-packages/google/protobuf/internal/python_message.py", line 1195, in InternalParse
    pos = field_decoder(buffer, new_pos, end, self, field_dict)
  File "/usr/local/lib/python3.10/site-packages/google/protobuf/internal/decoder.py", line 591, in DecodeField
    field_dict[key] = _ConvertToUnicode(buffer[pos:new_pos])
  File "/usr/local/lib/python3.10/site-packages/google/protobuf/internal/decoder.py", line 553, in _ConvertToUnicode
    value = str(byte_str, 'utf-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 254: 'utf-8' codec can't decode byte 0xc3 in position 254: unexpected end of data in field: TextSensorStateResponse.state

What version of Home Assistant Core has the issue?

core-2023.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

ESPHome

Link to integration documentation on our website

https://www.home-assistant.io/integrations/esphome

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Bump php from 8.2.1-cli to 8.2.2-cli

Bumps php from 8.2.1-cli to 8.2.2-cli.

updated-dependencies:

• dependency-name: php dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #95 from nohn/dependabot/docker/php-8.2.2-cli

Bump php from 8.2.1-cli to 8.2.2-cli

Bump php from 8.2.2-cli to 8.2.3-cli

Bumps php from 8.2.2-cli to 8.2.3-cli.

updated-dependencies:

• dependency-name: php dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #96 from nohn/dependabot/docker/php-8.2.3-cli

Bump php from 8.2.2-cli to 8.2.3-cli

prepare v1.2.20

prepare v1.2.20

Bump php from 8.2.2-cli to 8.2.3-cli

Bumps php from 8.2.2-cli to 8.2.3-cli.

updated-dependencies:

• dependency-name: php dependency-type: direct:production update-type: version-update:semver-patch ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #96 from nohn/dependabot/docker/php-8.2.3-cli

Bump php from 8.2.2-cli to 8.2.3-cli

Bumps php from 8.2.2-cli to 8.2.3-cli.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

refactor

The problem

When trying to configure a Wireless Client Reconnect service as per https://www.home-assistant.io/integrations/unifi/#service-unifireconnect_client, the drop down in automation UI lists my UniFi access points and switches, not my configured clients:

What version of Home Assistant Core has the issue?

core-2023.2.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Unifi

Link to integration documentation on our website

https://www.home-assistant.io/integrations/unifi

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Bullseye non-support and omxplayer deprecation

Update README.md

Merge branch 'Anonymousdog:master' into master

cleanup & reduce update interval to 10s

fix links in README