Guy Lavoie

If you can't ping your eisy (and your router doesn't show it either in it's connected devices table) then you have an issue that's more primary than java versions or configuration. You'll need to open a ticket with UDI. Be prepared to connect a keyboard and monitor to it if asked.

First thing to try: are you able to ping your controller from a command prompt? If you can, then try manually adding the controller to the IoX launcher: click on "Add", and type in the URL. For example, if your controller's IP address is 192.168.0.123 https://192.168.0.123:8443/desc Then try using the added line to connect to it. If you can't ping your controller, you'll likely have to open a ticket.

If they were working fine and you confirm that you didn't change anything, I would start by doing a factory reset on them, then a device restore from IoX. I would start with the South Lights one if that's the one that seems to trigger the odd behavior. Test that, and then do the other one if problems persist.

Matter support appears to be quite the challenge to implement, but it's the next, necessary move if home automation is to become more mainstream than it is now. Look at other electronic products: all TVs now support hdmi, all computers (both Windows and Mac) do 95% of what people expect of them. All phones (Android and IoS) have equivalent apps for almost everything. Time for home automation to eliminate the "is it compatible?" guesswork.

I just listened to that. Nothing really new for us. Much of it is about their upcoming Hub 3. It's currently in beta testing. They're still calling it a hub and not a controller, though it is intended to allow some form of if/then/else programming. They also plan on supporting Matter, though not initially. No announcement of any other new modules or devices. The ever changing tariffs situation appears to have been a significant part of their supply issues. I smiled when one of the questions was about whether their new hub would support migration from a ISY994. The answer was basically no, you would need to factory reset everything. The bigger question is: who would want to do that when you have the eisy? Another question about access to an API got a rather evasive answer. I'm not sure whether that was about local control or just an open API for 3rd party access. They do mention the eisy (the ee-eye-ess-why lol) and consider UDI as partners, so that's always good to hear.

Just wondering if you made anything of the logs I sent you.

I don't have a Elk M1 but here is a general suggestion: program (in IoX) a variable as a flag that gets set upon startup, and create a program that looks for the flag set to that value, then have the program reset the flag, set your alarm status to a temporary value (armed might be the best one) and then query the M1 for it's status to update the eisy.

Well it might be more a function of the hardware platform or FreeBSD, depending on how far it gets or where it stalls in the reboot after a power glitch. It would be interesting to have a screen and keyboard attached to the controller (though that's not possible with a Polisy, only a eisy) to see what exactly happens. But an external delayed power on would probably be the best workaround.

Sounds like you could use a power on delay circuit module, to delay the startup of your controllers for several seconds. Most of these are sold as low voltage devices with relays, but you could install it inline with the low voltage power going into the controller.

But did you try rebooting the eisy after adding it back? That appears to be the workaround suggested.

Have you tried doing a factory reset on the switch first?

It could be a failing PLM. If you have a spare Insteon module laying around, try linking it. Or factory reset a seldom used module and try a device restore. How old is your PLM?

Nice. Take the time to read it's detailed documentation. You can configure when each stage kicks in based on time the previous stage has been running, or on temperature differential from setpoint. You can choose to keep the additional stages going until the setpoint is reached, etc. It's very configurable.

Does the login box say "use your IoX login name and password". If not, does it ask for your portal login (email) and password ? Just make sure you're using the right ones

Have you tried doing a factory reset and then a device restore in IoX?

You would need to create a program to detect the status change of the two switches, and turn on the light. Something like this: If icon status is On Or keypad button status is On Then Turn on switchlinc Operating the secondary switches manually has them send out the comnands due to links, but status changes caused by external commands (between the controller and secondary switches) only update them, not having them send out commands.

Let us know how it goes.

Well, it couldn't stop the isy service because it wasn't running...which corresponds to your problem. Otherwise it says it's restarting it. So try connecting again to the admin console. It it still doesn't work, you'll probably need help from UDI.

So the eisy is there. Harmless thing you can try: redo the ssh command and enter "admin" as the password. If that doesn't work, try your IoX admin password. When you get to the $ prompt, try restarting the isy service: $ sudo service isy restart You should see messages like shown below, if it restarts ok. Any error messages might give you a hint as to what might be wrong.

Ok, have you tried a connection to it with ssh? From a windows command prompt, enter: C:\ ssh admin@eisy.local Does it connect and ask you for a password?

Yes, that's how I typically capture a value from a sensor into a variable, by running a test that's always true. I'm not planning on using the high/low limit values or event triggers from the temperature sensor. That s_yolink_high_temp variable was just for testing purposes, to increment that variable by 1 every time the sensor temperature went over 26 C (I'd trigger it by holding the probe in my hand). The second way that would work here is by capturing the value in a variable and then testing against that, as I indicated in my later post. My intended use is for two things: First is to be able to ask Alexa what the pool water temperature is. This works, directly with the yolink's Alex skill (the connection to eisy isn't even needed). The second use will be to update my solar pool heating setup by capturing the water temperature to a variable, and also the temperature in the enclosure where my solar heating coils are on the roof with a second temperature sensor (I have 1200' of hose, in glass covered enclosures). Currently what I have up there is just a mechanical on/off thermostat, giving me a contact closure when it's above 80 F. In my updated version, I want to compare the water temperature against the enclosure temperature, ideally the water temperature where it exits the enclosure, and turn the valve to activate the solar heat when the water up in the enclosure exceeds the pool temperature by a certain margin.

Are you sure that the IP address you're pinging is the eisy? Do you have the IP address reserved for it in your router? If you didn't, something else might have taken the address. Check the MAC address.

This is the one you need: https://www.amazon.com/Adapter-Standard-Computer-Overclock-Quieter/dp/B0CFH98CTT/ref=sr_1_4?crid=GDYBNQPDUP61&dib=eyJ2IjoiMSJ9.sf0GiA3PTCJLEmuSfrfWLijf41NLO_8ZXideBCz6g0A0yMpO88mR1YkdoisM8Ks8J9Sezzi9lS3nGmEueOvlf8kDm27aYcMkNR_NEU1ugjT7h-Z_Xqj6TKbBI_y0vw1IDpMaRda1ZCs9N1crLIG9pr323yNfTmiDgLFSDA0mqj7qNruNr5YJBUdLsZVznsG4mii6o0LZ7jHY42eROUHMEDcrp7owd5c49pbKUy60hp8.68MO_g1RTmKvPjNM5xid_JEUoHJO4pEA9PZCFCgOzcU&dib_tag=se&keywords=mele+mini+pc+power+supply&qid=1763137625&sprefix=mele+pc+power%2Caps%2C105&sr=8-4

That must be geek mode!

I created another test today: copying the temperature (of the temperature sensor) to a variable. I triggered it with the s_yolink_trigger variable as shown in my programs above. The value was correctly copied into the variable.