ferventgeek

Thanks Geddy. I checked from the other machine and you're correct- it's a Mac issue. On Windows, Java is using a "+" icon from deep in a win32.dll somewhere, while in Mac it's using something different. It appears as a down carrot, in a gray color almost the same as the background. So the workaround is click in the "blank" space left of the object to open. Thanks for the tip. "Java: write once, run anywhere". lol. (and I was a Java dev long ago..)

There are no pluses to expand. That's the issue.

I'm probably missing something obvious, but there are no device tree views under any scenes in the admin console as described here, so there's no way to remove a device from a scene: https://wiki.universal-devices.com/ISY_Users:V5:ZWave:Advanced_User_Guide:Scenes#:~:text=as%20a%20Responder-,Removing%20a%20Controller%20or%20Responder%20from%20a%20Scene,Native%20(Controller%E2%86%92Responder) Without the tree view how do we removed devices from scenes? Firmware loX v.6.0.4 ( 2025-12-18-18:51:58 ) UI IoX v.6.0.4 ( 2025-12-18-18:51:58) Product eisy (5226) OpenADR (21010) Networking Module (21040) Portal Integration - UDI (21075) Z-Wave Module (21100) A10/X10 Module (21060) Thanks! Patrick

Thinking. They host raspberry pi's online... how much a month would someone pay for a hosted Polisy with SSH access? 💰🦾😂

Thx Guy. I'll message with the details.

I have an original blue-box Polisy with power adapter and 3D printed wall mount plate that's looking for a new home. I've migrated everything to the eisy now and I hate to stuff it into a storage box. Donated as-is, the firmware will need a re-flash since it's old and had more than a little SSH jiggery-pokery. Cover the shipping and it's yours. ✈️ 5/21 Update: It found a home, thanks, community. (Please let me know if it's not ok to post this here.)

Thanks Bob. I'm also tweaking my IsyJson gateway to decode Unicode from Isy. Ex, formatted=: <property name="Feels Like" prec="1" uom="17" formatted="80.4&#xb0;F" value="804" id="CLITEMP"/> Didn't realize that's the serialization format for the UD Java console, but that makes sense for its heritage, vs UTF-(8/16/32) string encoding. I worked in EBCDIC back in the day, and ISY's stalwart ascii is just fine. Cheers.

Thanks will do. I might remove and reinstall it to get the specific error message. The "stuck" stake flow is: install plugin, get red "you need to set your API key" box on the detail page. Set the key from Ambient Weather "You need to set key" box remains 2nd box also appears with a message that the API request to AWN isn't authorized, and it includes the url the plugin is trying to hit. (Interestingly if you cut and past it into an editor, there's a space in the url after the AWN endpoint and before the path. IF I remove the space and put it in a browser window it works.) I can wait hours and it remains in this state. Restart / Stop / Start on the plugin does not clear the error. Reboot eisy, and the problem goes away. Like I said it would interesting to remove and re add it to see if it's repeatable. It's a great plug in and I showed an app demo of the PG2 version on stage last year for 1,500 observability geeks. IsyJsonGateway, FTW. Thanks for all your work on these plugins! 🙏 { "ResponseJson": { "properties": { "property": [ { "@id": "BATLVL", "@value": "0", "@formatted": "OK", "@uom": "25", "@name": "" }, { "@id": "CLIHUM", "@value": "73", "@formatted": "73%", "@uom": "22", "@name": "Humidity" }, { "@id": "CLITEMP", "@value": "796", "@formatted": "79.6°F", "@uom": "17", "@prec": "1", "@name": "Feels Like" }, { "@id": "DEWPT", "@value": "692", "@formatted": "69.2°F", "@uom": "17", "@prec": "1", "@name": "" }, { "@id": "TEMPOUT", "@value": "7862", "@formatted": "78.62°F", "@uom": "17", "@prec": "2", "@name": "Temperature" } ] } }, "Endpoint": "isyportal", "Command": "status/n004_ec63155_5", "Timestamp": 1747150361.696, "IsoTime": "2025-05-13T15:32:41.696+00:00" }

Thanks. It's only one plugin that seem to have an issue, for example AmbientWeather https://github.com/BME-nodeservers/docs/blob/master/udi-ambient-poly.md which returns permission errors from the server until PG3 is restarted. (Plugin restarts don't clear it.) I'll SSH in for reboot. That might be a fun plugin for a weekend project. Or, on second thought, hacking a plugin to do random SSH commands might not be something to release. 😂 I am however, thinking about a plugin to bring in metrics from Grafana/Prometheus, and an OTel event forwarder.

Does clicking "Restart IoX" in the UD Console also reboot the eisy and with it PG3? I'm confused about how PG3x and IoX share the eisy hardware. As a former PM, I'm sure there's a PowerPoint with layer boxes and client apps, likely with the FBSD kernel at the bottom, then C++ IoX and Python PG3 on top of it, each with independent HTTP service ports. But what I can't deduce is the relationship between IoX and the platform in terms of PG3. The "Multifunction button" doesn't seem to do anything if you press it 5 times, and I hate to power cycle the platform just to clean up occasionally wedged PG3 plugin states. So really, a few questions for you gurus: Does the "Restart IoX" button in the UD Console also restart PG3? If not, where is the widget to do that? What's the process to soft reboot/gracefully powerdown the eisy? Is there a command line option for the eisy to do this? OR just used standard FBSD shutdown -p {or -r} now command and IoX and PG3 gracefully exit on the OS halt message? Thanks for your help, and I appreciate you looking at it here since this also applies in the eisy and IoX forums.

Oooh.. sweet! Thanks Guy! Yeah it feels like there's an opportunity for a USB cable connected wall mount enclosure as a sidecar. Having the dongle hang off the USB port with those big antennas feels a bit sus, plus it would be handy to mount the ZMatter's antenna array independently of the eisy. Nice work.

Thanks bpwwer. Yes, the controller coincidently died two days before I tried to migrate the Polisy PG2 Node Servers to eisy PG3 plugins. So, I replaced it with a Rachio, and support helped me swap out the RainMachine plug-in for one for Rachio. It's working great. But bigger than that, I'm done with the overall project: old ISY99 + early separate blue box Polisy + lots of mixed Insteon and Z-Wave + 12 years of automation code + AWS and other external portal integrations + 6 Node Servers.. now all on one eisy. Maybe ten hours total planning, acquiring parts, and prep here and there over three of months, then the actual migration took less than an hour. Michel was awesome with helping resolve perquisite issues, and it worked as described the first time, including pulling all the Z-Wave nodes over.

Will do. Thanks!

RainMachine sprinkler controller.

It looks like a device controller isn't accepting connections from the new plugin I bought today because they're going out of business. So with the device dead and no replacements coming the plugin will never work. What's the process for getting a refund from the PG3 store? Thx!

Thanks Guy, that's the doc I'm looking for. An unexpected requirement for snapping a card in half should have something from the manufactured describing the process. I snapped it off and it fit in the case. Related:

Looking at the site and forum, I don't see a manual for inserting the ZMatter card and antennas into the case. The clearances for the antenna mounts are fairly tight. Even a couple of pictures would help. However the images on the ZMatter card in the store don't show the card and antenna leads installed. There's no document in the store under "Additional" and there was no insert in the package with the card or enclosure or QR code to docs. Hopefully Google and I are just missing it somewhere. If it's not documented by UD, would one of you have photos of the correct internal layout of the ZMatter card in the enclosure? Thx!

Whelp, it looks like Polisy updated some of it's modules but now the node servers won't start. This an original Polisy unit, and as I recall requires manual updates. The Node servers are Polyglot v2.. I know. Version 2.2.13 Frontend Version: 2.2.9-5 Based on this error, I'm guessing the OS needs an update: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/lib/libpython3.9.so.1.0 not found What's the manual update process for this unit to get it one with the release steam? Not seeing it in releases or in posts. Thx!

Thanks Geddy! 994i Pro - Thanks, I updated the post USB PLM - I bought it as soon as Instron had them back in the store. Seems like the right route to eliminate the need for the blue adapter cable (with another inline processor), and it's 10 years newer. Since that is the most critical interface, I'm trying to make it as reliable as possible. So in this regard the ISY994 to eisy is a one way trip and there's no way to know if going from the 994 on it's serial PLM to the eisy on a new PLM will work? Portal - Yes I'm letting go og MobiLink. And I already interface all my external integrations via a custom AWS Lambda function, so that will be a single point for any modifications to the XML API. (The lambda is an XML<->JSON gateway with additional features and fine-grain RBAC auth.) Polyglot - I'm running both 2 & 3 on the Polisy as there are a couple of legacy PG2 plugins that aren't available in the store. I'm assuming that the eisy can run both Polyglot's like the Polisy. If not, it's a dealbreaker for now, as I don't have time to hack PG3 versions of both. Thanks again for your assistance. It's a lot of moving parts, each of which has "should" work's.

I’m going to bite the bullet and finally combine all of my accumulated UD gear into a single eisy (assuming they come back in stock). I’d love for you experts to weigh in on my upgrade plan. Here’s my current, reliable if old, setup: ISY994i Pro (Instron and Z-Wave devices) Polisy with PG 2 & 3 Plugins and lots of integrations ZMatter card (never installed) Instron serial PLM MobiLinc portal for remote APIs I'm planning to migrate all that to eisy using the following path. Please let me know if you think this will not end well. On the existing isy994, migrate from the Instron serial to a new USB-based PLM. Let it run for a couple of days to ensure all is well since it’s the house's core. Put my never-installed ZMatter card into a ZMatter USB Enclosure from the UD store. Plug the now ZMatter dongle into the eisy Do the backup migration from the ISY to the eisy Migrate remote management to the ISY Portal Troubleshoot Z-Wave Do the backup migration from the Polisy to the eisy Profit? Thanks for your assistance!

Thanks. It's hard to know where to post platform interface questions. Because the ISY source is closed, it makes sense that core dev support is also closed- i.e. no public forum. However, the REST interface is documented, minus it's primary interface schema. Mostly I try to ask the community first for self-service, before bugging the Universal Devices team. I'll ask them directly.

Is there a magic link to an XSD or other doc for the ISY XML schema? I'm finally converting my handicraft XML to JSON converter to a Python library, and am wondering if the official ISY XML schema is available somewhere. I've been lucky to find several great libraries to draw from, but each has it's limits. Generally, they only convert what they need to based on white-box understanding of a subset of XML responses. This makes sense- why reverse engineer every possible message and device type if you don't have to? However, I'd like to clean up my transformer to look as close to an "official ISY" JSON response format as possible, then do the app specific transforms on that. There are great general XML->JSON libraries available, but end up including unnecessary or duplicated meta that a schema-aware transformer would omit. Thanks!

I have the serial Instron PLM, not the USB version. USB would be a non-event.

Google + Thingaverse are magic. This just showed up today, fits perfectly on my Polisy. Slight delay of game for the Zmatter driver, but getting really excited about the migration from my ISY994i. Chipset troubleshoot yea verily, firmware team! My wall is ready. https://www.thingiverse.com/thing:5221086

Thanks Michel. I did, I’ve got it sorted