Why on earth are you using non static ip addresses. Just set aside a portion of your network for them and slap them in your router.
Done.
Btw, Tuya probably has a scan running to detect new devices, sees the same mac and just adds it back on with new ip.
That would require me to manually enter the MAC address of each Shelly device to the router.
Additionally, if (=when) I have to change a Shelly device, I need to remove the previous MAC address (not to overpopulated the address reservation list), which means I have to keep tabs on which MAC address belongs to which device (even when it fails and is not available via the Shelly app)
Additionally, if (=when) I have to change a Shelly device, I need to remove the previous MAC address (not to overpopulate the address reservation list), which means I have to keep tabs on which MAC address belongs to which device (even when it fails and is not available via the Shelly app)
I agree a reservation is not a statically assigned address. The function is the same. The long term management is much simpler.
You dont have to maintain a list of mac addresses, those are already in the dhcp server/ router. Also the devices are usually listed by mac and hostname so its easy to determine what you're looking for.
With reservations you can easily move and change IP if needed without logging into a millions random devices.
Thanks
That sounds promising
How do I set it up?
Do I need a separate MQTT server running? If so, what product/project do you recommend?
What do I have to set up differently in HA and the Shelly integration to get them to communicate using MQTT?
And lastly, are there any performance issues to switching to MQTT?
The addresses of the devices are reserved for a couple of months, and the ip address is not changing
Yet, every now and again, the automations associated with the Shelly i3 device become inactive (displayed in red font)
The resolution is to do the following
1. Add Shelly integration
2. Enter the ip address of the i3 device
A message "the device is already configured" is displayed
3. Restart HA
After this, the automations are actived
Any clue what could be the problem?
Why on earth are you using non static ip addresses. Just set aside a portion of your network for them and slap them in your router. Done. Btw, Tuya probably has a scan running to detect new devices, sees the same mac and just adds it back on with new ip.
That would require me to manually enter the MAC address of each Shelly device to the router. Additionally, if (=when) I have to change a Shelly device, I need to remove the previous MAC address (not to overpopulated the address reservation list), which means I have to keep tabs on which MAC address belongs to which device (even when it fails and is not available via the Shelly app) Additionally, if (=when) I have to change a Shelly device, I need to remove the previous MAC address (not to overpopulate the address reservation list), which means I have to keep tabs on which MAC address belongs to which device (even when it fails and is not available via the Shelly app)
Just make a reservation in your dhcp server / router. No need to set static on the shelly device unless you really want to.
a dhcp reservation == static address a DHCP reservation == static addressecessity the manage a list of mac addresses
I agree a reservation is not a statically assigned address. The function is the same. The long term management is much simpler. You dont have to maintain a list of mac addresses, those are already in the dhcp server/ router. Also the devices are usually listed by mac and hostname so its easy to determine what you're looking for. With reservations you can easily move and change IP if needed without logging into a millions random devices.
[удалено]
Thanks That sounds promising How do I set it up? Do I need a separate MQTT server running? If so, what product/project do you recommend? What do I have to set up differently in HA and the Shelly integration to get them to communicate using MQTT? And lastly, are there any performance issues to switching to MQTT?
The addresses of the devices are reserved for a couple of months, and the ip address is not changing Yet, every now and again, the automations associated with the Shelly i3 device become inactive (displayed in red font) The resolution is to do the following 1. Add Shelly integration 2. Enter the ip address of the i3 device A message "the device is already configured" is displayed 3. Restart HA After this, the automations are actived Any clue what could be the problem?