Phil G

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?

These look great, but they're sold out. I'd buy a handful if they're not too painful to add in and manage. My experience with zwave and anything non-insteon, so far, is not encouraging.

Thank you Techman. I resolved this problem by disconnecting the lock from the Ultraloq wifi bridge and then including it again even though the IoX node was still listed. I included as a new node and I was then able to 'Remove Fail Node' on the old node. I think that using the Ultraloq wifi bridge as well as Zwave was creating problems. Not too many posts on this forum regarding Ultraloq U-bolt locks, so I'll add some info here in case someone else comes up with issues. I like these locks quite a bit although I don't have anything to compare them with. They seem to be solidly built. I wouldn't spend money on the fingerprint feature because it just doesn't work reliably. I was having some quirky behaviors with my 2 locks, so I disconnected both of them from their wifi bridge (each bridge only accommodates a single lock) and only use the UD Mobile app for remote status and activation and zwave inclusion/exclusion. I still can get full lock status with the Ultraloq app using bluetooth; gives me all the other features like access logs, firmware version, etc. Battery life may be an issue; some users report only 4-8 weeks of life using rechargeable NiMH.

I'm having trouble getting a reliable zwave connection to an Ultraloq U-Bolt Wave lock. It was included on the zwave network and then quit responding the next day. I'm now trying to exclude it but it is returning a communication error in the Ultraloq app. In IoX, the lock node is not responding at all, but I use "ZWave > Remove Failed Node" , I get this error: Any thoughts on how to deal with this?

Thank you for the explanation. I didn’t understand this aspect of using scenes vs program statements to control devices. This may explain my occasional device communication problems where I’m switching 5-10 lights with program statements and one of them doesn’t respond.

@paulbates, could you expound on this comment please? Are you suggesting to create another scene with all of the devices added, or something more elegant? Why would a program not be needed to set the devices to 'off'? Thanks in advance.

So you saw the message “start.jnlp was blocked” and clicked on the Run Anyway button?

I didn't explicitly import the certificate, so I think it happens when you first run the start.jnlp and get a Mac OS warning that the app developer is unknown. Here is how to override the warning and complete the install: I'm on Mac OS Sonoma 14.5. The 'Privacy & Security' setting to allow identified developers looks like this (it may look a little different if you're on a different OS version, but the selection is in there somewhere). Since UDI is not identified, maybe this doesn't matter so much, but I select it anyway: Now, when you double-click the start.jnlp file, you should get this popup: Select OK, then open Privacy & Security settings again and notice that "start.jnlp" was blocked. Select 'Open Anyway' to install Launcher: I think this process installs their app signing certificate. Since you said earlier that you don't see this certificate as being installed, then I'm assuming that you've never successfully installed that Launcher.

Do you see the Universal Devices trusted certificate? (click on Manage Certificates...)

I'd bet you're going to like the Ecobees. The only active control I do with IoX is adjusting the humidity set point for my upstairs Ecobee when the dehumidifier kicks on. I want it to run for at least 30 minutes. Otherwise, I can only say that I'm very impressed with their cloud service reliability as well as the hardware. I added 3 new thermostats recently to 3 remote shops that I monitor around town and they all showed up on my Admin Console w/o any action on my part. Kudos to the node server developer, @Jimbo.Automates, too! Well worth the cost. My only worry is that the Ecobee server might go away some day.