![]() I have reviewed two other in this repository. To help with the load of incoming pull requests: Untested files have been added to `.coveragerc`. For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description. Open the app, and click on the Microsoft product you need help fixing. Updated by running `python3 -m script.gen_requirements_all`. Microsoft Support and Recovery Assistant can help you fix problems, install, uninstall, activate, and more. New or updated dependencies have been added to `requirements_all.txt`. Updated and included derived files by running: `python3 -m script.hassfest`. The has all fields filled out correctly. Documentation added/updated for [If the code communicates with devices, web services, or third-party tools: If user exposed functionality or configuration variables are added/changed: Tests have been added to verify that the new code works. The code has been formatted using Black (`black -fast homeassistant tests`) There is no commented out code in this PR. **Your PR cannot be merged unless tests pass** The code change is tested and works locally. Code quality improvements to existing code or addition of tests Breaking change (fix/feature causing existing functionality to break) Deprecation (breaking change to happen in the future) New feature (which adds functionality to an existing integration) Bugfix (non-breaking change which fixes an issue) This is now all reduced to using the built-in unique ID matching. There was a bunch of logic matching on hostname and config names to update config entries. It's also causing havoc when a user renames an ESPHome device.Įxisting config entries are automatically migrated the first time they are set up.īasing unique ID on MAC simplifies the config flow code. This is against the rules of Home Assistant. 2021-275, the Alabama Board of Nursing began permitting and regulating the practice of. Previously it used the configuration name which is a user provided name. Use the MAC address of the board running ESPHome as the unique ID of the config entry. It's no longer possible to take a device down, reflash the config to a new device, and have the new device "become" the old device inside HA. Technically not a breaking change but I am going to mention it anyway, just in case: # Anything in the logs that might be useful for us? # Link to integration documentation on our website # What type of installation are you running? # What was the last working version of Home Assistant Core? ![]() # What version of Home Assistant Core has the issue? But now the iBeacon source attribute represents the MAC address of my ESP device.Īlso, is there a convention that the mac address should be upper or lower case? As the ESPs give their mac address in lowercase and my Raspberry Pi in upper case Until recent the iBeacon source attribute represented the name of my ESP device, for instance kitchen-esp32 or livingroom-esp32. I'm using the iBeacon integration with my Android phone as an i … Beacon and ESP32 BLE proxies in each room.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |