Geddy

What version Polyglot are you running? At the bottom of the dashboard (or almost any PG3 page) what do you have for version? I'm currently running 3.0.63 and Hue NS runs fine in PG3. Perhaps this is something the developer @xKing can help decipher or else you might need to PM them your full Hue log file for them to check. My hunch is that you might have updated PG3 with an SSH command recently (it's not advised to do that currently) and you might have corrupted some UDI files. Since this isn't being reported by many others you might be better off with a support ticket with UDI for them to review PG3 logs as well. However you get things working please post back here to update what helped resolve your issue incase others have a similar issue. And yes, as @lilyoyo1 says it wasn't anything like the thread you posted in. So moved out to its own thread for additional attention. Thanks for posting! Hope you get things working soon.

@dinostop merged your post into this issue as it referenced same issue and @Michel Kohanim has confirmed this is a known issue that is being worked on.

@Schlyguy try logging into alexa.amazon.com Click on: Smart Home -> Devices Do you see more than just the few devices you've setup from Portal? Should have all spoken listed. It sounds like you might need to open a ticket with UDI asking about the portal. Perhaps there is something they can get from your logs to figure out why Alexa might be able to trigger something that isn't specifically exposed to the skill. I think it's something @bmercier might need to review.

Regardless of the device. Scenes are what link switches within the ISY control. That is if you want the ISY to know the status of the switch at all times. If you have manual links ISY might not get updated if the switch isn't reporting to the PLM. Maybe review this video for scene making: https://youtu.be/hbkFnzBhKB4?t=436 Also read through the Wiki - https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:How-To_Guide#Scenes (Most of the wiki scene information was written prior to or during 4.x firmware and should give you help with windows you're seeing.) Your Patio/Spotlight example is something that could be done with a program for on and fast on. Scenes are handled much different now (in 5.x firmware). Most users have upgraded to 5.x so getting support in 4.x might be more difficult. I'm not suggesting to upgrade because that's a complicated process. I think you should fix/work out your issue before you consider changing firmware versions. Did you control the Insteon with a hub before going with ISY/PLM?

@landolfi moved over to IoP area since you're specifically referencing Polisy. You did not have the same error as the thread you originally posted. Perhaps @MrBill's suggestion of opening a ticket will get you the help you need. Are you trying to backup IoP (admin console) or Polyglot (web interface)? And you reference you found a link somewhere suggesting a bash command. Always good to include that link in your post so anybody trying to help you here can go read what you're talking about and not your interpretation of that issue. Good luck getting this resolved! Please post if you get help from UDI Support as to what was done to resolve this issue so that it might help others if they run into this issue as well.

This appears to be an AT&T issue. There was a comment on another thread about this...seems like AT&T is not picking up the correct "from" and just using string of numbers. I tested with ISY994 and IoP over the last week using T-Mobile and never got such strange looking messages. This still comes back to the suggestion that Email to Text is not the ideal way of processing notifications in 2022. There are Node Servers to handle pushing notifications to mobile devices either through UD Mobile or other applications (such as Pushover). Those options have many more functions and features than Email to Text. I think anybody using Email to Text should consider other options.

I don't know first hand, but there have been a few other posts about X10 working with IoP. Seems to be hit and miss. Here's one that might help:

@Sachelis well...in truth...the url you posted is "impossible" and "wrong". There was should have more to the URL. That's why I asked if you actually posted the bookmark URL or just summarized it. Looking back at some old 4.x release posts the URL had the version number behind the /994i/. I had to go back to 4.3.x release notes to find that. And yes...I remember the days of having to use IE to start the process. But even at the 4.3.x stage Chrome had removed such Java support so IE was the only way to still access it. That's why the ISY Launcher method was vital. It helped resolve two issues (reliance on IE to launch admin console and helped match UI/FW by default). I'm not at a decade yet, but just over 6 years so I remember the old process...vaguely. Thankfully, the new way is simple and easy. Let me know if you have any issues with it. Hopefully your ISY is somewhat up to date.

You're still having these problems? Didn't you post about that a year or so ago? I would have thought it had resolved. I would have scrapped Google home long ago if I couldn't make it work for something simple like that.

@TriLife Yes...well...I believe you can, it should be possible. Are you going to leave z-wave items on the ISY994? Also, since you are going to be removing the PLM from the ISY994 you should change the firmware on the ISY994 to the non-PLM version so if/when you log into the admin console it's not showing being in "safe mode" because there's no PLM connected. You can find the different firmware in the release threads. Basically, the Polisy would run PG3 and IoP. You would enable Insteon support on the IoP and then follow the migration process in the wiki (Polisy User Guide). Once you got all the Insteon devices moved over you should then reset the ISY994 with the non-plm firmware. I don't use Z-wave so can't help with the process there. I'm not sure if there's a way to backup just z-wave and then just restore that to the new firmware on the ISY994 or if you would have to set everything up again. I know @lilyoyo1 and @asbril more proficient with z-wave that they might be able to answer that specific process. There is still little known about the eisy. That's just been a few posts from UDI about that and think it's a new device that will work just like the Polisy. It seems that Polisy and eisy will maintain some similar support for the time being. PG3 is still the route that development appears to be going. It's so new that I doubt it would make a major course change at this point. (All just speculation...I don't know...I'm just a user like most of us here!) So I'd say stick with the Polisy since you have it in hand. Keep learning to develop for PG3. If you're in the UDI developer system then you have all the tools needed to keep current as Polisy and eisy are available and as PG3 continues to advance.

@Sachelis Is that URL you posted exactly what you have in your bookmark that you've used for ever? I recall "back in the day" there were links that were needed back when browsers handled Java requests and opened the admin console that way. Long ago browsers stopped supporting Java and how it launches applications such as the admin console. In 2018 UDI released the "ISY Launcher" method so a browser isn't required to access the ISY admin console. This "new" way is a cleaner, easier way to access the admin console. This process also always makes sure that the User Interface matches the Firmware of the ISY994. Since that was a large issue people were having as upgrades were being released over the last few years. There is an alternate way of getting the admin console file directly from the ISY, but it's just that the current suggested/preferred route is using the ISY Launcher process.

Go to this link: https://forum.universal-devices.com/forum/339-current-release-announcements/ Click the "Follow" near the top right and make your selection for how to be notified. When new posts are made in any category within that release announcement area you'll get a notification and you can read the post about how to update your system. There's no need to randomly update if there hasn't been a release announcement made. That's what gave people issues before.

This sounds like you’ve got a program stuck in a loop. @MrBill has made a post recently about braking the look so you can control the programs again. Check this thread out: Hopefully that gets you squared away. If you can get to the summary tab of the program see if one keeps running or see what’s most recently run. Post back if still having issues once you set the folder option to stop all programs. Make sure you just use this test folder option in the ROOT program folder.

@C Martin If you mean you clicked the right link seen here: That's trying to open Polyglot Cloud. And as @Bumbershoot points out that's been turned off for a while. That's not accessing any local/home Polyglot connection. Currently only the IoP process (as far as what's running on a Polisy) is accessible while remote (to the best of my knowledge). If you need to access your PG2 or PG3 while remote I think the only way to do that is run a local VPN to make a connection while remote.

@larryllix thanks! Just saw your post about it in another thread...

Got it. Just found that when I deleted the entry the program change to "[Entry #]". Appears to be a slight UI "bug"/anomaly. I suggest you start a support ticket to see if @Michel Kohanim can recreate on a test system. While I kind of see it happening it changes/updates if I click elsewhere and is correct when I come back to it. My test steps: Create notification customization of name = "test 1" Save customization Create test program w/ notification to "test 1" in "THEN" save programs exit admin console launch admin console - everything looks correct delete customization name = "test 1" save customization tab program now shows "[Entry #]" referenced where "test 1" used to be. save program tab exit admin console launch admin console program tab referenced "test 1" click "Configuration" tab -> Emails/Notifications -> Customizations - confirmed that "test 1" wasn't there Clicked "Program" tab - program now references "[Entry #]". In trying to fix it...I made a new customization (saved) and then updated the program (saved). Exited AC. Launched AC. Program showed "[Entry #]". But, then I clicked over to Customizations and then back to Programs and it referenced the new customization name. Ran "THEN" of program and notification came through just fine. What's also strange is that when the program references "[Entry #]" and I run "THEN" of the program I get the notification that I expect to get. The program showed incorrectly until I clicked on the Customization tab. Just changing from Program Details to Summary to Variables did not change the program. I had to click to Configuration and to the Customization tab to make the program read correctly. And yes...it also resets every time I load admin console, but will refresh just by clicking on the Customization tab. Very odd. So yeah...might be a UI bug. Best way to track bugs is through a support ticket (not through the forum). So I'd suggest opening a ticket. Explain your steps so that they can recreate your steps and hopefully reproduce the results.

@webminster Are you still having this issue? Not sure on this one. I just tested a few notifications and programs and the name didn't revert. Have you attempted to delete the "Entry 12" and create a new notification? For me, the program didn't change the reference until I saved the renamed notification so I'd say you did that part correct. Make sure you hit save on the programs tab! I did further testing and have this issue if I don't press save on the program tab. Even though you didn't directly change a program it might be an oddity that the system isn't pushing that program change to saved status so when it reloads it pulls up the last saved state for the program. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@Techman OP stated running ISY994 v5.3.4; those buttons aren't available on the ISY994. The process you reference is only available on IoP. Additionally, the OP is using PG2 and hasn't updated to PG3. Sadly, OP apparently didn't receive the email that was sent in early July or didn't read the forum post referenced in their original post warning that the SSH method was causing issues. @Michel Kohanim informed the OP to submit a ticket for assistance because there are certain steps that must be attempted if the SSH update method is attempted and corrupts libraries. So, the best way to resolve this, currently, is through opening a support ticket.

You’re logging into PGv2. I believe @Techman is looking at the PGv3 interface. Please just start a ticket as @Michel Kohanimsuggested to get taken care of.

Doubtful, but could be one or two out of the 6 pack. Some changed about 3 months ago from same batch are 80%+ with all setup the same and not in cold areas. 2 that are reporting 75% were changed about 2 weeks ago. And were ones that kept getting bad URL call emails about.

Anybody else check to see if this impacted battery life? I just changed batteries in a few tags and they're suddenly at 75%. Normally it's months before they read 75%. So I wonder if the issues were trying to connect to the tags non-stop and caused battery drain faster. Wished I could have gotten my wife to unplug the tag manager faster.

Make sure you delete any old messages that came through with numbers. The phone (or as @MrBill says AT&T) might be picking something up and applying that number to it. I'm on iOS and T-Mobile and it came through with alerts@ email for the from. Have you tried the @mms.att.net as @MrBill suggested?

@Prana electric I think @Michel Kohanim means remove the whole thread of texts on the phone. I just ran some tests using the default server on IoP and they were delivered to T-Mobile network almost instantly. They were received from alerts@universal email. So I'm not sure how you got some from multiple long numbers like that. Perhaps it was in the process of moving the server to SES, but try again. Delete all current alerts/tests first though.

Thanks @Michel Kohanim for the update. Testing the default with T-Mobile email to text worked almost instantly. Hope other carriers continue to support this. I know Google Voice stopped forwarding texts (sometime last year) to the actual cell phone because of some abuse issues. https://www.engadget.com/one-of-google-voices-best-features-is-going-away-092145507.html#:~:text=The Google Voice app now,ring all your other phones. https://9to5google.com/2021/03/09/google-voice-soon-no-longer-forward-messages-phone/ I always wonder when people start having relay issues from email to text if the carriers themselves start turning it off. I know it's low priority delivery as it is (for most carriers) so what's keeping them from turning it off completely? Text comes in from the alerts@universal email so that's great!

@JimboAutomates the Google group got a reply that it should be fixed. I haven’t gotten home yet to plug the tag manager back in to tell. Hope others are working now.