larryllix

The only thing I remember about those pieces of junk is the unit I received had the IR sender was wired in reverse polarity and I could never get it to work properly. I could not get passed the memorize the IR codes I tried to program it with, and then ISY would not recognize it properly. When I tried to send it back under Insteon's warranty, they replied, sure..not problem but the $50 CAD cost to return it for warranty services was almost the cost of a new unit. Poor warranty for a newly purchased device. Buh-bye old Insteon failure. (Glad to see new blood there) Garbage. As IR was dying very quickly I attempted to find other ways and other equipment that didn't use IR, or also supported WiFi control.

I have thought about the eISY many times but everytime I add up the aartech.ca price and include the matter dongle (still using my old PLM) and add taxes, and shipping, it gets to be $1000 and way too big of a jumps since my $99 ISY introduction.

I am not sure the ISY would handle a card larger than 16MB. It could only use a max 2MB of partition size as it used the old standards. Only format the SD card inside ISY to be sure. It should be automatic from there. IIRC it was FAT. Try a smaller SD card size if you have an older one laying around. ISY originally came with a 2BG SD card.

No. eisy.local results in a Not Found error in the browser. My bookmark https://my.isy.io/index.htm works fine for ISY Portal though. That would be an assumed port 443 then. My bookmark http://192.168.0.165:3000/dashboard works OK for PG3x also.

The Ping plug-in mentioned sounds like a great idea but in the old(er) days I set up a state variable and made ISY Portal aware of it, presenting it to the Alexa cloud app. In the Alexa cloud app, I created a routine, triggered by the pseudo MS from ISY Portal and that triggered a turn on of another variable that ISY watched for response. I am not sure who cleared it now. On a cyclic timer ISY then sent that semaphore by toggling the variable to True and then False (1/0) and then the program allowed half a minute to see or not see the response. If no response was found then a series of repeated attempts to power cycle the router was done with that program watching for a successful retest each time. IN the end IIRC I increased the time delay to about once per hour to retest. It may be a possible Internet failure. We've had a few in the Eastern Seaboard (NY, Ontario, Ohio, Michigan, Manitoba) so far.

It really ticks me off when I have to jerk my devices to get them reconnected each time the router decides to hiccough. Power cycling the router leaves a few devices hanging and need to have various degrees of power cycling, rebooting, and complete reset of the security details. My VR headset complains but then reconnects automatically.

ISY and an Insteon OnOff module is cheaper and you can control the logic to do it automatically. However, complete manual control has a lot to be said also.

Thanks for that info. I guess I have never had one. On that same note: I had to upgrade my java again and now have no IoX finder again. None of my links work anymore as they appear to have all changed again.. I can only download the start.jnlp app now. However java apps cannot be installed on the Windows Taskbar. ☹️ Here we go again.

Oh so you have a backup Internet access system, using a mobile cell signal device. That works. Costly for most of us though.

Network devices do not communicate by URL names. A DNS server has to be contacted first, which then supplies an IP address for same, or passes the request up to the next DNS server, usually google or similar, to be used by network devices. Then network and Internet devices use IP addresses for communications. LAN devices do shout out keepalive signals occasionally, to keep the router aware they are there but no URL names are used. Only IP addresses are used at this point in connection time. LAN devices contact a DHCP server with their MAC address of the hardware and receive an IP address from it, so they can be contacted by their assigned IP address.

Is this the Hot-spot from your mobile device? Can this work from 3000 miles away when your router crashes or locks up?

Thanks Of the 7 routers I have owned, they have only ever supplied the IP address of external DNS servers. There was no local DNS server or file containing local name conversions. Routers always contain a NAT translation table for the DHCP server. This has always been a problem because the ISY URL, always given out here, has never worked on any system I have owned. The IoX locator always disappears sooner or later, and then the links to reload it, never work, making it a real struggle to recover and access my polisys or ISYs.

Unless this devices has an automatic "return to on" routine, once turned off you will be locked out of any further WiFi actions once your power is off, and not be able to turn your router back on from anywhere.

How would my router know where eISY.local is? These names have never worked in any LAN/Router system I ever had. I have no local DNS server.

Did you know there are Govee 1 and Govee 2 revisions? I am not sure what the difference is but I know some software doesn't work with both version. There was a major change in the protocol. The PG3x plug-in only supports one of the protocols and it isn't matter, only the plain WiFi protocol.