IPv64.net | Free DynDNS2 & Healthcheck Service | Integration for Home-Assistant
What is IPv64.net?
IPv64 is of course not a new Internet Protocol (64), but simply a deduplicated short form of IPv6 and IPv4. On the IPv64 site you will find a Dynamic DNS service (DynDNS) and many other useful tools for your daily internet experience.
With the dynamic DNS service of IPv64 you can register and use free subdomains. The update of the domain is done automatically by your own router or alternative hardware / software. Besides updating IP addresses, simple Let's Encrypt DNS challenges are also possible.
Own domains can be added and benefit from all IPv64.net features like DynDNS services, GEO load balancing, DDoS protection, DynDNS2 and SSL encryption.
You need an Account Update Token and an API key to access the IPv64.net API.
Copy the ipv64 last Release folder and all of its contents into your Home Assistant's custom_components folder. This folder is usually inside your /config folder. If you are running Hass.io, use SAMBA to copy the folder over. If you are running Home Assistant Supervised, the custom_components folder might be located at /usr/share/hassio/homeassistant. You may need to create the custom_components folder and then copy the localtuya folder and all of its contents into it Alternatively, you can install localtuya through HACS by adding this repository.
- Ensure that HACS is installed.
- Search for and install the "ipv64 Integration" integration.
- Configuration for the
ipv64
integration is now performed via a config flow as opposed to yaml configuration file. - Restart Home Assistant.
- Go to HACS -> Integrations -> Click "+"
- Search for "ipv64" repository and add to HACS
- Restart Home Assistant when it says to.
- In Home Assistant, go to Configuration -> Integrations -> Click "+ Add Integration"
- Search for "ipv64" and follow the instructions to setup.
ipv64 should now appear as a card under the HA Integrations page with "Configure" selection available at the bottom of the card.
There is a switch to prevent the API key (default: 64) from being used up. The last IP address and the current IP address are compared (https://checkip.amazonaws.com/), if it is negative, the IP update function of IPv64.net is called.
logger:
logs:
custom_components.ipv64: debug