1.5.2

Changelog for custom_components/ipv64 version 1.5.2

Added

• Added a default value for the ip_is_changed variable in the _async_update_data method to ensure that the IP address is updated by default if not in economy mode.

Changed

• Updated the check_ip_equal method to return a boolean value indicating whether the IP address has changed or not.

Info

• Updated the version to 1.5.2 in the custom_components/ipv64/manifest.json.

These changes improve the behavior when the economy option is not present in the service call data, ensuring that the IP address is updated by default. The version has been updated to 1.5.2 to reflect these changes.

What's Changed

• 🚑 add default by @Ludy87 in #26

Full Changelog: 1.5.1...1.5.2

1.5.1

Changes in version 1.5.1

Added

• A new option economy in the refresh service, allowing users to enable economy mode to conserve API key usage by updating the IP address only when it changes.

Changed

• custom_components/ipv64/__init__.py

  • Updated the async_update function to accept a ServiceCall argument, allowing for a new option to be passed.
  • Added logic to check if the economy option is present in the service call data and then use it in the _async_update_data method accordingly.

• custom_components/ipv64/coordinator.py

  • Updated the async_update method to accept a ServiceCall argument, which is used to determine whether to use economy mode or not.
  • Added a new method check_ip_equal to check if the IP address has changed or not.
  • Modified _async_update_data to use the new check_ip_equal method when economy mode is enabled, ensuring that the IP address is updated only if it has changed.

• custom_components/ipv64/strings.json

  • Updated translations for the new refresh service and its economy field.

Info

• custom_components/ipv64/manifest.json

  • Updated the version to 1.5.1.

• custom_components/ipv64/services.yaml

  • Added a new field economy to the refresh service, which is a boolean selector.

Removed

• No items were removed in this version.

These changes introduce a new option economy in the refresh service, which allows users to enable economy mode to conserve API key usage by updating the IP address only when it changes. The version has been updated to 1.5.1 to reflect these changes.

What's Changed

• 🔨 Update hacs.json file by <github-actions[bot]> by @github-actions in #24
• add refresh service by @Ludy87 in #25

Full Changelog: 1.5.0...1.5.1

1.5.0

What's Changed

• Bump github/codeql-action from 2.21.0 to 2.21.2 by @dependabot in #20
• Bump svenstaro/upload-release-action from 2.6.1 to 2.7.0 by @dependabot in #21
• 🔨 Update hacs.json file by <github-actions[bot]> by @github-actions in #22
• add service - refresh ip address by @Ludy87 in #23

Added

• Added a new service called "refresh" to refresh the IP address.

Changed

• Updated the "get_version.py" script to use UTF-8 encoding when reading the manifest.json file.
• Updated the "config_flow.py" file to improve exception handling and error messages.
• Updated the "coordinator.py" file to include a new method "_async_update_data" to update data from the IPv64.net API and use the "refresh" service to update the IP address.
• Updated the "sensor.py" file to use type hints and improve attribute handling.

Removed

• Removed the "scripts/update/hacs.py" file.

Full Changelog: 1.4.0...1.5.0

1.4.0

Changes in version 1.4.0 :

1. Updated the API key and token labels in the "config_flow.py" and "coordinator.py" files to ensure the use of consistent labels.

Details of Changes:

• In the "config_flow.py" file, the label CONF_TOKEN has been replaced with CONF_API_KEY to correctly use the API key.

• In the "coordinator.py" file, the label CONF_TOKEN has also been replaced with CONF_API_KEY to correctly use the API key.

---

🚨 Step 1: Disable the Integration 🚨

1. Navigate to the user interface of your application or platform where the integration is set up.
2. Go to the settings or configuration area where integrations are managed.
3. Find the relevant integration and temporarily disable it, if possible.

🚨 Step 2: Remove the Integration 🚨

1. Go to the settings or the list of installed integrations in your application.
2. Locate the integration that needs to be reconfigured.
3. Select the option to "Delete" or "Remove" the integration. Confirm the action when prompted. This will delete all configuration data and settings related to the integration.

🚨 Step 3: Reconfigure the Integration 🚨

1. After removing the previous integration, navigate to the page or section to set up a new integration.
2. Choose the option to "Add" or "Add New" the integration.
3. Follow the instructions to reconfigure the integration. You may need to enter login credentials, API keys, or other information required for the integration.
4. Save the new settings and wait for the integration to be successfully configured.

🚨 Step 4: Verification and Testing 🚨

1. After reconfiguring, verify the functionality of the integration to ensure it is working correctly.
2. Perform any necessary tests to ensure that the integration functions as expected and interacts properly with other components or services.

By following these steps, you can remove the integration and then set it up again from scratch. Note that after deleting the integration, some previous settings may be lost, so it's advisable to create a backup of relevant data before deletion if possible.

---

🚨Schritt 1: Deaktivieren der Integration 🚨

1. Navigiere zur Benutzeroberfläche deiner Anwendung oder Plattform, auf der die Integration eingerichtet wurde.
2. Gehe zu den Einstellungen oder Konfigurationsbereich, wo die Integration verwaltet wird.
3. Suche nach der entsprechenden Integration und deaktiviere sie vorübergehend, falls möglich.

🚨Schritt 2: Entfernen der Integration 🚨

1. Gehe zu den Einstellungen oder der Liste der installierten Integrationen in deiner Anwendung.
2. Suche nach der betreffenden Integration, die neu eingerichtet werden soll.
3. Wähle die Option zum Löschen oder Entfernen der Integration aus. Bestätige die Aktion, wenn du dazu aufgefordert wirst. Dadurch werden alle Konfigurationsdaten und Einstellungen der Integration gelöscht.

🚨Schritt 3: Neue Einrichtung der Integration 🚨

1. Nachdem die vorherige Integration gelöscht wurde, navigiere zur Seite oder dem Bereich, um eine neue Integration einzurichten.
2. Wähle die Option zum "Hinzufügen" oder "Neu hinzufügen" der Integration aus.
3. Befolge die Anweisungen, um die Integration erneut einzurichten. Dabei musst du möglicherweise Anmeldedaten, API-Schlüssel oder andere Informationen eingeben, die für die Integration erforderlich sind.
4. Speichere die neuen Einstellungen und warte, bis die Integration erfolgreich eingerichtet ist.

🚨Schritt 4: Überprüfung und Tests 🚨

1. Nach der erneuten Einrichtung solltest du die Funktionalität der Integration überprüfen, um sicherzustellen, dass sie ordnungsgemäß funktioniert.
2. Führe eventuell notwendige Tests durch, um sicherzustellen, dass die Integration wie erwartet arbeitet und mit anderen Komponenten oder Diensten richtig interagiert.

Indem du diese Schritte befolgst, kannst du die Integration entfernen und sie anschließend wieder von Grund auf einrichten. Beachte, dass nach dem Löschen der Integration möglicherweise einige vorherige Einstellungen verloren gehen, weshalb es ratsam ist, vor dem Löschen eine Sicherungskopie der relevanten Daten zu erstellen, falls dies möglich ist.

What's Changed

• Bump github/codeql-action from 2.20.4 to 2.21.0 by @dependabot in #16
• 🔨 Update hacs.json file by <github-actions[bot]> by @github-actions in #17
• 🐛 change api_key and token by @Ludy87 in #18

Full Changelog: 1.3.1...1.4.0

1.3.1

What's Changed

• 🔨 Update hacs.json file by @github-actions in #7
• Bump github/codeql-action from 2.20.1 to 2.20.2 by @dependabot in #8
• Bump github/codeql-action from 2.20.2 to 2.20.3 by @dependabot in #10
• Bump actions/setup-python from 4.6.1 to 4.7.0 by @dependabot in #12
• Bump github/codeql-action from 2.20.3 to 2.20.4 by @dependabot in #14
• 🔨 Update hacs.json file by <github-actions[bot]> by @github-actions in #15

New Contributors

• @github-actions made their first contribution in #7

Full Changelog: 1.3.0...1.3.1

1.3.0

Changelog

Added

• Added .github/workflows/stale.yml workflow file for stale issue and pull request management.
• Added .github/workflows/update_hacs.yml workflow file for daily updates and creating pull requests for the hacs.json file.
• Added new constants CONF_DAILY_UPDATE_LIMIT, CONF_DYNDNS_UPDATE_TODAY, CONF_DYNDNS_UPDATES, and CONF_WILDCARD in custom_components/ipv64/const.py.
• Added new functionality to retrieve account information and domain data in custom_components/ipv64/coordinator.py.
• Added new subdomains data to the domain result in custom_components/ipv64/coordinator.py.
• Imported constants have been rearranged and added: CONF_DAILY_UPDATE_LIMIT, CONF_DYNDNS_UPDATES in custom_components/ipv64/config_flow.py.

Changed

• Updated the logic to handle account information and domain data in custom_components/ipv64/coordinator.py.
• Updated the stale policy for PRs to close after 7 days of inactivity in .github/workflows/stale.yml.
• Updated the message for stale issues and pull requests in .github/workflows/stale.yml.
• Updated the check IP URL to use CHECKIP_URL constant in custom_components/ipv64/coordinator.py.
• The constant CONF_API_KEY in custom_components/ipv64/const.py has been marked as Final type.
• The constant CONF_API_ECONOMY in custom_components/ipv64/const.py has been marked as Final type.
• The constant DOMAIN in custom_components/ipv64/const.py has been marked as Final type.
• New constant DEFAULT_INTERVAL has been added to custom_components/ipv64/const.py.
• The data schema DATA_SCHEMA in custom_components/ipv64/const.py has been updated accordingly.
• Imported constants have been rearranged and added: CHECKIP_URL, CONF_DAILY_UPDATE_LIMIT, CONF_DYNDNS_UPDATE_TODAY, CONF_DYNDNS_UPDATES, CONF_WILDCARD in custom_components/ipv64/coordinator.py.

Fixed

• Fixed a syntax error in custom_components/ipv64/config_flow.py.
• Fixed a missing import statement for CHECKIP_URL constant in custom_components/ipv64/coordinator.py.
• Fixed an exception handling issue in custom_components/ipv64/coordinator.py.

Updated

• Updated manifest.json version from "1.2.0" to "1.3.0".
• Added IPv64SubSensor class to sensor.py to support subdomain sensors.
• Updated async_setup_entry function in sensor.py to add subdomain sensors if corresponding data is available.

These changes result in improved functionality and support for subdomains in the IPv64 component.

Full Changelog: 1.2.0...1.3.0

1.2.0

What's Changed

• ✨ add api key economy by @Ludy87 in #5

Full Changelog: 1.1.2...1.2.0

1.1.2

What's Changed

• 🐛 fix trigger update by @Ludy87 in #4

Full Changelog: 1.1.1...1.1.2

1.1.1

Full Changelog: 1.1.0...1.1.1

1.1.0

What's Changed

• Bump github/codeql-action from 2.20.0 to 2.20.1 by @dependabot in #1
• ✅ add show dyndns_update_limit by @Ludy87 in #2

New Contributors

• @dependabot made their first contribution in #1
• @Ludy87 made their first contribution in #2

Full Changelog: 1.0.0...1.1.0