Fix Nanoleaf light state propagation after change from home asisstant

[tyriis]

Proposed change

As discussed in #97599 the propagation of the state change is not happening as expected within the nanoleaf integration. the update happens after a regular poll from the coordinator (instead of instant). By calling the integrated self.async_write_ha_state() the on/off toggle is propagated back to home assistant state store.
It still not solve the back propagation from the nanoleaf app, this will be done in another PR.

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: fixes #
• This PR is related to issue: The switch does not correctly reflect the state of the Nanoleaf product in reasonable time #97599
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @milanmeu, @joostlek, mind taking a look at this pull request as it has been labeled with an integration (nanoleaf) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nanoleaf can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign nanoleaf Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[joostlek]

Would it make sense to ask the coordinator to refresh the data instead?

[tyriis]

Would it make sense to ask the coordinator to refresh the data instead?

I am not familiar with home-assistant core logic, is there a drawing (uml) on how it should work? (I copy pasted this from an external integration wich is working pretty well, govee). Do you have a reference? would be great if I can implement it the home assistant way.

[joostlek]

well you can run self.coordinator.async_refresh() and it will automatically fetch new data and updates the light, so maybe that's better than just assuming it went well

[tyriis]

hmm okay, so this is called in the light? will give it a try, thanks for the hint

[tyriis]

I have updated the code, local tests are working well. Light state is reflected after toggle/change via home assistant

[tyriis]

@joostlek any chance to get another review from you? 🙏

[joostlek]

I updated the tests, mostly because we use end-to-end tests and that this integration did have no framework yet. I would be happy if we could add more tests though, but I now made sure that your change is properly tested.