leonpc

Thanks... I will definitely try this today.!

As I said in the previous post I have been looking for another DHCP server but have not found one yet... I have another trick up my sleeve to try but so far nothing. It seems to change ip addresses every 3-6 hours. If I notice the new address and I reboot eisy it comes up with the address I expect. I assign addresses for 24 hours at a time, so the 3-6 hour timing puzzles me. Also the secondary address is random but it is always within my allocatable address range. Also the DHCP server reports the address with a lease time as if it provided the lease. There is one other thing... I have mentioned it before, but at the time that the ip address change you can see an interesting transaction in the logs: Lease is still valid EISY request an address DHCP server responds with the reserved address EISY decline the address and request another address DHCP server responds with the reserved address EISY decline again Silence for a few seconds A bunch of ARP requests from EISY Silence again for a few A lease request from EISY containing an address that is free the DHCP server response with a lease for that address That whole behavior makes me think there is not a second DHCP server but I would rather make sure. At least I have no issue with networking tools but this one is really stumping me.

I have tried it can it still has not stopped the address swapping from happening. I am at the point where I am running wire-shark on my network searching for a rogue DHCP server. I have not been able to identify one at all. Currently the only device that is swapping id addresses is the EISY. @Michel Kohanim Did you perhaps enable virtual mac addresses with the v6.0.5 update. It is a long shot but I am asking

I can try that... At this point I am willing to try almost anything. Although something interesting I have seen... In pihole when you use the DHCP server it assigns a unique identifier to any of the addresses and try and use that in the futureto speedup assigning addresses. This would take the format of 01:macaddress and when you have multiple network cardsin the same system you may see 02:macaddress:systemid eisy I see the following: ff:b9:02:66:f4:00:01:00:01:2f:95:52:e8:macaddress

Ok... So there is definitely something going with the eisy and it all started after the update to v6.0.5 I have been using the DHCP server on my gateway switch and it worked fine except I ran into a limitation that i could only reserve 64 ip addresses. I figured i could live with that and so did nothing. when this issue with EISY started I started thinking about it again and in essence people higher up in the thread said if address reservation is not working, then it is an issue at the switch. And with the combination of the address roulette and the 64 reservation limitation I decided to pull the trigger and install pi-hole. Even after setting up pi-hole I could see that eisy is still changing addresses even though the address is reserved. Looking in the log I see DHCPdecline errors from eisy. I checked the network and there were no other systems using the address I was trying to assign

Thank you. I did this and will monitor the system over the next couple of days

tazman said: "Is there a chance eisy is switching between wired and wireless or do you have a mesh system where eisy is changing acces points?" It is hard-wired to the main router, so I am not sure if it is switching from wired to wireless but that makes sense. Yes, I do have a mesh network but as i said it is hard wired to the main router so i do not thing it is swithing nodes and it is within 4 ft of the router. I will look further into the switching from wired to wireless. Just not sure why it is doing it now.

Guy said "It sounds like this would be more of an issue with the router. Especially since you configured a reserved DHCP address. When you look in your router's connected devices, does the eisy's MAC address stay the same, even when the IP address changes?" Initially I thought so but I have about 40 reserved ips and the only one changing is eisy. And I only saw this behavior once I updated to 6.0.5 about 2 months ago. I have checked the router and at the time it did not show multiple mac addresses

I know it is recommended to use DHCP to assign an IP address to eisy and that is how I have my eisy setup. In my network gateway I run a DHCP server and there I added an ip address reservation for eisy. This worked really well up until the upgrade to v6.0.5. Since then the ip address on my eisy changes randomly every 15-20 minutes. Very weird... I would not be a big problem because I can get to the Admin Console using the ioX launcher but it breaks connection on the UD mobile app and Polyglot interface. Yes I can work around it but I have been told by my wife that I need to fix the app because it is currently "unusable" and "useless" as far as she is concerned. Is eisy changing it MAC address dynamically and that is why the address reservation is failing? Can I just hard-code the ip address? I tried in the admin console under configuration but it will not allow me to unselect the "Automatic" and then set an IP address

I am sorry I had to step away for a bit but am back in the country now. I uploaded your latest v2.0.14 and now it is connecting to my eisy but it is not creating the nodes for them after discovering them. I notice Lore already uploaded log files. If you need another set I can upload my logs as well but if you do not need it I don't want to overload you.

I have updated my roomba plugin to v2.0.9. However since the update I cannot get the roomba plugin to connect and I cannot get any logs to display.

Thanks will test it and let you know... Appreciate your trouble!

Thanks for the update. I have tried to update the plugin but it never really updated the roomba plugin. Finally just deleted the old one and reinstalled. that worked and now I am running 2.0.8. However when trying to connect the Roomba device I still see the following error in the log: 2025-10-09 22:01:25.678 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: start password discovery 2025-10-09 22:01:25.679 Thread-5 (handleConfigDone) udi_interface INFO roomba-poly:getPassword: Connecting to 10.100.100.142 on port 8883 2025-10-09 22:01:26.150 Thread-5 (handleConfigDone) udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1016)

Noticing that Matter is now in beta I also tried to connect a matter device to my eisy. The device is a tube lamp from LiFX:| Model: LFX/T10L/OP After scanning the QR from the UD Mobile app I get prompted to add the device to an app and I am shown 3 apps on my phone that does support (Google Home, Lifx App, Tuya smart) but UD Mobile is not one of the apps to pick. I get a message to restart the lamp but then only see messages the bluetooth devices without matter was found. I forced an update on the system to see if there are any updates available but it is still the same as from March 2oth: ************ IoX ************ isy-5.9.1_18 Name : isy Version : 5.9.1_18 Installed on : Thu Mar 20 19:21:25 2025 MST Origin : misc/isy I am running UD mobile on Android

Hi Bumbershoot Thanks for pointing out this post. I have tried some of the solutions mentioned in here. I get error message when running these commands. As it is I already had the dev packages installed but tried to install them again just in case those were not updated when upgrading from 5.8.3 to 5.8.4. It goes very quick. I have restarted EISY after that but still no luck.