Everything posted by Guy Lavoie
-
Introducing eisy-ai !!!
Putting a bit more time on this today, Ocelot plugin almost done. Notes and observations: The sense of context is very good. I keep getting afraid that at some point I'll hit a wall and it won't have any sense of what I'm asking it to do. But no, it really seems to understand and have a feel for my intention, For example when I configured the I/O modules, it knew to poll the inputs constantly and automatically set them up to read them at every short poll, at 5 seconds. The same poll reads the inputs and also the output relay's status, which is good because a C-Max program in the Ocelot could also change an output, so it can't assume it's the only one changing outputs. In testing it, I noticed that if I had the plugin change an output, the status stayed unchanged until the next poll updated it. So I asked it to also immediately read in status whenever it changes an output. It understood the notion of doing that as well as the timed polls. No fuss. Similarly, since I want to use the Ocelot variables as triggers (ie: like status variables) I asked it to add a variable read to the short poll routine, as well as after any variable write. Again, no fuss. It seems to be aware of cpu and bandwidth usage too. It told me that it would be sending three 256 byte serial polls at every short poll interval, advising me that lengthening the poll interval could be done if that's too much. Here is another interesting thing it understood on first try: I typed: when you do a Get Unit Type command on startup or rediscover, if module types other than 11, 12,13 or 6 are discovered, create dummy nodes for them. List them as "Mod " with the module address followed by "Type " and the module type number discovered. These will act as placeholders. There will be no commands associated with them. response: Understood. Unsupported types will get inert placeholder nodes named like "Mod 5 Type 20", with no commands. The empty-slot marker 254 stays ignored, as it is now. Before designing it I'm checking the UOM table for the type-number property and how the real Node.setDriver behaves, so I can test discovery properly. That's impressive. When it makes updates to the plugin, it generates version numbers. Does this imply that changes that I'd want to undo can be rolled back to a previous version, like a source code control system?
-
500 error on backup attempt
I noticed this error 500 a couple of days ago, with eisy=ui 1.4.8. I just upgraded to 1.4.9 this morning and it's still happening.
-
Any interest for a Adicon Ocelot plugin?
Anyone who knows my former life will remember my involvment with Applied Digital and the Ocelot/Leopard controllers. The controller is outdated, but the expansion modules and IR capabilities are still useful, and my Ocelot hasn't missed a beat in the 26 years I've had it. If you're still using it, chances are you're triggering routines with slow and unreliable X10 commands from your eisy. Well I've been working on a plugin for it, using eisy-ai and it's almost fully functional. If there is community interest in it, I'd polish it up and make it available as a plugin. It would be free. I also need to make sure I understand the code well enough to properly support it. So let me know!
-
Plug in Dimmer Options?
I guess I've never noticed (or used) these options. I have 5 lamplincs and I'm seeing the same thing you are, with no Options button.
-
Plug in Dimmer Options?
-
Introducing eisy-ai !!!
Hah, similar experience here today, on day 2 of creating a plugin. It's great at creating code, but doesn't share our human intuition when it comes to naming stuff! I'm creating a plugin with a controller, add-on modules, and i/o ports on modules. I want the name to be hierarchal: add on module address, module type, and i/o port. Took a fair bit of time to get it to understand that.
-
Old dumb user here, upgrade where? How?
5.8.4 is too old. Open a ticket for help on upgrading your eisy.
-
Introducing eisy-ai !!!
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!
-
Daylight Savings Time
It would leave you at standard time. So time would stay constant, but sunrise and sunset times would be off by about an hour.
-
Introducing eisy-ai !!!
For your first one, it sounds like AI is confusing "test" as both a command and part of a device name.
-
Introducing eisy-ai !!!
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.
-
Webinar Time Poll
I just hope no last minute thing trips me up, like a hospital appointment. I'm looking forward to this!
-
Introducing eisy-ai !!!
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.
-
Variables displayed
The ability to use formatting strings (like printf) would be a nice plus.
-
Some insteon lights switch off spontaneouly
Handful? Like a scene maybe? Always the same ones?
-
Introducing eisy-ai !!!
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!
-
ZMatter USB Firmware Update 7.32 to 7.46
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.
-
ZMatter USB Firmware Update 7.32 to 7.46
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.
-
Introducing eisy-ai !!!
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.
-
Help me figure out what eisy to replace Polisy
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.
-
Group Nodes
So you want a group ungroup!
-
Help me figure out what eisy to replace Polisy
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.
-
Update packages for eisy-ui use
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,
-
Light sensor inverted voltage.
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.
-
Light sensor inverted voltage.
You could use math to reverse the value: Light level = 400 - sensor value