ferventgeek

No. I'm here to understand. I also accept that like Linux and Apple forums, members in any community- no matter how otherwise excellent- can become so attached that honest questions seem like attacks. And if you spend time in those more toxic forums, you can appreciate how important it is to welcome newcomers. Especially for complex pro-sumer gear like UD. That begins by assuming that even stupid questions are exactly what they seem to be. It assumes new members aren't on a mission to badger an old guard. It assumes a poster's frustration is driven by a shared passion for the community and a desire to find answers. It assumes new members are eager to deepen connection with experts. That's how great communities are built. I urge you to review my other posts in these forums and assess my intent. You'll find nothing from me where I'm sarcastic toward other members, much less basing the first sentences in posts that way.

Right? Putting my software product manager hat on, I think the logic goes something like this: The ISY can't support two portals. Mobilinc was THE portal ISY "portals" was originally that UD extension working with Wes Later, UD Portal would use the internal ISY C library API first created for Mobilinc The goal would have been near-zero changes for the portal hooks in ISY The only way now to support both portals would be a decent chunk of new ISY code UD would need to abstract portals into a class, and manage messaging for a list of them That code would need full regression testing and change the UD support process All that adds to costs and risk and UD PM didn't see the value The future of UD is an all-in one that combines the ISY heart with Polyglot node adapters to deal with the never-ending parade of proprietary home automation protocols UD would love a modern re-write of ISY, including a modern JS UI to replace the Java console, more advanced logic, and abstract node definitions within ISY. However that's waaaay out of scope. Therefore, UD needs to support the device with a SaaS interface based on what they have on the truck. And Portal needs to be stupid-simple to configure and ready to go UD PM had to make a choice There aren't resources to extend the internal ISY portals interface They have to have OOTB portal working to drive adoption (accelerate UD onboarding) So it's UD Portal, sorry Mobilinc I've stayed with Mobilinc for two reasons The main one- I don't want to have to reimplement integration code and re-deploy several AWS and Azure interface services. Also, regression testing for human-factors driven long-cycle async code takes weeks to catch edge cases in API quirks. Mobiinc has been rock-solid. Looking at the US Portal forum, that's perhaps not the case just yet. So, I'll adapt.

Thanks. I already built something like that- golang subscriber pushing to AWS SNS. Still hoping it will eventually be built into a portal. The old SOAP wrappers have all the magic.

Thanks. Yes, everything has been centralized on my ISY for a decade. I've watched protocols come and go. That's why losing connectivity (without re-implementing custom integrations via Mobilinc) is painful. I'll effectually lose the center of my automated world. I'll stay on the ISY99 until I have a solution. Maybe an intermediate AWS Lambda function that's UD Portal on the backend, and Mobilionc REST on the frontend. They're both wrapped local ISY REST.

Ah. I just followed the emails. "Hey we have Polisy now for node integration" - bought one. "Hey we have an updated Z-wave+ module for the ISY" - bought one. "Hey we have a new card that lets you migrate ISY to your Polsy and get Matter and Zigbee" + pre-ordered on announcement day. To find out this late after all the announcements, documentation review, and purchases that my primary interface to my home automation may have been been cut.. is more than a bit of a surprise. And disappointing. This isn't a rant- I'm invested pretty far in.

I did, before posting this. They are waiting on UD, thus my question here.

I'm looking at the Portal API in case I have to move away from MobiLink with a shift to IoP on Polisy. Does the UD Portal support REST subscriptions? https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface#Subscriptions_(Web_Sockets)

I'm not sure I agree with moving this topic to MobiLinc- seems a bit like burying it. There haven't been any meaningful updates in this forum in a while. The problem is that Polisy and IoP is supposed to be the next iteration of UD. Mobilinc is not a new feature- in fact it's the original integration portal- delivered years before the UD Portal. Its absence in Polisy is a feature regression, especially for me. I have several integrations including a demo kiosk that goes to enterprise IT shows where visitors can trigger automation actions based on machine learning. So is the answer to my original question, "we're choosing this migration to EOL Mobilinc in favor of our own competing portal?" I'd hate to think that.

Checking all the details before migrating off my ISY99, it appears MobiLinc Portal isn't supported on the Polisy. Is that true? I have a lot of 3rd party integration via the MobiLinc API and this may be a dealbreaker for migration. Hopefully, I heard wrong. Is it supported, and if not, when will it be?

Correct. I have the adapter ready, and am checking all the dependencies. It's a simultaneous zmatter install -> migration, so I'm checking everything I can beforehand.

Ahhh.. That's the value coming from the ISY99 via {host}/desc, not the local IoP server. Thx Michel.

I've tried rebooting and restarting and updating and all the things, but still see mismatching version numbers in Polisy. Is there magic for this? (Getting ready to move to the Zmatter card). Thx.

Thanks. Oh yeah, I'm on the list

Thx all for the links to the official UD cable. I try not to create e-waste and wouldn’t use the serial to USB or Ethernet cables. But if the $3 homemade adapter option doesn’t work then I’ll get a cable. Hopefully USB PLMs will come back in stock and I’ll eventually move to that, and make the existing 10yo adapter the backup.

Thx Brian. I should have labeled the connector as female front. This would be the view looking at the end of the connector not the back of the plate.

Thanks @Geddy @Brian H does this look correct for https://www.startech.com/en-us/cables/gc98ff?

I'm ready to migrate my 99 to my Polisy, but for one thing- no serial cables available for the PLM. Womp-womp. https://smartenit.com/shop/plm-serial-cable/ are out of stock. Is this a standard cable, or is there a published pin-out so I can make my own? Is it a standard console cable (AKA Cisco blue? https://www.amazon.com/OIKWAN-Rollover-Console-Management-Adapter/dp/B08V539JMQ) Thx, I can't wait.

Thx @TexMike, that's perfect. I'm running the ISY and Polisy off UPS-backed PoE with the rest of the core network, and didn't want to jam a plug over the pin. I'll make a cable for it, and this time 5.5 x 2.5. Thanks! ?

I'm finding standard 12V wall warts work fine on the ISY99, but not the Polisy. The Polisy jack's center pin appears to be a bit larger than on most 12V connector plugs. Is it a different specification? Strangely, a lightning strike took out the Polisy brick and I subbed an old one from the ISY, no issues. Thx!