Guy Lavoie

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

Ah UDI is now into gaming home automation controllers? Still needs the multicolored LEDs! Really though, avoiding to put it in a closed cabinet is probably the simplest and best thing you can do. The new R2 version has that going for it: lower power consumption.

Before the holiday period is over, make sure you enjoy the festivities by having your Polisy participate in the entertainment. For this, ssh into it, and first adjust the permissions on the speaker device: [admin@polisy ~]$ sudo chmod 622 /dev/speaker Then let 'er rip: (highlight the line below, starting with "echo", do ctrl-C to copy it, then go to your ssh window and do ctrl-V) [admin@polisy ~]$ echo "t165l8epepl4epl8epepl4epegcdl1e l4fffl8pfl4feepeddel2dg l8epepl4epl8epepl4epegcdl1e l4fffl8pfl4feeeggfdl2c." >/dev/speaker Of course, for the best sound, you need to be using Monster network cables! Sorry eisy owners, you're out of luck this time!

I also bought a Echo G4 for the same reason.

Bring up the device you want to map, tap on the three dots at the top right, and select "Configure Advanced Status Color, etc". You'll get the mapped values screen.

A question pops up in the back of my mind: is it even possible to program (link) a switch send an Off command to another switch when turning it On?

To rule out IoX (your controller), just unplug the PLM temporarily and redo your tests. If things stay the same, then it's not a program.

12 volts is 12 volts, nothing magical. I think the warning is because of the USB C connector used for the power connector. For the average tech stuff user, you would usually assume that any power supply with a USB C connector "should do", especially with some power supplies that sense and automatically adjust to the required voltage. It isn't the case with this PC. I'd almost be more vary about accidentally plugging the power supply into the actual USB C port on the eisy.

I've also noticed that, though I've only done it once or twice since that change

Yes, however there is now a several seconds long delay where the screen stays blank when you first fire up the app and when your device list appears, device statuses are already updated. Sounds like there is a silent sync of the displayed devices during that blank time. Not a bad idea really if that's the intent.

You won't be able to do that with a program node as a favorite. If you tap on Display Status, you'll see that the options only pertain to program related choices, like the last time it was run, things like that. To do what you want, you would be better off having your favorite change something like a variable, or a virtual switch type node. The display options then allow you to display the value or status of that node. You can also have it change the color of the icon based on value. The variable value or virtual switch status or control event could then be the trigger in a program (or programs) to launch a scene or whatever.