Phil G

Installed latest eisy-ui and PG3x. Reinstalled WeatherFlow. Still cannot migrate PG3 Legacy to eisy plugins.

My PG3 (Legacy) Dashboard randomly does this. Refresh doesn't fix it, but Logout and back in brings it back.

I did Upgrade Packages early this morning and then this trouble seemed to start. Not positive though because I only did the big upgrade to eisy-ui late yesterday and still not too familiar with it. You have to love how simple it is now to review package versions and perform upgrades. Boot Environment feature is pretty cool, too. Worth the pains to get to this point in my opinion. Well done, UDI.

@dbwarner5 , to be clear, you had to restore IoX from a backup? Did you do that in A/C or eisy-ui or does it even matter? Thanks for the tip.

I have tried unplugging / restart, and the Add All Nodes suggestion but still getting this error message. The eisy-ui PG3 (Legacy) page is populated with all Plugins connected. Migrate All results in them all coming over with the same error.

What's the eisy-ui version of right-clicking on Programs in the Admin Console to copy / paste programs into a text file?

I hear ya Now. I've been procrastinating for months but finally just did it. Backed up ZWave, then IoX, then hit the Upgrade Packages button. After about 35 minutes UDMobile told me I need to reboot, then about 15 minutes later got a notice on my phone that a Node Servers was starting up. Went to http://eisy.local/nodes in Chrome on my MacBook and watched nodes come back to life (status: Connected). So stinkin EISY (see what i did there), should have done it months ago.

I have some simple If-Then-Else programs that set a scene on or off, but Eisy-ui lists those scenes as 'undefined'. See below, In the Admin Console: NightLights - [ID 0003][Parent 005B][Run At Startup] If $s_Night_Time is 1 Then Set 'NightLights Scene' On Else Set 'NightLights Scene' Off Eisy-ui shows this: If$s_Night_Time is 1 ThenSet 'undefined' On ElseSet 'undefined' Off Doesn't seem to be causing any execution errors; that scene is being switched on/off properly.

Same here. Hue lights quit responding when I upgraded Eisy to 6.0.0. Noticed the duplicate nodes AFTER I upgraded the plugin to 1.6.3 but they were buried under the Hue bridge node (had to expand it to see them) and they may have been there from the Eisy upgrade.

I have no idea what you guys are talking about, but I thought it might be interesting to run this through Grok, so I queried someguy's original post. Here is the output: To have your IoX (Polisy) send a clickable link or button in a text message, you’ll need to integrate a few components: crafting the SMS with a clickable URL, sending it via IoX, and ensuring it works on the recipient’s device. The old REST system you mentioned could still be relevant, as IoX supports RESTful commands for automation, but let’s break this down step-by-step to ensure it’s practical and functional as of today, March 17, 2025. Step 1: Understand IoX Capabilities IoX (running on Polisy) is a powerful home automation platform from Universal Devices. It supports sending notifications, including SMS, through its Notification system, often via email-to-SMS gateways or third-party services like IFTTT, Pushover, or Twilio (if integrated). The key is to send a text message containing a clickable URL. IoX itself doesn’t natively render buttons in SMS, but you can include a URL that looks like a button or leads to a page with a button. Step 2: Craft the Clickable Link SMS messages can include URLs that most modern smartphones (iOS, Android) automatically turn into clickable links. For example: Plain URL: https://example.com/do-something Shortened URL (recommended for SMS brevity): Use a service like Bitly or TinyURL to shorten it, e.g., https://bit.ly/3xyz. To make it "button-like," you can’t embed actual HTML buttons in SMS (since SMS is plain text), but you can style the link text to suggest action, e.g., "Click Here: https://bit.ly/3xyz". Alternatively, the URL can point to a simple webpage with a button that triggers your desired action. Step 3: Define the Action Decide what "accomplish something" means. For example: Control a device: Use IoX’s REST API to toggle a light, lock a door, etc. Run a program: Trigger an IoX program via a REST command. External action: Link to a third-party service or webpage. If it’s an IoX action, you’ll use the REST API. The Polisy REST system is still functional as of 2025 (no official deprecation has been noted), allowing you to send commands like: http://<polisy-ip>/rest/nodes/<node-id>/cmd/DON (turns a device on). You’d embed such a URL in the SMS, and clicking it would execute the command (assuming proper authentication). Step 4: Send the SMS from IoX IoX doesn’t send SMS directly but can use email-to-SMS gateways or integrations. Here’s how: Option 1: Email-to-SMS Gateway Set up a notification in IoX Admin Console: Go to "Notifications" > "Add Notification". Recipient: Use your carrier’s email-to-SMS gateway (e.g., for Verizon: yournumber@vtext.com, for AT&T: yournumber@txt.att.net). Content: Include your URL, e.g., "Turn on lights: http://<polisy-ip>/rest/nodes/<node-id>/cmd/DON". Trigger it: Link the notification to a program or event (e.g., "If motion detected, send SMS"). Option 2: Third-Party Service (e.g., Twilio) Integrate Twilio with IoX: Use a Network Resource in IoX to call Twilio’s REST API. Example HTTP POST: POST https://api.twilio.com/2010-04-01/Accounts/<AccountSID>/Messages.json To=+1234567890&From=+0987654321&Body=Click to act: https://bit.ly/3xyz Authenticate with your Twilio SID and token. Trigger via Program: Create an IoX program to send this request when needed. Step 5: Secure the REST Link (Important!) If using IoX’s REST API in the SMS: Authentication: Polisy requires a username/password for REST calls. You can append them to the URL (e.g., http://admin:password@<polisy-ip>/rest/...), but this exposes credentials in plain text—not ideal for SMS. Workaround: Use a proxy service (e.g., a simple Node-RED instance or a custom script on a server) to hide credentials and shorten the URL. The SMS would then contain something like https://myproxy.com/light-on, which redirects to the authenticated REST call. Step 6: Test and Refine Send a test SMS with the URL. Ensure it’s clickable on your phone (most SMS apps auto-link http:// or https:// URLs). Verify the action works when clicked. If it’s a REST command, test it in a browser first. Example Program in IoX If Time is 7:00 PM Then Send Notification "Click to turn on lights: https://bit.ly/light-on" to "1234567890@vtext.com" Else - No Actions - Does REST Still Work? Yes, the IoX REST system remains a core feature for automation as of 2025. Universal Devices continues to support it for controlling nodes, running programs, and querying states. You can confirm this by testing a REST command (e.g., curl http://<polisy-ip>/rest/status with auth) from your network. Final Thoughts For a "slick button," the closest you’ll get in SMS is a short, descriptive URL (e.g., "Tap: https://bit.ly/do-it"). If you want a true button, host a tiny webpage with a button that triggers the REST call—then link to that page in the SMS. Either way, this setup leverages IoX’s existing tools effectively. Let me know if you need help with specifics like your Polisy IP or node IDs! DeepSearch Learn about Twilio integration Explore IFTTT for automation

I found a Leviton 2-wire dimmer that is controllable with HomeKit as well as their own app. I bought it hoping to pull that dimmer into Eisy after the big UDI update in January. It requires a Leviton WiFi bridge device which is the size of a small wall wart. The Leviton app and setup, and HomeKit integration, was very smooth.

Safari by default will automatically open "safe" files, so .zip files are unzipped. But, you can change that by going to Safari > Settings > General tab and deselecting that option:

I need to get a life. I read through this like it was a murder mystery. Saw the green 'Solution' box at the top so I knew the killer was going to be revealed by the end. I couldn't figure it out. Good eye, @Geddy.

Thanks @IndyMike for all the information. I'm holding out hope that Eisy will eventually work with some reliable presence sensors. I purchased an rPi kit from HA a few years ago back when Insteon was on the ropes but never took the plunge and set it up. Tried using Zwave switches with Polisy, but it was not a good experience and when Insteon came back online I stocked up on replacements and tossed the zwave stuff except for some sensors which work fine. Even though Eisy supports zigbee, it won't talk to this sensor?

@IndyMike, the Zigbee occupancy sensors sound interesting. Would you mind sharing what device(s) you are testing and how they are working out for you?