bradshawkyle

I tried that first and ran into sone strange behavior. I couldn't access via Admin Console, PG3 disconnected, no UD Mobile, BUT I could see and control devices via ISY Portal. I looked around for a post explaining how to configure Ethernet and could only find instructions to "plug it in and wireless is disabled". And ideas how to resolve? If not, I guess I could back-up, factory reset, and configure eISY with Ethernet instead of Wifi. Seems kinda of extreme, though..... That said, I'm willing to go that route if I can get things working properly.

Like the title says, I can't seem to get the Node Server to discover my devices. It's worth noting they're running the S1 app (not the newer S2) as some of my devices are 1st Gen Sonos. I have some ZP100's and ZP80's that still work perfectly at 15+ years. The devices are on wifi (not currently using the Bridge) and eISY is on the same 2.4GhZ network. I've tried reinstalling the Node Server and restarting eISY, along with clicking Discover in PG3 and in Admin console, and the Node Server shows connected in both places as well. Any troubleshooting tips would be greatly appreciated.

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!

Thanks again, PM sent.

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

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.

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?

@bpwwer You question got me thinking....I tried upgrading my eISY when I first got it and wasn't successful. I haven't tried again until just now...upgrade ran this time, and I am now able to reinstall the trial. Thanks for the help! The bummer now is I only have 1 day left on the trial.

I'm attempting to install the trial and keep getting a "Can't find purchase option for license record" error - any ideas what I need to do to get the trial working?

Update: deleting all notification configurations resolved the issue immediately. Before deleting, I tested the text notifications and they worked instantly, with no delay. I went ahead and deleted them and ran with none for 2 weeks, then email only until this weekend. Emails worked fine. I added text notifications back in, tested fine, but today the same issues came back: receiving notification texts from events occurring at 8am multiple times and up to 12 hours late. I deleted all text notification data about an hour ago and just received a text from this morning's notification. They'll stop eventually. I have decided to ditch the text message notifications entirely, use the (character limited) push notification feature in Mobilnc to alert me, then send the details in email. BTW: the issue I was having with the porch light program was caused by a bad LED bulb, which I learned AFTER replacing the dimmer and encountering the same issue. ? The bulb worked intermittently and when it acted up it completely freaked out the dimmer and caused it to stop working. New bulb = problem fixed, AND I didn't toss the old dimmer so I'm not kicking myself.

The texts rolled in last night in a few batches even after the ISY was disconnected, which is pretty interesting. They would come in groups of three, same alert, time stamp was between 7 and 9am and never the same time on any alert. Truly bizarre behavior. Regarding @larryllix's comments on data congestion - we're fortunate to be relatively unaffected here in Washington State. I've been working from home the past two years now and monitor ISP and network health daily, so as far as our "stuff" goes everything is fine. Of course there's no telling how Verizon is doing, but I can tell you we haven't experienced any other delayed text messages, including ISY tests. The new power supply arrived and is installed, will monitor the aforementioned porch light program and see if it works. For now I am leaving all notification data (for sending text and emails) deleted to see what happens.

Update: The system has become self-aware and is attempting to assert its authority by barraging our cell phones with text messages from events logged 14 hours ago. 14 and counting from a single event. I disabled the program, but no luck. I have now deleted all notification settings (containing text and email addresses) in the hopes of making it stop. If that fails, I'll unplug the ISY and report back in the morning. If nothing else, I hope you guys are getting a chuckle out of my minor inconvenience. ?

Oh yeah, it's my first go-to when things are acting up. I don't think my ISY has an SD card, but will double check. Now that the porch light program ran and failed (light was not turned on) again, I noticed the program ran at 4:40pm yet the log shows the command was sent to the device at 4:58pm. I'm not sure of this is helpful information, but thought I'd pass it along just in case.

Yup, text and email notifications. Unsure how to do that, but I'll do a little research and see if I can add it. I looked at device activations related to the programs mentioned above and the logs show the command was sent at the requested time.

90 minutes past the program run time, still no text notification. The Last Run Time, however shows it ran at 9am, which would indicate I have problems with both signal and notifications which started at the same time. Tests using SP/carrier/SMTP server turn immediate responses as expected with no time delay. Signal tests where I control Insteon devices directly also perform perfectly with no delay. I'll follow @stillwater 's suggestion and order a power supply. If that doesn't work, I'm willing to replace the PLM and rebuild my notifications, but is there anything else I should test or examine before committing to that?

And while we wait, it's worth noting the "alarm" program I created (which sends notifications when motion is detected) is dutifully sending notifications via text despite the program being in "disarmed" state for the past 20 minutes.

Fantastic suggestions, thanks to you both. The good news is it's 8:22am here, so the first opportunity to diagnose is in 38 minutes. ?

I have a 994iPro running 5.3.0 that's been in service about 7 1/2 years, never had a problem with the ISY side of things. I've replaced a few PLMs, but otherwise it's proven extremely reliable. Recently, the system has been acting in what I can only describe as "inconsistent" then it comes to running programs. For example, I have a program that texts me 9am every weekday if I forgot to arm the alarm. Two weeks ago Tuesday it sent at 9:54am, then ran perfectly at 9am until the following Tuesday when it sent again at 9:54. Then back to the usual time until yesterday when it sent at 1:26pm and today at 4:12pm. Another example is a program I have to turn on the porch light 30 minutes before dusk....some days it runs and others it doesn't, and using the ISY to control the device directly works fine. If the problem were relates to controlling Instron devices I'd suspect the PLM had failed, but given the text message issues I'm suspecting it's related to running programs in the ISY. I checked the programs and nothing has changed in months - should I just replace the ISY or is there something I can do to troubleshoot?