Developer News

News for developers.

, , , , , , 0 comments

Develop, Debug, and Test IoX Plugins

Editors, NLS, NodeDefs, Status Names, UOM… Why, oh why?!

If you’ve ever tried wrangling these beasts, you know the pain. Constantly hopping between text files, XML files, and Python files, trying to keep them all in synch. Pulling teeth is less painful! And then there’s debugging, like finding a needle in a haystack but blindfolded.

I’ve been there. Developing plugins like YouTube, AudioPlayer, Drip, Modbus, and others felt like surviving an escape room designed by a mad genius for a mad genius. At one point, I genuinely questioned, Who in their right mind would willingly develop plugins for IoX? (No offense to my fellow geeks who already have.)

But instead of giving up, I thought, What if I could make this process eisy? (Yes, eisy)

So, I rolled up my sleeves and set out on a quest to eliminate the misery. My goals?

  1. Only One JSON File: Because juggling multiple files is hell. This JSON file describes everything—features, properties, commands, etc.
  2. Smart Editing: An editor so intuitive it practically writes your JSON for you. Need valid UOMs or valid elements for editors? Just pick from the list, and boom—you’re done. No second-guessing, no “why is this broken?” moments.
  3. Automation:
    • Auto-generate Python code stubs, so you only fill in the logic without touching the boring boilerplate.
    • Automatically publish your plugin to the local store, like magic but geekier.
    • An execution environment that lets you run and debug with breakpoints immediately. Yes, immediately. Like, before your coffee gets cold.

And guess what? I nailed it.

I chose VS Code as the IDE and developed an extension called IoX Plugin Developer. It does everything except make your bed. And the best part? No tedious installs or configurations. Just type ide in the terminal, sit back, and watch as all the extensions and libraries set themselves up.

Setback!!!

Ah, the sweet taste of victory—short-lived, of course. While basking in the glory of my creation, I shared it with a few developers, only to be hit with a humbling realization: I had completely missed a crucial point. I’d naively assumed that everyone develops directly on eisy. Because, obviously, who wouldn’t want to?

Spoiler alert: Nearly everyone. Boy, was I wrong.

Determined to fix this oversight, I searched for a solution. And wouldn’t you know it? VS Code already has a remote development extension. 

With this newfound wisdom, I updated the ide command to do even more magic. Now it automatically installs all the necessary libraries so you can use VS Code on any machine, and it’ll feel like you’re working directly on eisy. Glory restored!!!

Here are the instructions.

Jump In + Discounts + More !

Now that developing plugins for IoX is no longer a test of your sanity, why not jump in and help us make it even better?

Get a $26 Amazon Gift Card
Already have an eisy? Develop and publish your first plugin using the IoX Plugin Developer, and we’ll send you a $26 Amazon Gift Card as a token of our appreciation.

Get 15% Off eisy
Don’t have an eisy yet or need a dedicated development unit? Grab one at 15% off with coupon code WVS29RXH. Hurry—offer expires 12/01/2024!

Ready to make your mark?

  •  

, , , , , , , , , , 0 comments

Supercharge Your eisy!

Now that you’ve enhanced your eisy with added storage and a virtual machine (VM), you may wonder how to further boost its performance and reliability. Well, wonder no more! Our latest blog post will guide you through the process of configuring your eisy to boot from an NVMe SSD, with the option to use the onboard eMMC drive as a mirror for redundancy. 

You don’t have an eisy yet? Get 12% discount to upgrade!

Yes, you get 12% discount by using coupon code ER622HZH (expires 2/20/2024).

If you’re upgrading from a Polisy, you will also get an additional $30 refunded back to your CC. Once you place the order, please send an email to sales with the copy of your invoice/order for Polisy.

What do I need?

  • 1 x eisy
  • 1 x Serial PLM Kit if and only if you are using a 2413S PLM. You don’t need this if you are using a 2413U
  • For Z-Wave
    • If your Polisy already has the ZMatter dongle, then all you need is the ZMatter USB Enclosure
    • Otherwise, and only if you have Z-Wave devices that you want to migrate: 1 x ZMatter USB

How easy is it to upgrade?

If you have a Polisy or 994 with firmware versions 4.x or 5.x and don’t have any Z-Wave devices, it’s as easy as:

  • Backing up your 994.
  • Disconnecting the PLM from your 994 and connect it to a USB port on eisy using the Serial PLM Kit.
  • With one click, migrate your ISY Portal License as well as Alexa and Google Home configurations to your new eisy.

If you do have Z-Wave devices, and don’t already have a ZMatter dongle, due to the nature of Z-Wave routing algorithms, migration might not be as seamless.

Here’s the link to the complete migration instructions.

  •