Geddy

Glad you got your device issue figured out. Where are you seeing this? On the forums? Are you on a computer or mobile device and how are you accessing the forums? If you have any plug-ins that block cookies it might be causing you an issue.

You could contact sales@universal-devices.com and ask about having it combined to save them (and you) on shipping. The issue is with pre-orders it's geared toward only that device. You could probably add both to your order once general ordering is available. I don't want to take anything away from what UDI is offering, but if you're worried about shipping you can source the additional cable from Amazon as well. https://smile.amazon.com/gp/product/B00IDSM6BW/ Both the adaptor above and this cable have been offered as options in the past. UDI appears to have sourced product so users could buy everything from one place. Indeed, it's a shame you can't order to the pre-order, but I'm sure they can make it possible down the road.

Your link just goes back to the OP post.

Check this product out: https://www.amazon.com/StarTech-com-Serial-adapter-DB-9-RJ-45/dp/B00006IRQA/ This would work. There is specific pin setup information though in posts that @Brian H has made in the past. Most frequently found here.

Looks like it is an issue from the google group for this product: https://groups.google.com/u/0/g/wireless-sensor-tags/c/pvdH3fe-Ugk Wonder if it might have been the start to cause the tags to not reach the manager yesterday...that @johnstonf had and I had for a slight while.

As @lilyoyo1 says it seems to be old information that is no longer relevant. V3 was released in late 2017 (I believe). This area is probably left over from V2, prior to Echo devices having groups (as @oberkc points out). Further up in the "Migrating to V3" section there's mention of groups so they've been around since V3 came out. What's strange though is that I never set mine up with different accounts. So either didn't care about how different echo were controlling devices or just didn't need to have that option. It is nice to have the room groupings. Nice job reading all the way down on the wiki.

@matapan never seen that. Can you post the link you reference? I’ve got several Echo devices and just use one account. Never had a problem.

@Envirogreen you’re logging into PG2. You need to add :3000 after the Polisy IP address. That should get you to PG3 you then can setup the ISY on Polisy. Be sure you read the Polisy User Guide in the Wiki. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Also, on the PG2 side if your ISY994 is really 5.3.4 then it doesn’t look like PG2 can access the ISY correctly (probably user name and password issue or pointed to bad IP address for ISY994. It isn’t matching your firmware you show in the other screenshot.

Yes, you can push PG3 to the standalone ISY994. That ran just fine before IoP started. You just need to change the ISY settings in PG3 to see the ISY994. Instructions: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs Just use the IP for the ISY994 and I think change the port to 80. Make sure you use the user/pass for admin to the ISY994. It should allow you to have 2 ISY instances running in PG3. Just make sure which one is active when you start adding node servers in PG3 so they'll push information to the proper ISY instance. Not sure what versions these are for. I think you mean 3.1.x. Mine is currently 3.1.15. I think 3.1.16 just came out yesterday and I haven't updated yet. If you now have IoP running check for the "Upgrade Packages" button in the admin console. No clue how this should work. I think you might still not have the portal setup correctly. Log into ISY Portal (my.isy.io) then in the top right click on "My Profile". Should pop up this box: Make sure that your preferred ISY is the one you've linked to Google Home. If you haven't yet migrated the Portal over to the IoP instance then it's probably still trying to communicate with the ISY994. Wonderful! And it looks like their tag system is back online (I was able to log in and see prior tickets a little while ago).

@elite-rob If Insteon switches it's possible they got locally linked and the ISY (994?) would not notice/recognize that link in the admin console. You can fix this several ways, but I think the easiest is to: Factory reset the switch. Then re-link to ISY. I think there might be a way to make this work without removing it from the ISY tree and right click on the device and "restore device" and it should write back everything the ISY has for that switch. I've never personally tried it this way, but saw an old post referencing this method. Note - It's often suggested when installing switches to always perform a factory reset before linking to the ISY. This clears out any existing links or strange QA codes that might have been introduced to the device from the factory. When linking to the ISY there's always the option to "remove existing links". This way sometimes help stops this from happening, but is not always 100% accurate. That's why some will always suggest a factory reset just to completely clear any existing internal memory. Google search for the type of switch you have to get the proper process for factory reset.

This is normal. When you log into PG3 it will also ask you to log in to the ISY Portal. That's how Node Servers are tied to the Polisy in PG3. This is acceptable and should be done as part of the logging in process. I think you mean your ISY on Polisy is 5.4.4. Polisy version is only found through SSH (sudo uname -a). You should be at 13+ (current is 13.1 I believe) Mine shows: FreeBSD polisy 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 releng/13.1-n250158-752f8 13d6ccc POLISY amd64 PG2 and PG3 are completely different systems. They never "work together". Seems as though you must have just started running your Polisy. Have you not had it running and updating along the way and just now trying to update it? SSH update really goofed some stuff up, especially on original units. There was an email, forum alert, and announcement about that so somewhere along the way should have gotten your attention. You should only update the Polisy through the method @Bumbershoot references above. The "Update Packages" button through the admin console of ISY on Polisy. Apparently that part of the wiki should be updated. A problem with having static files in live "documentation" means that when something doesn't work right the static document is no longer relevant. The only migration steps I find on the Polisy User Guide are: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Migrating_from_994_to_Polisy I didn't see a reference to a PDF in those steps. What are you following? Make sure you're reading the live documentation for the Polisy found in the User Guide portion of the Wiki. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide You should also review this for how to get PG3 updated to the latest: Additionally, the ISY on Polisy system is most recently on 5.4.5, but there has been no release announcement for that. Here's the 5.4.4 release info: I think the simple explanation is by not running the Polisy until now and trying to update it (sadly, following old/static documentation) might have created unexpected issues. Further adding to issues by trying to add node servers before Polisy, Polyglot, and ISY on Polisy were fully upgraded and migrated possibly added to the issue. For many the process has been simple. For a few it has been problematic (along the way), but a lot of long time users that know how updates tend to be for ISY will have been on the bleeding edge of the update/upgrade process and updating their units along the way. Indeed...this is a highly debated outlook by some around here lately. Sure, the ISY994 has been a rock solid machine for many years and people will set it and forget it. Sadly, as technology changes and new devices are released and the ecosystem is being developed it's probably better to have been active and remain current on updates and upgrades so the system doesn't fall behind at a stale state then create problems when trying to be brought up to speed and put into production use all at one shot. I think if you are able to get the device to update to the above current release levels. Then follow the wiki path of migration it should work. It seems to have worked for many others as of late. But, as you said...you have a pre-order Polisy. It's possible that additional assistance is needed for an original device if not already updated. Sadly, with the ticket system down and if you're not able to get support emails then there's little that could be done. If you email support@universal-devices.com and make sure you explain that you don't receive replies to tickets and with the ticket system down/unable to log-in you have no way to get the feedback I'm sure they will find a way to get back in touch with you.

Oh no! That's never good. Hopefully was easy to get setup again. That's insane to have to go that drastic just from setting an IP reservation. What make/model router do you have? Glad to help.

@IPapp If the errors were not giving you problems then they might be okay to ignore as they do appear in my error log, but very long time ago (probably around last reboot). Those could just be additional information at startup rather than anything majorly wrong. I just don't know. If you're able to log in without pop-ups or "system busy" issues then you're probably okay. On the configuration tab do you have Network Settings -> Automatic and have you checked "UPnP"? Mine is set to automatic, but I don't have UPnP active. I have an IP reservation on my router for the ISY so it's always at the same spot. Ages ago the theory was to have static IP set at the ISY994 level, but many people would have to replace routers and end up with a different subnet for the LAN and the ISY wouldn't reattach. The more current solution is to use router IP reservation and allow the ISY to connect to the LAN automatically. If you keep having errors every few minutes or faster then it's time to open a support ticket to have the issues reviewed and possibly troubleshoot further. But, if they're limited to soon after rebooting the ISY994 it should be okay. Glad you got the biggest issue resolved of getting back into admin console without the system busy issue.

Take a look at this for the error codes: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages Looks like might be network issues. Make sure all wires are connected to the correct ports and pushed all the way in. What lights do you have on the front of the ISY994? See the Wiki for what light patterns mean. How old is the ISY994? It’s possible the power supply could be going bad. If the blue light isn’t brighter than the sun and always in replace the power supply. (Info in the wiki for options to replace it with). What ISY firmware are you on? Post a screen shot so you also confirm FW/UI match. You might need to save the error log and open a support ticket to get UDI to troubleshoot further. (The 170001 is usually informational (to who and why I have no clue, but having a bunch is not good as something is going on that probably shouldn’t be. The 140000 is a DNS issue so suggests network problem.) Do you have an ACTIVE ISY Portal license for this device? It hasn’t expired has it (if you have one)? The ISY could be trying to confirm the portal license and getting an error. Just another thing to check/confirm.

That forum notice was only temporary to attempt to avoid such a post. I think it was only set to run through yesterday. Since the communication said "hopefully sooner". I too hope they can get it updated soon.

Not having this issue. Doubtful that it's the whole issue, but you need to update your Java. Current version from java.com is Version 8 Update 351. Delete previous copies of start.jnlp or admin.jnlp (be sure to look for multiple copies of same file i.e. start (1).jnlp) After you do that: clear your java cache, (Be sure you check/select all 3 boxes in this process!) download a new start.jnlp file from the Universal Devices site or through the Wiki. Once you are able to log into admin console confirm your Firmware and UI match (Help -> About). They should match EXACTLY (even the date/time code). Other items to check: Is there a steady bright blue light on the front of the ISY (if not see here). Do you see the ISY as a connected device if you log into your Router? Can you ping the ISY from your computer? You say UD Mobile works "most" of the time. Is that accurate or assumption? If really is "most" of the time it sounds like a network issue. Log into my.isy.io and check the error log (Tools -> Select Tool -> Logs) to see if there are any significant errors seen. Check error codes in this wiki article Let us know how things look once you check/fix/update the above.

@EWhite might be good to mention @Panda88 to get help from the developer. Looks like they're following the forums and should get a notification, but sometimes mentioning like that might send an alert to get quicker assistance.

Sorry you feel that way, but your post has the most replies for the day so far. So yeah, guess it's buried real good. Your question is more related to how Mobilinc can integrate with UDI offerings so this is where it belongs. I think you have a different view than most on how 3rd party applications work. UDI develops hardware and systems to control a multitude of devices. 3rd party developers then need to figure out how to integrate into such a system. Would be interesting to know what @InsteonNut is "waiting" on from UDI. As far as I see it the Moblinc (Pro) that I've used from day one still works just fine for my needs. But I don't get all "fancy" as you so I haven't had any compatibility concerns. I think most ISY users would all consider themselves fairly deeply invested. I mean, we're not the type that just buy a system and the hub that goes for THAT system. We saw the value that Universal Devices brought to the market with a controller that was more advanced than a standard hub. The technology and desire to grow has evolved over time. It's great to see the Polisy (and next eisy) development. But it's still up to those 3rd party developers to work with the products available in the market place or say "we no longer support" something. The Polisy has been out for many years. If Mobilinc isn't supporting something for it then you've got to ask them why. If they don't have an answer then figure there's a reason for lack of support and sadly, probably never will support if they haven't by now. And that's a huge benefit of a system that works as you have designed it. UDI developed hardware and systems that work. They have not "dropped" the reliability for their equipment that continues to be used by a wide market. They began developing for the next generation with the Polisy and now the next with the ZMatter and eisy products. It just seems like you've really done a lot of individual manipulation that you're coming here to complain that you can't just move your efforts into a new system. Then asking/expecting UDI to make some sort of concession to fit your need. Innovation hurts sometimes. But that doesn't mean it's a bad thing. Hopefully you get your answers from Mobilinc as to what they can (or cannot) do going forward.

From the wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Creating_a_KeypadLinc_LED_Follow_Program Also in a couple of places in the cookbook (Page 99) (Page 115) (Page 282) (Page 334-335)

Guess you missed the link I had in my earlier reply. Nope. Hasn't allowed logins since February 2022. There were several emails about that and a post on the announcements area of the forums as well as mentions of this on the wiki.

@JTsao what you describe doesn't mean that it's Polisy related. Both issues seem (to me anyway) might relay on multiple systems talking/reacting together. That would rely on localized transmission speeds. #1 - Not familiar with either note, but if either are cloud based have to account for communication beyond local network. Plus, the fact that Polisy doesn't have IR so a slower signal might have to travel and be computed by a system that is faster than a simple button press. #2 - "Z-wave" - I'm not a z-wave user, but from reading here that's just a hit or miss issue at times. I doubt that's Polisy/PG3 related. Of course...having large systems can tax any system, but I think these aren't resource dependent on the Polisy. If a major issue then I would suggest opening a support ticket to see if indeed there was an issue with the Polisy.

There were a few modules that UDI has supplied in the past. As far as I can tell the Elk module is really the only one that went away in favor of a more robust Node Server (mostly in PG3). It's been communicated through various emails from UDI when Polisy was first announced that Elk module would be going away in favor of the node server. I think perhaps those notifications only went to those that purchased the Elk Module from UDI and not a full customer distribution list. Another that I remember was the weather module (again, not something UDI could control), and again a lot of communication came from UDI before (and after) the weather module went away. When PGC began as an option for people not to have to have the skill/ability to run a rpi to run PG2 locally it added a lot of functionality without additional equipment. That's how I interpreted the statement. I saw that there was a NuHeat node server available on PGC and figure since it shut down in February I wonder why it took until now to get this question. Perhaps it just got cold where @EddieRock lives when he realized the ISY wasn't doing something with the heat system. There were a couple of emails sent by UDI when PGC was shut down. Due to the severity of the issue there was little (to no) warning that PGC would be shut down. At that time there was available Polisy equipment that users with mission critical PGC nodes could have purchased with a generous discount offered from UDI. So even if not reading the forums the effort was certainly made to get the word out about the change. Why thank you! 😊 But it can run with the existing ISY994. At least in theory. None of us know the full abilities of the eisy (not yet released). If running a rpi with PG2 installed it would feed node server information back to the existing ISY994 (there does appear to be a NuHeat node server in PG2). Additionally, if @EddieRock was able to source a Polisy it too can feed information to the existing ISY994, but also can replace the ISY994 with the latest ISY on Polisy (IoP) service. The only issue is that the Polyglot Cloud is no more so additional equipment is needed, but most certainly, the existing ISY994 could still remain in service. Just need the equipment (and ability) to run the node servers now. Simple? Depends on ability. Ideal? In the mind of the beholder. I completely 100% agree with you. Having a family, full-time job (remember, I don't work for UDI), and other hobbies, reading lots of posts is not always possible. There is a search feature and a Google Site Search function that both tend to work well for many issues people might have. Although most figure they don't have the time to search for their issue and just quickly post when a well phrased search (especially with Google Site Search) can usually result in a good starting point for information or support. But you're also correct...lots of users here have really been helpful. That's why I felt moved to step up to volunteer to help give back to the community from all the help I've received through the years. I appreciate the discussion, but I think beating the dead horse much more would really drift off topic of OP. 👍

Do you think you're having performance issues? Polisy should be well overpowered to run so much more than it is that this would be the first time I recall somebody suggesting having performance issues running PG2 and PG3 concurrently. If you're worried about resources you can delete/remove all node servers from PG2 so at least those processes aren't running, but I figure you've already performed that process.

@Dr Neal Phillip welcome to the Universal Devices forums for support for products and services provided by Universal Devices. Perhaps your question would be better supported in a forum for the product you're using.

If you have (or create) an account at the Universal Devices site you have the option to sign up for newsletters. I'd suggest signing up for the "Product News & Announcements" list at the very least. That should get notifications when the eisy is available for pre-order. Also (FYI), I'm not affiliated with Universal Devices in anyway. I'm just here as user-to-user support like most of the rest of the forums. I just volunteer to try to keep the forums a little more organized and on topic (at times). But I get what you mean about trying to find information. It can be daunting at times...that's the life of working directly with the hardware developers...they develop...they don't always document/market the way some might expect/desire. Many users on the forum have formed a good support network for the user-to-user base that many are here regularly to keep up with what's going on and on the horizon.