Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Change IPv4 Address when it is already registered #128

Closed
xvolte opened this issue Dec 7, 2021 · 5 comments
Closed

Can't Change IPv4 Address when it is already registered #128

xvolte opened this issue Dec 7, 2021 · 5 comments
Labels
enhancement New feature or request fixed Upcoming fix/feature already on dev

Comments

@xvolte
Copy link

xvolte commented Dec 7, 2021

Version of the custom_component

meross lan v2.4.2

Configuration

no yaml conf, that is the problem, all was done by the interface "integration"

Describe the bug

I set up all my meross devices couple of months ago, and it worked very well. Thanks for your work.
However, i started segmenting my Lan with VLANS and now i have other ip addresses assigned to the devices.
If there was a way to change manually the ip address that would be awesome, because this way i would not need to change my lovelace card nor my nodered automation, which are all based on the devices entity id.

Can you tell me how to proceed? might be good if there was an option to be able to change the ip of a device once it is configured.

Debug log

It is not a bug, but it is an issue. One could consider this a feature request maybe ? it depends if there is a solution to this already or not

@krahabb krahabb added the enhancement New feature or request label Dec 8, 2021
@krahabb
Copy link
Owner

krahabb commented Dec 8, 2021

Hello @xvolte ,
Yeah this is something I often think of: the ability to change the ip address for an already known device. Up to this point I've always considered an ip change as a device change so I've never considered the ip as an editable property but as an identifier property. You're right anyway there could be some cases where would be benficial to not re.configure the integration from scratch if a device jsut moves to a different ip.
Beside this 'theoretical' consideration I'm scared that allowing editing the ip would need some added logic in meross_lan to check the address change is still related to the same device (identified by its own UUID that is) and so I've always postponed the implementation which itself would be easy in terms of added UI fields.

Thinking of it right now..if not too cumbersome I'd post a patch with some other bug fixing very soon

@unlucio
Copy link

unlucio commented Dec 20, 2021

I suspect I am too "victim" of this issue as I recently revamped my lan and put order in my DHCP changing pretty much all the devices' IP in my network.
Now I'm in this weird situation where the integration seems working fine:
Screenshot 2021-12-20 at 23 09 01
While all the devices and entities are unavailable
Screenshot 2021-12-20 at 23 09 27
and since one of these plugs controls the booster heater in my bathroom I woke up and had to take a shower in 18ºC 🥶

Jokes aside my 1st thought was to remove the integration and add it again, promoting the rediscovery of the devices.
The problem is: there is no remove/delete button and even if I fiscally remove the module from HA (from hacs), as soon as the module is reinstalled I'm back on square one (and frozen butt in the morning).

Please adivese?

@krahabb
Copy link
Owner

krahabb commented Dec 22, 2021

Hello @unlucio ,
I'm sorry for the 'cold' showers ;) and slowly working toward allowing the ip address edit in configuration.
At the moment, deleting the meross_lan folder does not remove the configuration from HA so it is nearly useless.
You can instead remove and readd every single 'integration' entry : not the devices nor the entities.
Just enter a single card (every physical device has 1 integration configuration entry) from the integrations page and, by using the 'dots' menu on the panel hit 'Delete' in order to cleanup the HA configuration from any 'awareness' of the device.
Then you'll be able to either manually add a new intgration configuration for the removed device or wait until discovery does its job (which could never happen at least until you restart HA)

@roberttco
Copy link

Unfortunately deleting the device to remove awareness of it doesn't seem to completely work. I'm looking forward to the fix for this issue...

@krahabb
Copy link
Owner

krahabb commented Feb 15, 2022

The incoming release allows updating the host address in configuration (allowed the device is really the same..else: boom!)

@krahabb krahabb closed this as completed Feb 15, 2022
@krahabb krahabb added the fixed Upcoming fix/feature already on dev label Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fixed Upcoming fix/feature already on dev
Projects
None yet
Development

No branches or pull requests

4 participants