Migrate Flo to new entity naming style

[bachya]

Proposed change

This PR migrates the Flo integration to the new entity naming style.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: N/A
• This PR is related to issue: Add Entity.has_entity_name attribute  #73217
• Link to documentation pull request: N/A

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @dmulcahey, mind taking a look at this pull request as it has been labeled with an integration (flo) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[bachya]

Need to fix tests.

[dmulcahey]

Need to fix tests.

It looks like the change causes entity ids to change. does something else need to be added for backwards compatibility?

[bachya]

It looks like the change causes entity ids to change. does something else need to be added for backwards compatibility?

No – this will just affect new installs of the integration.

[dmulcahey]

Need to fix tests.

It looks like the change causes entity ids to change. does something else need to be added for backwards compatibility?

entity_id = "switch.shutoff_valve"
assert hass.states.get(entity_id).state == STATE_ON
AttributeError: 'NoneType' object has no attribute 'state'

INFO:homeassistant.helpers.entity_registry:Registered new switch.flo entity: switch.smart_water_shutoff_shutoff_valve

[dmulcahey]

It looks like the change causes entity ids to change. does something else need to be added for backwards compatibility?

No – this will just affect new installs of the integration.

then all of the entity ids in the tests need to be adjusted.

[bachya]

Yep, already on it. 👍

[frenck]

Thanks, @bachya 👍