MrBill

August 11th They had a Full Disk on their Windows Server.

Have you tried "Reboot Tag manager", I can't find it in the mobile app, however at https://my.wirelesstag.net/eth/ there is a button at the bottom of the page, one of it's items is Wireless tag had an Issue back on August 11th where a hard drive on a windows server filled up. I had to reboot the tag manager to get two of mine to reconnect.

I fixed to for ya... that is a slimy ad. I took a close look after you posted... extremely misleading. Happy you asked.

The closest easy method, is to view all, by clicking "ISY" (or whatever your root level is called) and then clicking the "address" column header in the right window to sort the table by address, then scroll down.

Actually I've had a problem with naming too, especially "living room". If I use "living room" in almost anything it doesn't work, but instead of what you are seeing I get "sorry, living room doesn't support that" I have no idea what she thinks "living room" supports, I've been through device names dozens of times trying to figure it out... as a result we use a lot of what I'd call silly names for Alexa spokens in that room, like Turn on Alan Shore for the fireplace... Turn on Denny Crane for the ceiling fans... That said both my wife and I hate speaking to Alexa and neither of us use Alexa all too often for home control. We tried to like using her, but she talks back too much and too many things have to be repeated. We do use Alexa a lot in other respects... playing music "everywhere" and kitchen timers are the top 2 usages.

Those are exactly the scene control buttons I meant. If Alexa still isn't controlling the original scene correctly, I would delete that from the portal, make sure the scene is gone via the Alexa app, then add it back..... that said, it looks exactly correct from your screenshot a few messages up and it doesn't make sense why deleting and adding back the original voice control would make it better, since the ISY is the scene controller in either case.

@KentinadaThe troubling thing about your problem is that Alexa and mobilinc are both using the ISY as the scene controller. As someone else above asked what happens when you use the ISY scene control buttons? The next steps for this problem are to open the event viewer and set it to level 3, then control each device and analyze the log. You can post those here for comment too. I'm not very good at event viewer logs and will let others answer at that point. There's a steep learning curve for the system integrator but so far my wife's favorite "non-light switch" controller has been Home Assistant with the app on her phone, she prefers that over Alexa. The UDI ISY-994 HA integration works perfectly. The learning curve comes from designing dashboards, it's actually pretty easy anymore to create simple dashboards. Mine are probably a notch up at the intermediate level.

The node count includes Insteon Devices, Z-wave nodes, Scenes, Node Server Nodes, and Folders. My guess would be that you weren't counting something. If you're on Version 5 and have polyglot there is a nodeserver named ISY Inventory that does the counting for you.

@Kentinada Your scene's are in fact configured correctly. (sorry for pushing the point, but 98% of the time posters don't understand the concept that scenes can be programed based on the controller used.) The next step that I would try, is right clicking each device that is included in the scene and select "Restore Device" (I would do these one at a time, i.e. not queuing them up with the "disable automatic writes" button.) This will resend the links stored in each device to the device. If the problem persists after that you likely have a standard Insteon noise/signal sucker issue.

I you haven't already done the above you might just try right clicking devices and selecting restore device. If you need to go to the extreme of removing devices from the ISY, I would suggest factory resets before readding them. Factory reset procedure can vary slightly by model.. a 2477. is pull out the air gap switch and wait 10 second... Push back in all the way and Hold... keep holding until the long beep STOPS.

I dislike Caseta switches immensely they are way too busy with all the marks and buttons. RR2 the simple and elegant look that high end customers would be looking for.

Sounds like the two controllers are programmed differently. Take 2 screen shots, one with the Root Level "RL Lighting" highlighted showing the right hand window, then take highlights or click on "RL UP - 2" and showing the right hand window, and post both.

There are actually two controllers in that scene. The root level that's highlighted "LR Lighting" is the controller settings that are used when the ISY itself is the controller. "RL UP - 2" is also controller because its name is Red. The scene can be programmed to behave differently based on which controller was used. Also NOTE, this isn't the problem in this case, but that little gray 1011 icon means there are things in queue that need to be written out to the device. The fact that it's gray means that you also have wireless writes disabled which is fine for short term while getting things ready, but you really shouldn't leave unwritten instructions hanging around, they will come back to bite.... To resolve put the device in linking mode, and release the wireless write hold by clicking that icon.

To add to what @lilyoyo1 mentioned. click the scene name in the tree, are the devices configured correctly there? each scene must be configured at the root level, and each red controller link.

I assume you saw the 5 on eBay https://www.ebay.com/itm/144056662776

That's also true! In this case tho, the OP upgraded to V5.3.0 but was still using V4.6.2 admin console... those two don't mix at all....

the easy way to buy the caps is the Ebay deal. I bought 2 sets just to have on hand. Looks like the sellers out of town until the 26th tho, and it does ship from Canada which adds a day or 2 if your in the states... Arrived quickly tho. Edit to add: note there is two kits a 5 cap and a 7 cap... the slector box chooses.

The important issue is that the Firmware version number and the UI version number must always be exactly equal. When the firmware is upgraded, you must make certain to get the new admin console. After clearing the java cache, the link https://isy.universal-devices.com/start.jnlp should get the correct version of the UI automatically. What won't work is clicking an admin console that you already have saved.

A great thread about z-wave to go read is this one from @lilyoyo1

I just discovered this treasure trove of old Developer Docs. Thought you'd like to have the link,,, it's buried in a folder in the PyInsteon project on github.

In the Admin console, Tools > Generate Topology will produce a list of devices then scenes it's not the greatest but it's workable.... TIP: After the HTML file opens in a browser click in the window and Ctrl-A (select all) then Ctrl-C copy, Then open a blank Excel worksheet and click in A1 and right click, paste special, match destination formatting. Once it's in Excel you can clean it up and make it more useful.

Are you aware that the ISY must be rebooted to find a PLM... It only looks for a new connection on startup.

Another option that's in Alpha testing at the moment is "ISY on Polisy" which can use the USB PLM, however we don't know how far in the future this will be ready for production usage. We also don't know when smarthome will be restocked on serial PLM's.. it will be interesting to see how fast they sell out when they are restocked.

@Mikes The largest difference is being able to use node servers to add more node types to power your automation. Nodeservers run locally on a pi running Polyglot, or a Polisy from UDI. (the pi running polyglot may be phased out in the future) The local nodeserver store can be viewed here: https://polyglot.universal-devices.com/ There are also cloud nodeserver that can be run if you have an ISY portal subscription. The cloud nodesever store is a more limited list https://polyglot.isy.io/store Some nodeservers are better suited for local, and some better suited for cloud, while a limited number are available both ways. Beyond that upgrading from 4 to 5 goes fairly smoothly nowadays however if you have ISY programs that use the feature "Adjust Scene" all of those programs will need to be manually repaired. If your interested in using nodeservers then you'll want to update... if not the path of least resistance is stay at version 4.9.

Unless as I believe what Brian is suggesting is that one may become a signal sucker.