Guy Lavoie

Did you ever figure out how to get the temperature device to be recognized as such by Alexa? Just wondering. Thanks.

The same thing happened with one of my Polisys, updating from 6.0.0 to 6.0.4, upon a reboot (which came after powering it up after I flashed it's SSD with a 6.0.0 image I had made in September). Looks like they're taking a page from Microsoft's playbook, doing upgrades on the fly upon a reboot. I'm guessing that they figured 6.0.0 wasn't stable enough to leave as-is on a running system.

It could just be going bad, such as a bad capacitor.

Can you see your eisy among your router's device table?

The usual advice is to go into java and clear the cache (all 3 clear options). My personal approach is to click on "Add" in IoX finder and manually enter the url. For example if the IP address of your eisy is 192.168.0.123 then enter: https://192.168.0.123:8443/desc Then click on the new entry. If that works out, saving it to a file (click on "Save") is handy, so you can load it from a file the next time this happens.

I had a similar experience with one of my two Polisys. It took a long time to update, though I left for lunch while it was still going so I can't say how long it all took. I was monitoring the log file with a tail -f so I know it was busy doing it.

My understanding of the wall mounted panels on the old Chamberlain openers (which is what I have) is that they have only two wires but have three buttons: open/close, light, and lock. The open/close button shorts the two wires together, which what we do when we use a IO Linc to operate the door. The other two buttons would put capacitors across the wires, altering an oscillator circuit that the main controller board in the opener could distinguish to know which button was pressed. With the newer openers, the wall mounted panel only receives power, and the buttons make the panel transmit rf commands, just like a remote. This would mean that you need to open up the panel and wire the IO Linc across the contacts of the open/close button itself, instead of the external wires supplying power to the panel.

Can you ssh into it? If you're not in a position to wait for UDI support in 2 days, you can try this: ssh admin@eisy (or ssh admin@<ipaddress>) Then try: sudo pkg install -f isy sudo pkg install -f udx If it asks you to allow reinstalling packages, respond with yes. If it completes ok, then wait at least 10 minutes, and then reboot: sudo shutdown -r now See if that brings you back up.

Fresh batteries would be step#1

Motion sensors can certainly add to irregular triggering. Adding cats to the mix steps that up another few notches!

I've always saved the device list whenever the list changes, and I've never needed to do the clear java cache thing. It would be handy if we could add a link to eisy-ui among the entries. A one stop shop for whatever access method we want.

The nodes in folders I'm seeing aren't ones I created. In fact I've never tried that myself in admin console. The ones I see are those created by plugins, such as the Hue plugin.

This morning I can confirm that it's now working for me, which is the first time I'm trying this plugin.

If you look around in eisy-ui you'll see that existing folders are shown (although in always expanded mode, at least for now). This is true for device nodes and programs. The development path seems to be aimed at getting all the information showing up on screen first. There are no editing features yet, such as for programs. I gather that the ability to create new folders will get added along with program editing, etc.

Do you have a local nameserver, or a local hosts file on one of your computers?

What's odd is that their phone app kept working just fine, and I was even able to add a new plug. Like they didn't need this function themselves.

It's still in development so we'll see how it ends up looking once it gets closer to being finalized.

If you ever find out, you might win the Nobel Insteon prize!

If you have a spare switch of the same type, add it as a new switch with a temporary name. Then bring up one switch you want to rewrite to, right click and select "replace with" and assign it the spare switch. This will adjust your programs automatically. Similarly, add back the original switch as a spare, and "replace" the temporary switch back with the original one, again getting your programs automatically adjusted. But before all that, have you tried "restore device" on the switches?

Interesting. I'm away right now but I'll certainly try it this evening. Thanks for the heads up.

Well it didn't cause me any issues, being a test system. On my production eisy, I went straight from 5.9.1 to 6.0.3, then to 6.0.4. Another thing is that it did it as I was booting it up. A Polisy beeps when it starts up. This time it beeped again, a few minutes after the first time. I don't think they'd do updates on a running system. They probably evaluate the risks on a case by case basis. This was likely a minor bug fix. Maybe UDI could let the user decide, by adding a "Allow automatic updates" check box in the Configuration screen.

There has been a few mentions of people getting updates getting "automatically" installed. I had a hard time believing that, until yesterday when I seem to have been bestowed the privilege of experiencing one myself. As I've mention on these forums a few times, I have two Polisys that I use for testing. I had disconnected one for over a month for various reasons and when I plugged it back in a few days ago, it wouldn't boot up. Reflashing the SSD failed, Rufus couldn't write to the drive. Obtained a few spare SSDs and flashed one with a Polisy image file that I had created on Sept 29th, a file I named polisypro_600 because it was a 6.0.0 system. Put that in the Polisy and it booted back up just fine, and IoX finder showed it as...6.0.4! I sshed into it to view the sysconfig.txt file and yup, it has 6.0.4_1. Interesting.

Another thing I like to do is add the devices to my local hosts file in windows. This file is \windows\system32\drivers\etc\hosts. This way I can give them meaningful names, handy for things like ssh admin@<my_name> especially when you have one eisy and two Polisys sitting around.

I don't ever remember seeing a notification in admin console saying that an update was finished. What I do remember seeing is a notification that a reboot is needed, if the update involved updating the OS (FreeBSD version). Otherwise, it will usually just restart the udx and isy services.

Well that's it: you don't want to assume anything. In trying to do something like this, I'd actually skin the power cable to expose the wires and find out which wires carry the voltage, and the polarity. Then cut the cable and connect my own 12 volt supply to those wires. I'm guessing that only power is being carried (no data of any kind) and seeing only two conductors would confirm that. The actual controller hardware is a MELE mini pc. Amazon sells replacement power supplies for it. Read the warnings in the product description. It is meant only to be used with that type of mini pc https://www.amazon.com/Standard-Computer-Quieter2-Quieter2Q-Quieter2D/dp/B099RXXDYT/ref=sr_1_1?crid=MR3G3BKEVMXI&dib=eyJ2IjoiMSJ9.sf0GiA3PTCJLEmuSfrfWLijf41NLO_8ZXideBCz6g0Bgw9kXukFwtcKGsmB5HuumH5uNTyCm1Qi7cxjQoBq5JKwx4EpKPi5U8tRWO2cwE-ECfU-l3Lkz4Ou0rQQjUXRMgDBTdTfq1QD1UtLpnwqm2p_6e3-vLzuZ1AdH0dxJuisCin15etxo9-TX6KL4CktDzVcUw84RiDhXZQcykS8_SXXcDlT1tQK0TMtTq5FYBj4.WNmSzb-X67YTH0fkuXrY3PHd_y_a9r5jH29MvegbXWo&dib_tag=se&keywords=mele+mini+pc+power+supply&qid=1767110606&sprefix=mele+pc+power+supply%2Caps%2C140&sr=8-1