set scan_interval and add attributes installed version/available version about breaking_changes

[ludeeus]

I'll have a look.

This does not use or configure sensor.version but uses the same library.

[Mariusthvdb]

sure, aware of that.
As just confirmed: taking the integration breaking_changes out, makes the sensor: version show up each 5 minutes. As per design.

making breaking_changes is the cause the per minute update of sensor: version, both showing PyPi as source, and Local.
Hope you can fix this in the integration.
Other option would maybe be to check first if the system already uses the sensor: version, and if yes, use that, and not use a check to PyPi by itself?

[ludeeus]

As just confirmed: taking the integration breaking_changes out, makes the sensor: version show up each 5 minutes. As per design.

No... it is not that sensor you are seeing logging for, it is from the library pyhaversion.

The reason PyPi is used, is that one is first updated when there is a release.

[Mariusthvdb]

ok sorry, worded it incorrectly.
let me just show what is looks like without breaking_changes:

sensor: version shows as it should, each 5 minutes, for both setup checks.

with breaking_changes , it shows as posted in top issue posting.

[ludeeus]

No... That is not sensor.version....

This integration does not change how that sensor (or any sensor) operate.

[Mariusthvdb]

well, what can I say. It does. in my setup.

without integration breaking_changes the log shows:

with integration breaking_changes:

[ludeeus]

And that is not a home assistant sensor that is creating those logs, that is a python library.

[Mariusthvdb]

and it is caused by the integration breaking changes...
have tested 2 extra scenarios:

only breaking_changes installed:

none installed:
nothing showing in the log, so we can be certain no other integration is at the root of this.

[ludeeus]

I'm done with this discussing, you are not getting what I'm saying to you.
If you don't like how it works, don't use it.

I will look into adding a scan_interval option, but I'm not making any promises.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[ludeeus]

scan_interval added here https://github.com/custom-components/breaking_changes/releases/tag/0.3.0

[Mariusthvdb]

thanks for the scan_interval!

tried it as follows:

# https://github.com/custom-components/breaking_changes
breaking_changes:
  scan_interval: 3600

to have it update every hour. Unfortunately it still fires every minute:

[ludeeus]

https://github.com/custom-components/breaking_changes/releases/tag/0.3.1