Fix Islamic prayer sensor timestamp format

[engrbm87]

Proposed change

Add timezone info to sensor timestamp.

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)
• 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 Prayer times not showing up correctly on mobile but correctly on all other web/desktop platforms #35053
• This PR is related to issue:
• Link to documentation 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
• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

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

[MartinHjelmare]

Looks good!

[MartinHjelmare]

Should this go in a patch release?

[engrbm87]

Currently only the ios mobile application is showing wrong time. Android app and the web browser are working fine.

[talondnb]

This seems to have broken the times for me.

I've tried removing integration and re-adding and also tried changing the calculation method, but still shows the wrong times.

edit: rolling back to 0.109.5 has fixed this for me.

[engrbm87]

This seems to have broken the times for me.

I've tried removing integration and re-adding and also tried changing the calculation method, but still shows the wrong times.

edit: rolling back to 0.109.5 has fixed this for me.

Please submit an issue for tracking. And mention the sensor state value (timestamp)

[webhostsg]

This seems to have broken the times for me.

I've tried removing integration and re-adding and also tried changing the calculation method, but still shows the wrong times.

edit: rolling back to 0.109.5 has fixed this for me.

Same issue for me had to roll back to 0.109.5, sensor showing UTC time instead of the current local time..

[talondnb]

This seems to have broken the times for me.

I've tried removing integration and re-adding and also tried changing the calculation method, but still shows the wrong times.
edit: rolling back to 0.109.5 has fixed this for me.

Same issue for me had to roll back to 0.109.5, sensor showing UTC time instead of the current local time..

Please see home-assistant/home-assistant.io#13361