Everything posted by Guy Lavoie
-
Introducing eisy-ai !!!
Yes, I've just done that. Thanks. They are now submitted. I was able to install them in new slots from the "My Published Plugins" list, so I guess I have the file names and paths correctly set up. I imagine that they now just need approval to appear in the plugins store.
-
Introducing eisy-ai !!!
Well these are under the new integrated plugin platform (not PG3x), and I have never submitted anything for plugins yet, so there is an approval process. And these will be free.
-
Introducing eisy-ai !!!
Made another personal advancement today: setting up github and pushed my three plugins. Thanks in large part to @apostolakisl and his excellent writeup on setting up github (see page 6 of this thread). His instructions from step 3 onwards have now mostly been replaced with a streamlined process that was added to eisy-ai. Just give it the url and deploy key when asked and it gets done. 🙂 The next step is to make these plugins available to community, Not sure how we proceed to submitting that and getting vetted, but I'm guessing it's by opening a ticket, so I'll go do that now. Thanks for the help in getting me there!
-
Introducing eisy-ai !!!
Do you enter moves with a keypadlinc? Lol
-
Introducing eisy-ai !!!
Revenge of the Machines!
-
Introducing eisy-ai !!!
Yesterday I tried yet a different approach to creating a plugin, a bolder one. I spelled out everything I wanted in a single long request. It was about 7 lines long in the chat window. I told it the name I wanted, how many nodes to create, characteristics (raw number, increment once per second if non-zero), control buttons (stop, pause, etc) and pressed enter. It worked from the first try. So don't be afraid to be fussy and detailed!
-
Issue with upgrade to Eisy-ui 1.4.12
If you go into Protocols -> Z-Wave, do you see "Z-Wave Radio Connected" at the top right? Do you see "Z-Wave Support" set to On?
-
Introducing eisy-ai !!!
Done.
-
Introducing eisy-ai !!!
Ok I finally got around to doing this today. I have to say, for such a major update, it went really well! As expected, I had to wait a bit more while it reinstalled plugins, and needed to restart some, but in the end, everything was working. I then proceeded to migrate the plugins away from PG3x, one by one. Again, smooth sailing. There is only one minor issue remaining: It won't migrate the Virtual plugin because it wasn't installed from the production store. Indeed it was installed from the beta store. Thing is, the beta version is 3.2.3 and production store version is 3.2.2, so even though I go to the production store and click on "update" in the plugin's configuration screen (and it appears to be udating), the version remains the same, probably because it sees that the production version number is lower. How do I get around that?
-
Introducing eisy-ai !!!
Done. Took about 10 seconds.
-
Variable data editing in eisy-ui node screens
We're all used to how node controls are laid out in Admin Console: status information at the top, editable values in the middle, and action-only buttons at the bottom. The editable values area was particularly handy, because you could see the current value of that setting in the edit box,. You could edit it, and then click on the button/label next to it to make an immediate change to that value. That capability appears to have been lost in eisy-ui. Now you can only view the current value at the top (like a status), and then need to locate a separate list box to change that value (where you can't see the current value). When the list is long, you have to scroll back and forth to make and then see the change. Not great. Even Claude (in eisy-ai) says it like this: "In eisyUI the property tiles at the top are read-only displays. The editing happens through each variable's command input, in the list at the bottom." I'm working on a plugin in eisy-ai that allows editing 128 variables in a connected controller, so that's a long list. Initially I had it set up with a list box to "set" the variable I wanted to change, and then a second box to choose the value to set it to. It worked, but changing a value in a program required two separate program lines, not good. Seems we've lost something that was clean here.
-
Scenes losing Hue bulbs
Are you saying that they disappear from scenes, but their nodes still exist in your Hue device list?
-
Upgrading ISY/Polisy to Eisy
...or if you have a "main" location with several, smaller remote buildings, you could use IP based devices for those remote sites, if you have an ethernet network that covers the whole camp. Matter uses IPv6, though you would need to upgrade your Polisy to a eisy to use Matter.
-
Looking to upgrade from an ISY99i to the new eisy r2
Programming the eisy is very similar to the isy994i that you're already familiar with. The harder part (that we're all dealing with right now) is switching over to eisy-ui. It comes with just using it.
-
Upgrading ISY/Polisy to Eisy
Yes, the Polisy is officially no longer supported, and a few things like Matter won't work on it. It will also fall behind over time because it's version of FreeBSD cannot be upgraded to the latest versions. But eisy-ui does work on it. I have a few Polisys that I use for testing. Just from your user name, I'm guessing that you have several buildings in a camp layout. Depending on how far apart the buildings are, Insteon may or may not work reliably across gaps if the distances are too large. You would need to test this first, with something like appliance or lamp modules to see if you can reach them. I hope you at least have dual band devices.
-
Upgrading ISY/Polisy to Eisy
The new user interface is eisy-ui. It's still in development, though largely operational now. Some key features such as Find/Replace are still missing. They are tageting mid December to have it complete. It works on both the Polisy and the eisy. You can currently still use both Admin Console and eisy-ui, though you'll find some things not looking quite right in Admin Console with the newer IoX releases. Yes, that should largely be easy to do. Yes, though you'll need a USB to serial adapter, because the eisy has no serial ports. Yes, you could combine several controllers into one, if the device commuications can bridge the physical area. If you have Z-Wave devices, that can be a bit more work to carry over.
-
Looking to upgrade from an ISY99i to the new eisy r2
The documentation needs to be updated (isn't that always the case?). UDI now supports several dongles, some of which do both Z=Wave and Zigbee. The supported dongles are listed here: Universal DevicesProtocol SupportSupported Protocols: Z-Wave - Requires an external dongle (not included) - See supported dongles Zigbee - Requires an external dongle (not included) - See supported dongles Matter - Included for WiFi
-
How to add old X10 devices to EISY-UI?
Even IBM sold X10 devices, under the Home Director brand. I remember seeing live demos at the Comdex shows in Las Vegas. It really was the future, and suprisingly affordable. You can see the whole list of companies that sold X10 devices under their own name: https://en.wikipedia.org/wiki/X10_(industry_standard)
-
How to add old X10 devices to EISY-UI?
Radio Shack's house brand for X10 devices was Plug 'n Power.
-
How to add old X10 devices to EISY-UI?
The old geezer club showing through!
-
How to add old X10 devices to EISY-UI?
I'd be curious to know how many of us went with our UDI controller because it supported X10. It allowed a progressive migration. Count me as one.
-
Introducing eisy-ai !!!
Actually, knowing our token usage would be a good part of learning to use eisy-ai. It would allow us to guage our activity to a cost. Is there a way to see it ourselves?
-
Introducing eisy-ai !!!
Same here, I couldn't get anything done on it this evening either. Seems disconnected in some way.
-
How to add old X10 devices to EISY-UI?
You can add them as you manually add Insteon devices: Go into Insteon -> New Insteon Device, and key in the X10 address directly, eg: A1 and give it a name.
- Webinar Roadmap