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.

Guy Lavoie

Members
  • Joined

  • Last visited

Everything posted by Guy Lavoie

  1. 5.8.4 is too old. Open a ticket for help on upgrading your eisy.
  2. Yup, I agree 100%. I expect a significant leap in the number of available plugins. My only concern, which I've brought up before, is that we'll end up with plugins whose code creators won't fully understand. That will make the "are you able and willing to support it?" question difficult. I include myself in that. I've been learning Python on and off, mostly by reverse engineering existing plugins. I did create a couple of simple plugins on my own. Now the irony is that we'll need to reverse engineer our own plugins. But back to how awesome this is: The plugin it created is well configured and "parameterized" (is that a word?). When I gave it the IP address and port needed to connect to my device, it automatically made that as a user configurable parameter. Just from the protocol document it dug up on it's own, it figured out that this was a main controller with expansion modules with module type numbers, and created "Discover" and "Rescan Modules" buttons. It figured out the binary protocol from a document that describes the commands like this: Get Unit Type ->Send 8 binary bytes: <42> <0> <0> <1> <176> <0> <148> <39> <-Receive 6 byte header: <n> <n> <n> <n> <n> <n> <-Receive 256 bytes data: <unit 1 Type> <unit 2 Type> <unit 3 Type> <unit 4 Type> etc… Note: only the first 128 bytes of data are valid <-Receive 2 byte CRC <n> <n> Data Explanation: SECU 16, Type = 11 SECU 16I, Type = 12 RLY08-XA, Type = 13 The above command is pretty well the only hint that there are various module types. It showed me the response it got and set up a sub node for each one. It implemented the commands matching each module type. It also told me about an unknown module type 6 that showed up in the list. I told it that type 6 is a SECU16IR (I literally typed that in) and it dug up the one entry in the document that refered to that module name, and added the commands for it. Powerful stuff!
  3. Guy Lavoie replied to ErikN's topic in eisy
    It would leave you at standard time. So time would stay constant, but sunrise and sunset times would be off by about an hour.
  4. For your first one, it sounds like AI is confusing "test" as both a command and part of a device name.
  5. But USB to serial is more constraining, with a cable directly between the two devices, not handy if they're far apart. Using IP allows you to use your network infrastructure. It's also somewhat easier to use IP when you need multiple access, such as with the Ocelot: it's admininstration program is called C-Max and accesses it with the same serial port. Using a virtual serial port on the PC, I can easily switch back and forth between that and the plugin. Same thing with administering a Elk M1 with ELKRP and using the Elk plugin. I actually have three of these IP to serial devices in service here: one for the Ocelot, another one for the Elk M1 (instead of a M1XEP) and another one for accessing a Somfy URTSII with the Somfy plugin. I use the Lantronix EPS1 print servers because I happen to have bought a bunch of them at $5 each many years ago. I have 15 of them! They're often available on ebay for prices as low as $20. In fact I should do a little writeup on configuring these, could be handy for other members. Speaking of USB and constraining... The advent of Z-Wave LR is making the placement of the antennas of dongles (ZMatter and otherwise) more important because you don't have a mesh network in LR, and being stuck with a USB cable between the eisy and the dongle is a limiting factor. If anyone is aware of some kind of USB extender (like a wireless link), it could be a nice solution.
  6. I just hope no last minute thing trips me up, like a hospital appointment. I'm looking forward to this!
  7. Today is day 1 of trying out plugin creation with eisy-ai. I just spent a few hours on it. In one word: Mindblowing! Well ok, that's actually two words... but I'm totally amazed! For over a year I've been thinking about creating a plugin for the Applied Digital Ocelot and it's expansion modules. This got it mostly done in one day. It went out on the web and found the CPUXA serial protocol document (that I already have) for talking to the Ocelot, and commands needed to do things like read and write inputs and outputs. It's an old document (March 2000), which didn't list the module type for the SECU16IR module, but it did have the commands for it. So I told eisy-ai that module type 6 was a SECU16IR, and it took my word for it and implemented the commands. Customization is at least as impressive as generating the original plugin. The Ocelot is a serial device so it's connected to a device server for IP access (actually, a Lantronix EPS1 print server). I just told it use the IP address and TCP port number, which it automatically implemented as a Configuration parameter. I then asked it to make that two independant parameters, and it made the change. No fuss. I'm still missing the read variables command, which I had reverse engineered years ago but have misplaced the sheet (dang, I'll have to drag out the ole breakout box again). This is a plugin that I'd like to make available to the community once it's cleaned up and a few more features added, such as supporting the bobcat modules and the Leopard too (basically an Ocelot with a touchscreen). The next challenge will be to make the expansion module list and adnet address configurable as parameters.
  8. The ability to use formatting strings (like printf) would be a nice plus.
  9. Handful? Like a scene maybe? Always the same ones?
  10. Yes, I just got this set up and working! I'm so used to running the staging versions on my test Polisys that I forget that my eisy was running from beta releases. All updated and eisy-ai installed correctly, and json file is now all set up. My first request was simply asking which lights were on, and bingo, it told me 🙂 I wanted it all set up and working before the webinar, to avoid wasting people's time in figuring this out. Now the real learning begins! I'm particuarly interested in plugin development with this. Thanks to UDI for letting me participate in this trial!
  11. Have you tried enabling LR in eisy-ui? On the Z-Wave screen, select the "US LR" Z-Wave region. It won't appear to be selected at first, but if you then turn Z-Wave Support off and back on, then you should see US LR appear in the region, then try adding a device with SmartStart Add. It should let you select LR or mesh.
  12. Did you then try the Zsniffer tool? That's what seems to be needed to make it add the license to your dongle firmware. Read my October 10th post in this trhead for the specific things to click on in the tool. it's not very intuitive.
  13. I'm finally getting around to trying this out, and I'm not getting very far: Is there any kind of "how to" anywhere for someone who hasn't ever used AI (other than one on a free web site)? I get a sense that everyone here is already familiar with some aspects and are just concerned with getting it to work on the eisy. Posts mention configuration files, etc but no specifics. The README file mentions a json file, with no clue where it is, etc.
  14. Aww, another Polisy not getting the love it needs! I'm running my own little Polisy no-kill shelter here...I have 3 of them! Even funnier is that I went straight from a ISY994i to a eisy, and got the Polisys after, they came up as opportunities (I wanted the ZMatter boards in them). I use them for testing new releases and testing devices. But I understand that some people are more interested in mainly using their controllers, and not necessarily as a hobby. @michaelrlawrence and @MClark01 you should offer them for sale here. Traditionally, people offer their devices in the Coffee Shop section of the forum. Indicate where you're located, how much you want for them, and if they have any extras, like wifi or a ZMatter board. You might make someone else happy.
  15. Guy Lavoie replied to Techman's topic in eisy-ui
    So you want a group ungroup!
  16. If you're more geeky, you could also keep that Polisy for testing. I've been doing that and it's been rewarding. Though you sound like you'd just rather have something that's less maintenance.
  17. Open a ticket, An alternative fix would be for UDI to allow you to download an installation image to your own stick and reflash the eisy that way,
  18. The ideal method is by integration (averaging over time). 4 or 5 samples spread out over several minutes, then take an average. Then discard oldest sample and take new one, keep averaging.
  19. You could use math to reverse the value: Light level = 400 - sensor value
  20. I'm starting to think it could be your PLM. Do you have a spare on hand?
  21. Yes, I also saw the "reboot needed" message after upgrading my test Polisy today. We're getting there!
  22. Yes, that's annoying.
  23. Welcome into the LR sect! Now that you know the secret handshake, let us know how your tests go.
  24. @Javi Another thing I noticed, which may or may not matter: When I upgraded the dongle firmware, I enabled both the "Long Range" and "Fast Communications (Fast UART)" features. @johnstonf didn't enable "Fast UART" (see his screenshot above). Do you think that this could be related to the timing issues that he experienced?
  25. If you haven't updated your dongle yet, then your existing devices will certainly be in mesh. Re-installing everything in LR when it's working fine in mesh might not be the best idea. If it ain't broke, don't fix it. I think this will be a dilemma for everyone with an existing Z-Wave setup that's only beginning to get LR devices. The beauty of Z-Wave is that your network can use both LR or mesh, so it might be an idea to try LR if you've been having signal reliability problems with particular devices. If you do reconfigure some devices to LR, let us know how it goes.

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.