search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.9k stars 498 forks source link

Homeseer user. The deconz ip is always changing from local to standar ip. #848

Closed MattL0 closed 5 years ago

MattL0 commented 5 years ago

Hi , here is the Homeseer log. I do not think this is a Homeseer plugin issues... so i post it here.

capture

MattL0 commented 5 years ago

This is happening with a 5 or 10 minutes interval. it depends

MattL0 commented 5 years ago

I think it is mostly 5 minutes. The 10 minutes interval is surely when I rebooted my system , or deconz, or homeseer, or the homeseer plugin.

MattL0 commented 5 years ago

Seems to be ok with 2.05.40?

Will report

manup commented 5 years ago

I guess when the Websocket runs in a timeout after no events were delivered for some time, the plugin might close the connection?

wvuyk commented 5 years ago

I don't think so from here. The plugin changes IP only based on UPNP calls. I have the impression that when deCONZ runs on the same machine as the plugin UPNP can return both local and network IP? It seems to occur on Linux mainly.

ebaauw commented 5 years ago

The plugin changes IP only based on UPNP calls. Seems to be ok with 2.05.40?

There was an issue that deCONZ would advertise the loopback IP address over UPnP, see https://github.com/dresden-elektronik/deconz-rest-plugin/issues/759#issuecomment-419644087.

MattL0 commented 5 years ago

I tried to remove upnp .maybe it was that..

Get Outlook for iOShttps://aka.ms/o0ukef

From: Erik Baauw notifications@github.com Sent: Friday, October 12, 2018 4:15 AM To: dresden-elektronik/deconz-rest-plugin Cc: MattL0; Author Subject: Re: [dresden-elektronik/deconz-rest-plugin] Homeseer user. The deconz ip is always changing from local to standar ip. (#848)

The plugin changes IP only based on UPNP calls. Seems to be ok with 2.05.40?

There was an issue that deCONZ would advertise the loopback IP address over UPnP, see #759 (comment)https://github.com/dresden-elektronik/deconz-rest-plugin/issues/759#issuecomment-419644087.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/dresden-elektronik/deconz-rest-plugin/issues/848#issuecomment-429244012, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AaOUWQM1ykXvFcmR75hFr0eOLGn4o-d4ks5ukE-igaJpZM4XWtFR.

MattL0 commented 5 years ago

So what should we do?

@manup ?

MattL0 commented 5 years ago

Up .

Is disabling the upnp the only solution?

manup commented 5 years ago

We need to check the upnp code, and maybe just stick to the eth0 interface IP address.

MattL0 commented 5 years ago

Just to be sure. Mine is enp4s0, not eth0

manup commented 5 years ago

Just to be sure. Mine is enp4s0, not eth0

My arch linux box also has a different ethernet name, but it should be simple to filter for the ip prefixes to detect the "right" one.

KodeCR commented 5 years ago

The #817 pull request under discussion might help here, as it updates gwConfig["ipaddress"] once the network has initialised and that is used for the announce, while I believe the current code doesn't update this and just gets the ip-address each time it's needed for a rest-request without updating gwConfig["ipaddress"]/upnp.

stale[bot] commented 5 years ago

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