MarkJames

Thanks - I've been an ISY user for some 20 years or so and have never bothered with the internet access/certificate part of it. I've always used a port forward and secure password. Accessing it from the portal 'looks' the same but apparently uses the portal credentials instead - which I found a bit confusing. Now I get it. mark

So it's embarrassing to admit this but it was my own fault. I was changing some entries on the configuration page the other day and I must have accidentally unclicked 'enable insteon support'. Re-enabled and now working. I must have touched my touchscreen or something sigh. Thanks for the help, though.

Thanks, I'll try and post back either way

Thanks for the quick reply Green LED is on. The reset procedure went as expected Revision 2.6 1223 I don't have another cable like that to try so no - I'm stuck in that regard

I bought my eISY last year to upgrade my 994. I replaced my 2413s with a 2413u, ported everything over and for the last few months all has been well. Recently my eISY has lost connection to the 2413u. In diagnostics it says 'not connected' I did a hard reset on the PLM, power cycled the eISY and made sure the cable was plugged in properly but no luck. This sounds like a PLM failure, right? Or is there something else for me to try?

Never mind - the password got defaulted for some reason. My programs are now there after the reboot. Firmware and UI are at 5.7.1 Thanks. Any idea why the password I use if I launch using the my.isy.io/isy/xxxx link in IoX finder is not the same as the one I use if I launch using my direct IP?

Hmm... I'm away from home so I rebooted from remote. Now I can't log in. My password is rejected from IoX launcher. I can still use it from the portal, though.

I just checked and they match Firmware IoX v.5.6.4 (2023-08-11-12:24:06) UI IoX v.5.6.4 (2023-08-11-12:24:06) Product eisy(5226) I cleared my cache and deleted all applets. Ran it again but still no programs On another note is my password via the portal URL not the same as my password via a port forward?

Well this is weird. I just logged in to my eISY across the web directly to my home via a port forward. My devices are all there but there are no programs in the programs folder. I have a couple of hundred programs. So I logged in via the portal and lo and behold all my programs are there in the web version. I figured this may be some sort of credentials issue so I went back to my port forwarded login and went to set the admin user and password but it failed out trying to write. What am I doing wrong?

Thanks. Sorry for the long lag - I had been on an extended road trip and wasn't checking the UDI forum.

I see in the repository that speak with the canned phrases is marked as working.... can you point me to how to use the speak command within the admin console? I haven't been able to find a way.

Sorry - I left on vacation a day after posting this and had no internet. I managed to get it working. Thanks.

I'd seen that post and tried it but the info that comes up in my portal looks like this ::ffff:myip the myip portion is, of course, my ip, but the ::ffff: is part of what shows in the info window. Cutting and pasting that into the iox launcher just gives me 'bad url'. [edit] oops - just noticed the full url there that does, indeed, work in the iox launcher. Thanks - that will save me time in the future and also a port forward

I've had a portal subscription since inception and use it regularly but I've not seen a way to access admin console through it. I can access all my programs and devices but I can't write or edit without admin console.

I just finished migrating and have not tried to access the eISY from outside my home. Today I've been trying but have been unsuccessful. Hopefully it's a pebkac and someone can point out where I'm going wrong. I've been doing this for years with my ISY994 but for some reason this one has me stuck My router is at, say, 192.168.0.101. I've forwarded incoming tcp/udp 9000 to 192.168.0.101 port 443. If I try to add https://myip:9000 I get 'not found'. Any thoughts? Or even better - is there a way to launch the admin console via the portal? TIA [edit] figured it out - should have forwarded to port 8080. I can't seem to delete my post, though.

I purchased and installed the nodeserver, added my nuheat ID (which is my email address) and password (which I verified to be correct) but the NS isn't finding either of my thermostats. Any thoughts on what I might be doing wrong?

So is the control 'switched on' the equivalent of it going to 'violated'?

Thanks for the quick response. I have all my Elk violations in a folder for easy tracking. When, say, a PIR in a hall gets tripped it looks like this In this case it always turns them on - with some other doors/PIRs it checks first against time of day etc to see if they're needed. PIRs, can be funny things so I've been careful to make sure that the PIR actually does trip - I can see the light flick on it so I know it's sensed the motion. In general, you're right - it does happen fairly quickly. Fairly often, though, the lag is such that I stand there in the dark waiting for it to happen. I wasn't sure if the long and short poll numbers would be useful here as I'm new to PG and don't understand the finer details yet. On another note should I be checking for zone status for this sort of thing or should I be looking for a control ON message instead? Oh - lastly - any chance of being able to grab the lines of the Elk log as a substitution variable to be able to send via an email notification? You've made the Elk integration far more robust than the native version. I integrated all the same functionality that you did but I did it through the rest interface and acted on it through Tasker via autoremote on my phone. Yours makes it much easier Thanks!

I just migrated to eisy from my isy and purchased the Elk nodeserver. I use motion sensors connected to my Elk to turn on lights. This was fairly immediate with the ISY but with the eisy and the nodeserver I have a lag. Sometimes it's very minimal but other times it can be long enough to make it useless for turning on lights to navigate at night. Is there something I can tweak to fix this?

Interesting that you don't experience the lag as I do. It may be that my system is seeing a lot of collisions and failed communications at the moment as I complete my migration. Many devices didn't come across properly and so I've had to restore them one by one. Once all the links and relationships are restored properly perhaps it will get more zippy. The Elk is what it is. The native option is sadly gone - I would have preferred that it remain and the Elk poly was a choice I could make rather than having it forced upon me. The native support did everything I need other than access to the log which I wrote support for myself. I launch a lot of programs based on doors/windows opening and closing, motion detected, and I arm/disarm my system from within the ISY. I've been with ISY since the 99ir - easily 20 years or more - so much of my programming revolves around occupancy and motion within the home. Time will tell if it's as stable

So I got my eISY and am migrating from my ISY994. It's been a little tricky - partly because of the DHCP requirement of the ISY, partly because I had to change my PLM and I have some 109 Insteon devices to update. Admin console seems to load faster so that's nice. I'm a bit disappointed about the lack of native support for Elk. The plugin that replaces it is more robust - I'm not sure if it will be more stable - and frankly I think that the plugin should have been included for legacy users who were already extensively making use of Elk support. With the loss of native Elk I now have to rewrite dozens of programs to use the plugin. Anyways, be that as it may I'm a bit confused by what seems to be a bit of a lag between writing programs to the eISY and having them 'go online'. The ISY994 would accept 'save changes' to programs and within moments they were functional. With the eISY I find that I write changes and they don't go into effect for a 'while' (vague term, I know). It caught me the first few times because I thought the programs just weren't working but it turns out they worked - just 'not yet'. Is this a thing? Is there a delay that I should be expecting going forward? Thanks

You both got it. The problem was in the 'from' field of the customized email. Thank you both. mark

I have a routine that emails me if my sprinkler is shut down during the spring/summer. The email had a typo in it which I corrected. But the routine that sends the email still sends the typo. I'm not sure if this is just a buffer that needs to be refreshed or if the actual old content of the email is part of the program. Here is the code This is the content of the email as of now. It's been this way for a couple of weeks But this is the email that I get The typo was in the customized email when I wrote it and when I added it to the program but it was corrected a few weeks ago. Version info is

Same... I guess I'll burgle a KPL from somewhere that's not used too often to replace the one that does my kitchen. Sigh. Gonna have to decide on a new technology for any future repair/replacement.

Well that's not the best news ever. Thanks, I guess. Do you know if there are any services out there repairing Insteon devices for people with existing installations?