bradshawkyle Posted January 30, 2023 Share Posted January 30, 2023 I just installed the trial and cannot s=seem to discover any devices. Node server is connected, showing 1 node on PG3 and eISY, and I've tried Discover on both. Any suggestions to get my devices discovered? Link to comment
Jimbo.Automates Posted January 31, 2023 Share Posted January 31, 2023 Is your eisy using only a wired Ethernet connection? And is it on the same LAN? Some have segmented their lan which causes discover to fail.Sent from my Pixel 6 Pro using Tapatalk 1 Link to comment
bradshawkyle Posted January 31, 2023 Author Share Posted January 31, 2023 4 hours ago, Jimbo.Automates said: Is your eisy using only a wired Ethernet connection? And is it on the same LAN? Some have segmented their lan which causes discover to fail. Sent from my Pixel 6 Pro using Tapatalk The smart bulbs are on a 2.4gHz network, eISY was wireless on 5gHz. I've read about people having problems accessing devices on the same network, but different bands. Just to be safe, I moved eISY to 2.4, reinstalled the node server, but no luck. I'm currently running the Honeywell Home node server to access two wireless thermostats with no problems. Link to comment
Jimbo.Automates Posted January 31, 2023 Share Posted January 31, 2023 Yes, but does the Honeywell NS use a discovery to find thermostats or are they manually entered? There was/is a problem with the way an IP address is defined on eisy when using WiFi which causes problems for some NS like this one. Please download log package and PM it to me and also let me know the IP address of one Kasa device.Sent from my Pixel 6 Pro using Tapatalk Link to comment
bradshawkyle Posted January 31, 2023 Author Share Posted January 31, 2023 2 hours ago, Jimbo.Automates said: Yes, but does the Honeywell NS use a discovery to find thermostats or are they manually entered? There was/is a problem with the way an IP address is defined on eisy when using WiFi which causes problems for some NS like this one. Please download log package and PM it to me and also let me know the IP address of one Kasa device. Sent from my Pixel 6 Pro using Tapatalk Goo d point on how Honeywell is configured, you point the Node Server to an API you have to create on the Honeywell side. I forgot about that. IP address for one Kasa device is 10.0.5.87. Log file is attached. Also, thank you very much for your help! Kasa_1-31-2023_84102-AM.zip Link to comment
Jimbo.Automates Posted January 31, 2023 Share Posted January 31, 2023 Sorry, can you change the node server log level to debug, restart wait of couple minutes then download another log package? It's best to just PM it to me and not post on the forum. 1 Link to comment
bradshawkyle Posted January 31, 2023 Author Share Posted January 31, 2023 20 minutes ago, Jimbo.Automates said: Sorry, can you change the node server log level to debug, restart wait of couple minutes then download another log package? It's best to just PM it to me and not post on the forum. Thanks again, PM sent. Link to comment
Solution bradshawkyle Posted January 31, 2023 Author Solution Share Posted January 31, 2023 It seems that moving eISY to the 2.4Ghz band and restarting several times did the trick. This is a GREAT Node Server! Just converted my trial to a purchase - thank @Jimbo.Automates for all your help! 1 Link to comment
tlightne Posted January 31, 2023 Share Posted January 31, 2023 @bradshawkyle I am considering moving from a Nest to a Honeywell thermostat. What model Honeywell Home are you using? Thanks... Link to comment
Recommended Posts