Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Guy Lavoie

Members
  • Joined

  • Last visited

Everything posted by Guy Lavoie

  1. One of my two Polisys did upgrade correctly, and I made an image of that one to reimage the other that didn't upgrade properly. The one that failed (the first one I tried) had one of those smaller filesystems, and it's one I had previously reimaged from a file provided by UDI. Hence the discussion about these incidents of smaller filesystems.
  2. So this small filesystem size thing is popping up again. That's three of us now.
  3. If you have multiple control systems, each with their own Alexa skill, then you'll need to be careful and avoid creating duplicates. They don't know about each other. Ideally it's better to have only one system actually talking with Alexa, and the other systems communicate locally with the one that does. Finding unique device names becomes a challenge as the number of them grows. It's best to avoid multiple word names where one word is used in several names (ie: bedside lamp, kitchen lamp, etc). I've kept everything to single word names, which is much more reliable.
  4. No, if Michel tells you it needs flashing, then that's your next step. That's a more extreme solution because you're not recovering anything, so if you have no backups, this really sets you back. About the portal subscription or not and my login screen comment above: I might have a bit of an exception here. I have two Polisy units, that I use for testing and learning. Polisy 1 has a few test nodes defined on it, and a lapsed portal subscription. Polisy 2 is one that I got recently, given to me for free by a generous forum member. He said it was messed up, it wouldn't even boot up. I ended up getting an image file from UDI and buying the needed USB adapter card to enable flashing the SSD using Rufus. That worked...I think. As I posted in another thread, it was seemingly working fine, and I picked that one to try the 6.0.0 upgrade. Well the upgrade failed (it stayed at 5.9.1) and when I started checking it out, I had the same issue as @apostolakisl: a 3 GB filesystem and the upgrade was failing due to disk being full. I haven't proven it but my thinking was that maybe I made a mistake when using Rufus to flash it's SSD. Well ok, so then I tried the upgrade on Polisy 1. That worked great. So I had an idea: make an image file of the SSD of Polisy 1 using Rufus, then I used that image file to reflash Polisy 2. So now I had a clone of Polisy 1 running fine on Polisy 2. Already upgraded to 6.0.0 too. Now back to the portal subscription thing: Polisy 2 was eligible for the free 1 year portal trial subscription (the previous owner had never subscribed), which I enabled. Works fine. Portal access is up and running on it. But, it was running an image of Polisy 1, which had a lapsed portal subscription. The 6.0.0 upgrade process was done on that unit, then the image copied over to Polisy 2. So the 6.0.0 upgrade process must check if you have an active portal subscription, and configure the Admin console login to use the usual IoX login and password if you have no portal subscription, or use your portal credentials if you do. Since the upgrade had been done on a no subscription unit and then copied over, Polisy 2 is having me log in using the IoX login and password, but still has a working portal subscription. I'm sure there must be a simple configuration file somewhere that tells the admin console login program which user name and password (IoX or portal) to use, and that could be easily changed to use one or the other.
  5. I notice that when you log into with the launcher, the login box actually tells you what login to use. On both of my test units (both Polisy) the box has the User ID and Password fields, and underneath it tells me "Use your IoX userid/password". I imagine that for those who now log in with their portal credentials, it must tell you to use those instead? Because not everyone has portal subscriptions.
  6. I'm confident that UDI will get you running again soon, since your Polisy is booting up and is getting a network address. Yes, do tell us what it ends up being. I have two Polisys here running 6.0.0 so it definately works.
  7. I also get the warnings about the polyglot owner not being right, the -H option, and a pkg names serial not found when doing a udx restart, but I can still log with with admin console.
  8. It would be helpful to see what those are. Ok, dusting off some old unix tricks here... redo the pkg install as follows: sudo pkg install -f isy >/tmp/log 2>&1 This redirects standard output and error output to a log file (/tmp/log). Because screen output is being redirected to a file, you won't see the prompt for the admin password, so just type it in blindly about 3 seconds after starting the command. You also won't see the "do you want to proceed" question, so after about a minute, just type "y" and enter. When the prompt comes back, you can view the output in the /tmp/log file, and post it here.
  9. So you tried the recovery in the announcement: sudo rm /var/udx/.udx_install_cleanup sudo rm /var/udx/.upgrade_status sudo pkg install -f isy sudo service udx restart The recovery instructions are written for a eisy, so it's normal that the interface re0 would not exist. For the polisy, that would be igb0 instead, so: sudo dhclient igb0 sudo service udx restart But first, what did you see when you did: sudo pkg install -f isy ?
  10. That looks good, so it's not a messed up filesystem. Normally when the upgrade finishes, it prompts you to reboot. See that at all?
  11. Log in with ssh and do the "df" command to show the disk apace, and post a picture of the screen.
  12. Thanks. I hadn't thought about the multiple pages, which can certainly make organizing things much more intuitive.
  13. Cool! Nice to have the tools to expand existing filesystems.
  14. Let me send you a message in a few minutes
  15. Guy Lavoie replied to Techman's topic in eisy-ui
    The easiest way is to copy and paste the link given in the release announcement. Otherwise you log in by ssh, go into the directory path shown in the link, and then use "vi" or "more" or view the sysconfig.txt file.
  16. In my case, he had sent me a link to download it from. It would be a rather large file to send as an email attachment. Could you post an image of your screen following a "df" comnand from the unix shell?
  17. Interesting. If you saw my first post about the two test Polisys that I attempted the upgrade on, the first one I did showed me a similar strange setup with only about 3 GB or so being used, and a filesystem using 512 byte blocks. I had recovered that particular Polisy using the disk image that UDI had me download, like you. I ended up recovering it another way (cloning the SSD of another Polisy) but what I *think* might have happened could be a mistake when I ran Rufus. When you select the image file to restore, you really need to choose the file correctly, as per UDI's instructions: From Boot selection, choose Disk or ISO image (Please select) and then click on the Select button which allows you to pick polisy.13.img that you downloaded previously The mistake I probably made was to pick the "polisy.13.image" directly in the Boot selection list (it does appear there), instead of selecting "Disk or ISO image (please select)", then select "all files" (by default the list shows iso files) and then pick the "polisy.13.image" file. I can't say for sure because I had restored that Polisy several months ago. But I can see how easy it would be to make that mistake. The funny thing is that the Polisy still worked, but with the much smaller disk size.
  18. That's the thing with disk image files. It simply takes an exact picture of what's on your disk, sector by sector. It doesn't know or care if it's unix, windows, etc. To have a bigger filesystem than the 32 GB that the UDI image was created with, you'd have to go through an actual installation of unix, setting up filesystems, etc. Because all Polisys are the same when shipped, it was much easier for UDI to make one detailed installation they way they wanted it, and then clone the disk image to make the product.
  19. Good. I thought so, that you would be doing something like that. Logical too, get the functionality first, and get the pretty stuff done later. As it is, it's darker than the inside of a cow! lol So the concept of tiles is to create a home screen with the nodes that you want to see right away when logging in, a sort of favorites? In my mind the term "tile" evokes more of a smaller icon, that you could then click on to see the details, a bit like the favorites screen in UD Mobile. I just want to make sure I get the idea.
  20. This is what I have: https://www.amazon.com/Adapter-ELUTENG-Converter-Portable-External/dp/B07VP2WH73?th=1
  21. You should get the USB adapter to allow you to restore the SSD from a file.
  22. I haven't opened up my eisy yet but from reading other information on the eisy, it doesn't have a removeable SSD. There is room for one, but UDI uses the one built in on the motherboard. It would certainly be nice to be able to make the same kind of image backup to a file. Maybe there's an alternate way to do that, or at least a full drive unix cpio backup to a file that can then be copied over the network.
  23. Just a note that I got this resolved. I took the SSD out of the properly working Polisy, made a disk image file with Rufus, and then wrote that image on the SSD of the Polisy with the weird filesystem sizes. Now I have a perfectly working clone, which is ok for test purposes. It's also a great way to make an ultimate backup, when you're about to make a big change like this kind of version upgrade.
  24. Logging in via ssh is the same as before: ssh admin@eisy.local In some cases you can/need to use the ip address instead, ex: ssh admin@192.168.0.199
  25. When I updated my Polisy, it did say that a reboot was now required, which I did from the Admin Console Configuration screen. I imagine that the eisy will be similar.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.