Skip 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.

Xathros

Members
  • Joined

  • Last visited

Everything posted by Xathros

  1. I just set up on Win 10 VM with no problem. Just double clicked the driver and it installed. Plugged in the etcher and launched the software. I just completed a test burn with one of the provided images (The rose) for the girlfriend. -Xathros
  2. Excellent. I'll give it shot on Win 10 and post my results. Thanks. -Xathros
  3. What platform are you running this on? I haven't set mine up yet. I have VM's for XP, 7 and 10. Just wondering what would be the best choice. -Xathros
  4. My etcher, laser tape and color fill are all scheduled for delivery today but I probably won't have time to play with it until the weekend. -Xathros
  5. Xathros replied to ldrinc's topic in ISY994
    You CAN hide programs from the Mobilinc user! And devices and scenes as well! In the Mobilinc settings, there is a setting called"Hide Text" that defaults to {HIDE ME}. I have Edited mine to be {H}. Anything that I don't want to see in Mobilinc gets prefixed in the Admin Console with {H} which prevents it from being seen in Mobilinc. This works for Devices, Scenes and Programs. Take all of the programs that you don't want this user messing with and prefix them with your choice of Hide Text. The UDAjax page will hide items prefixed with a ~ so that might be a better choice rather than {H} or {HIDE ME} since it would also work on the web interface. Hope this helps. -Xathros
  6. The inexpensive Foscam or Smarthome (rebranded Foscam) meet these requirements. -Xathros
  7. Just ordered my engraver. Now I need to go order some blank buttons. Thanks to marcin and everyone else who has contributed to this thread! -Xathros
  8. Certificate management is done via the Dashboard rather than via the admin console. Link to the dashboard jnlp file will be in the announcement post for the firmware version your running. Start here for 5.x versions: http://forum.universal-devices.com/forum/108-50/ or Here for 4.x and below: http://forum.universal-devices.com/forum/15-current-release-betas-and-bug-reports/ Hope this helps. -Xathros
  9. Nice find. I'll have to see if I can translate that into a python script. If so, I could execute it from node link's relay server. Thanks! -Xathros
  10. Can you provide details as to how that was accomplished before it broke please? Thanks. -Xathros
  11. I agree that $30 seems a bit steep for what it is but I bet this guy is worried about recovering his tooling costs and the price will drop after that is taken care of. I have seen many things that were much farther from a realistic price than this. If I wanted to wall mount my Echo, I think I would order one of these even at this price point. Based on the recent flood of Echo accessories coming on the market, I suspect it won't be long before this has some competition to chase the price down. -Xathros
  12. USB will NOT work. Must be a 2413S Serial PLM. Or an older 2412S but unlikely you will find one of those anywhere. -Xathros
  13. You will need an Insteon 2413S PLM to interface the ISY to the powerline. This is not a Hub but rather just a serial powerline modem. Not sure if what you ordered includes this but most kits do. -Xathros
  14. Have you ordered a Dot? I wonder if the updated software is being pushed out to accounts that have ordered dots... -Xathros
  15. Both of mine are at 3202. The upgrade from 3077 happened sometime over the last 4 days. -Xathros
  16. Problem solved. Turns out that both of my ISYs were using a dispatcher URL from back in the alpha days. Michel had me set the default dispatcher URL and my ISY came right back online. Just in case you find yourself in this position, telnet into your ISY and issue DPU <enter> to set the default url then XS <enter> to exit the shell. Thanks all for chiming in! And thank you to Michel for the speedy resolution. -Xathros
  17. This evening neither of my ISYs are showing online in the portal. On the one ISY that I can reach from here, the portal tab shows Offline, Registered. I have rebooted the ISY with no change. The portal shows both ISY's offline, last seen at 175:51:59 EST. Is anybody else seeing the same? I have PM'd Michel and will update this thread as I learn anything. -Xathros This has to be because of my "Cloud" comment earlier today...
  18. The Ubiquity network stuff is good gear. I use them both at work and at home. I have installed them at numerous client locations as well. No issues on my Macs in terms of getting them running. They do use Java for their "Controller" but I have not had any trouble in that regard. The controller is not necessary beyond for configuration unless you want to monitor the network. Hope this helps. -Xathros PS: These are WAY better than any of the Airport gear in terms of signal propagation.
  19. And retriggers your program running false because the mode was changed to off.... -Xathros Sent from my iPhone using Tapatalk
  20. Hey Stu, Wouldn't both of those trigger upon opening or closing (Assuming he is sending Off commands from the sensor) the door making this designed to do exactly what he doesn't want? Maybe program #2 was supposed to be disabled? I'm still waiting for a reply from the OP re my questions. It may be an issue with how the TStat is handling the mode set command as well but need more info from the OP to make a good diagnosis. -Xathros
  21. Is the Open/Close sensor configured to only send 'On' commands? Can you watch the program summary when closing the door and see if the program turns false? Post your findings. -Xathros
  22. Xathros replied to ldrinc's topic in ISY994
    You don't run the program. Instead, you wait for it to run by being triggered via the sensor's heartbeat which should come sometime within the next 24 hr period. At that point, the program will attempt to write changes to the sensor while it is awake for the heartbeat transaction. -Xathros
  23. Here are the key parameters I'm using for my smart plug: Parameter Size Value Comments ========= ==== ===== ================================================ 1 1 0 MultiSensor reports Power 90 1 1 Enable Params 91 & 92 91 2 25 Minimum Watts change to report. 92 2 5 Minimum % change in Watts to report. 101 4 8 Report KWH in Grp 1 102 4 2 Report Multisensor in Grp 2 103 4 0 Grp 3 no report 111 4 600 Group 1 report every 600 Seconds (You will want 300 here) 112 4 600 Group 2 report every 600 secs (10 min) I think thats all I set on mine. -Xathros
  24. I have a few of those. I will check my settings when I get back to the office this afternoon. -Xathros Sent from my iPhone using Tapatalk
  25. No problem. Always happy to help. The parameters are different for each ZWave device type/manufacturer. These should be documented by the device manufacturer. If not, I have found many answers in this ZWave device library: http://www.pepper1.net/zwavedb/device?page=1 Click the device name on the left rather than the document icon on the right for a readable parameter listing. Once you know the parameter ID's, parameter size and values, you can edit them in the ISY Admin console by right clicking on the ZWave device in the tree and selecting "ZWave / Set Configuration Parameters" from the popup menu. Then enter the parameter ID, it's size and your desired value. If you try to query a device to retrieve an existing parameter value, you must properly set the parameter's size in the dialog before you query. Give the system a few (5 ish) seconds after hitting query for the ISY to chat with the device, receive and display the result. Hope this helps. -Xathros

Account

Navigation

Search

Search

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.