Geddy

With ZMatter you get Z-Wave, Zigbee, and Matter (eventually more beneficial than currently...hopefully). More information from the UD Wiki: https://wiki.universal-devices.com/Eisy:User_Guide#Z-Wave_Support Reliability of what? The ZMatter dongle from UD only supports the above technology. It does not change how Insteon is supported. So I'm not sure what reliability you're asking about. Yes, to the technology mentioned above. Further to this the eisy itself with Polyglot Plugins opens you up to many more devices/ecosystems to integrate with the existing IoX and any ZMatter devices you might add if you get that dongle. You'd be better suited to look at the Polyglot store (https://polyglot.universal-devices.com/) to see what options you have for different products that can be added to the eisy. These are not dependent on the ZMatter dongle. I haven't kept up (lately) with those posting about this issue with the PowerWall, but seems like it was system based issues. Would Z-Wave be better? It's personal preference call. I've not seen any comments about it working or not working with a PowerWall system, but that's most likely that people either aren't having issues so don't post when they aren't having problems or just isn't something people have attempted and been a UD customer to come here to report one way or the other. You'd be better served by talking with the sales/installers of such systems as to what home automation systems they have had success running behind the battery/power source. They might know that something would impact Insteon systems or other technologies better than a user base here just basing on their own use or readings from other posts here (again, remember issues seen here are usually just from people having issues...people that don't have issues usually won't come just to say "this things works great"). Personally, I have over 50 Insteon devices working well in my system. I tried a few z-wave devices and found them lacking in reliability. Bulbs and/or switches were slow to respond to programs and verbal commands whereas my Insteon devices just worked. I wouldn't change based on my experience with them, but again I've got a lot invested in the Insteon setup and wouldn't want to blindly spend the money to change to Z-wave and not have the same operation that I have currently.

When you're using IoX Launcher (java based admin console) are you selecting "LAN" or "Cloud"? In the past if you selected "LAN" you would need to clear the cache since the version you had previously downloaded was an older UI. IoX launcher attempted to get away from having to do this, but was only more reliable when selecting the "Cloud" option. It would usually error out before getting to the login page. If you're selecting "Cloud" option then that's (quickly) downloading the proper UI for the firmware installed and does not result in an error. Prior to 6.x it did not mean you had to use your portal credentials as it was still a local connection...it just meant it "grabbed" the UI version from the cloud before you saw the login prompt. IoX Launcher was developed during the 5.x beta version period where updates were being released rapidly and many users would forget (or complain) about clearing cache after each (little) update. UD tried to make it easier for us users at the time and it's just been the best tool since it was released (and of course the browsers ending the old java connection method). Next time you log in check the Help -> About to see if the Firmware and UI match. If they do then you're all good. If they don't you might be better off clearing the cache (selecting all 3 boxes) and getting a new start.jnlp file from the UD site (top right "My ISY") and running that to put the launcher shortcut back on the desktop (for Windows PCs). It's just always been the standard operating procedure to assure you don't have issues. Mismatched versions have been problematic for scenes and programs (and possibly other issues). It might be best to keep things in check while UD fleshes out the rest of the web based process.

My understanding of Alexa+ is that it's only going to work on new(er) devices. Perhaps they're trying to figure out how it's going to impact those of us that have 1st/2nd gen stuff (or just stuff older than they want to support with Alexa+). I have two devices that would work with Alexa+, but I am avoiding it since I don't really like/trust Alexa enough to begin with. I don't want her to keep listening for follow up inputs when all I really need are timers and to turn things on/off randomly. It's this overreaching (over listening) aspect that Amazon is trying to make Alexa smarter by forcing users to use the follow-up that many probably turned off because it wasn't very useful when they first introduced it. I might be in the minority of wanting/using the new Alexa+. It's clear (to me) if Amazon is implementing Alexa+ while not working with their partners/developers for all the skills essentially breaking the skills (that people have developed over the years) is not very good for any parties involved (Amazon/Developer/User). If what @bmercier says is true that the V3 skill will work with Alexa+, but results users are having mixed results then I blame Amazon for breaking things. Sadly, many will come here (as they apparently have) and blame UD for not working with Alexa. Let's be sure to point the finger the right direction. Amazon is making a new offering while apparently not "breaking"/changing their API that developers use to make Skills. When the skill doesn't work why is it the developer's fault? The developer is only working off what Amazon is telling them that the skill would/"should" work. Sadly, it's a never ending cycle these days. Things are trying to become smarter while not supporting things that just work now. Toss into it any little break in network/internet connection really blows stuff up quickly. Remember when we had to physically flip a switch to make a light come on? That never broke...why did anybody think it needed to be "fixed"?

probably a macOS issue. I'm on windows 10 and 11 laptops and can stay logged in without issue. I don't usually have it open more than a few minutes though (typically just enough to help others here if I need to test something out). I know Apple likes to block Java and control background running "apps" more so they can have better battery life. Good luck tracking that down.

@GSutherland you could open a support ticket directly with UD to request a refund. They should be able to locate prior purchase and recent purchase. Might be good if you had an idea of the original date you purchased to include that in the message to support. https://www.universal-devices.com/my-tickets

For the issue of not being able to restore from a backup I would suggest you open a support ticket with UD to get help on the situation. There might be something that went wrong in an update that is not allowing the restore to properly complete. https://www.universal-devices.com/my-tickets What computer OS are you using? And what UI are you talking about? If on Windows and Admin Console you should be able to remain logged in quite a while. As far as I know there are no timeouts that UD implemented. Many say they leave their admin console up for hours/days without issue. Of course the admin console is not designed to be up 24/7, but some attempt this (I have no idea why). How quickly is your session timing out? It could be system or network related. Be sure you are not running any VPN or Anti-virus services. Also make sure you're on a stable network connection. When you have a support ticket about restoring the backup as them if there's a way to see why you are timing out of admin console if that's the UI you're speaking of.

@ctviggen1 If times still show incorrect please reboot your device and it should clear up.

You can follow the information in the wiki: https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3 You'll want to disable/unlink the V2 skill first. Not a requirement, but might actually remove it from the Echo/Alexa "my skills" and not give you a warning about it not working soon.

Others would need to chime in on this to confirm, but I seem to remember for my doorbell (Doorbell Pro) the motion was always empty. I don't run motion programs so not sure what would trigger it. Maybe @bmercier can chime in to see if there should be something inside the doorbell motion node. Looking at the information on the plugin (in the "More Info") there are no drivers under the doorbellMotion. I'm no programmer, but I would think there would only be items in the node if there were defined drivers. There's no drivers in my camera "Lights" node (and that node is empty on admin console), but there are drivers in that motion node. It matches what I see in the .py file(s).

This is normal. It's always been blank. My motion for doorbell is blank. My floodlight cam does have a status and battery life (even though it's a hardwired device). For the doorbell the status and battery life (again, I have a hardwired device) are in the main device node. You should be all good. I don't use motion for programs, but be sure you test your programs to be sure they work. I recall there being an issue maybe a year (more or less) ago that many went into a state where they were not active. I'm not sure what causes that, but don't think it's anything user related. At least didn't seem to be last time it happened. Glad you checked that too. I didn't get that far into looking at it since mine worked following the authentication and restart process. Sorry...should have said I split it out into a new thread. All good there.

@oberkc you replied to an old topic so I split out to new thread in case this is a new issues. However, you made me look into what version I was running and still 1.2.6. It did say I needed to re-authenticate the system. I did that and things seem to be working okay for me. I see motion nodes and if I "test" the ring node it is a success. I had to restart the plugin to get my associated programs to work properly.

@MBrzeski you need to add custom variables in the configuration screen. From the More Info section: "Add a custom variable named host containing the client_id and client_secret. Those value need to be requested from Flair Support." Click on "Add Custom Parameter" and then the "Key" should be "client_id" and add another to be "client_secret". Then hit save changes and restart the plugin. Be sure you are not logged into Admin Console at the same time as installing/updating plugins. When admin console relaunches it will read/load any changes you made in the plugins.

@francoislegacy Glad it worked on another...that's strange it doesn't for these plugins. Just for "fun" is it possible to reinstall the plugin into those slots? Is there an option in the plugin to try to install into 8 or 9? Maybe try to install a different (free/trial) plugin into these slots. It's been a while since many reported "unmanaged" and it usually happened when going from PG2 to PG3 or even migrating from Polisy to eisy. Have you tried a forced refresh (Ctrl + Shift + R [Chrome on Windows]) on the web page? I expect that support would be able to look into this better and get you the best method to remove them from the slots. They aren't hurting anything being there (I guess), but would be good to get them cleaned up so they can be used for other plugins.

@francoislegacy sorry that didn't work. It had in the past. I would open a support ticket with UD. This is probably simple with the right steps. https://www.universal-devices.com/my-tickets If it's a simple process please post here to help us help others if/when this occurs again. Please also let us know what firmware you are currently using.

@francoislegacy since they show "unmanaged" in the PG3 dashboard there's no way to do it there. Logout of PG3 Open Admin Console look at the menu for plugins Configure Find the ones in slots 8 and 9 Should get a "Plugin Configuration" window Delete (button along the bottom) Then close admin console log into PG3 dashboard They should be removed. That's been the way I've seen described in the past. Haven't ever actually done that, but seemed to work. Remember...only be logged into one thing at a time. Log out of PG3 on the web (don't just close the tab/browser window). Actually press "Logout"

@apostolakisl I might open a support ticket for this just as an issue that seems to have been around a little while. I recall this being mentioned... https://forum.universal-devices.com/topic/45675-unexpected-application-error-expandcollapse/ I know you and @bmercier had discussed this previously about having a expand/collapse button on the UI, but this sounds like a refresh issue. Have you tried on a different browser and have the same result?

Only one device needed new batteries in a year. Others are still going strong almost 2 years later (and seem to be good for a while more even). Glad your wireless tags are permanently powered…only some of mine were and they still will drop from the hub so I have to unplug occasionally (again…they aren’t super far from the hub…why do they drop?). The battery wireless tags seem to die every 3 months and I’ve trIed various brands of batteries….enough to where I just toss the tag away when the battery dies now since I refuse to change those batteries. Hopefully wireless tags get support again soon, but the product is not reliable (IMO) to be willing to continue to try to use in my situation. I’m sure everybody has different experience. Just sharing mine.

Not user definable like wireless tags are. That's one point where YoLink is behind, but like @Ross points out I've had much better reliability with YoLink than I did with wireless tag sensors (and I've used battery and usb powered sensors). To me the range and stability is much better with YoLink. I still have some wireless sensors running, but the errors I get with the hub and links to the sensors (within a mid size house) were too much for me. The YoLink updates on its own schedule, but seems to be if/when the temperature fluctuates within a few degrees. I don't really keep up with it (certainly not every 30 seconds). Mine is mostly if the fridge/freezer crash. I have a few in rooms just to keep up with how much the room temp changes during the day, but rarely look at them. Having a display on the device is nice if I walk by one I can just glance at it's current temp. The product offerings from YoLink are what won me over. Yes, it graphs well. It will do current day or historical. And you can zoom in/out as you wish. You can move along the line to see the time of the temp change. I started with the hub + 2 temp/humidity sensors from Amazon since it would deliver quick and allowed free returns if it didn't work like I wanted. Then added more sensors after I was pleased. Now I've got ~10 temp, 4 water, and 2 vibration. Also, battery life has been great! My fridge batteries got low at just about 1 year so I replaced them. The freezer batteries lasted ~19 months. The room sensors are still on original batteries at 22 months and show "medium high" in IoX through the plugin. So I expect they'll last another year at least.

@andrew77 Have you happened to have updated to Alexa+? If so, tell it to revert. Alexa+ is causing issues with home automation systems (there have been other posts here about it). Try deleting the "basement" (50515) scene from the UD Portal portal. It should remove it from the Alexa app, but might need to delete it in there too. Since it's a "scene" I'm not sure how it shows up on the app these days. Old posts suggested scenes aren't displayed in the Alexa app and since they got rid of the website access it's a little more difficult to clean up devices. More than likely Amazon has updated Alexa just enough that when you have one device that is "basement" and another that is "basement forty percent" it could be considering if you set the "basement" to 40% that's the same device as the "basement forty percent". Does it work with other percent requests? Or is it ONLY the 40% trigger? Do you have multiple devices in this scene or is this just controlling a single device to a set % of brightness? If it's just a single device then I wouldn't have scenes for set brightness and just tell Alexa to set it to that percent. I have a few dimmers exposed to Alexa and just say, "Alexa, set x-lamp/light to y%".

@haroldunger I ran Insteon leak sensors years ago and remember these two threads helping...they might be way overkill, but worth reviewing in your situation. I've since changed to YoLink leak sensors and they work great with the eisy+yolink plugin and (really just the YoLink app) for alerts. But I use YoLink for several other things so already had a hub and the plugin. Check these out: https://forum.universal-devices.com/topic/15170-leak-sensors-another-suggested-complete-program-package/ https://forum.universal-devices.com/topic/11566-leak-sensors-a-suggested-complete-program-package/

If the system isn't receiving a single tap then it's possible the switch is defective. I think there have been other reports of switches failing this way. I think @apostolakisl might have been one in the past to comment that they've had devices fail this way. I think it was around dimmer types. I recall there had been some discussion when Polisy and eisy were released about them being quicker than the ISY994 and not catching a double tap, but ended up that the device itself might have failed. Since you can control the switch from admin console and if the switch does power the load it's connected to then I think it's the internal components that don't push the Insteon signal out to the PLM.

As long as I can remember. It is kind of an oddball option (IMO) since automation is ongoing; when you uncheck it the program looks for a specific date. It is checked by default on new programs (like "All"). If you uncheck "daily" it looks for a specific day for the program to evaluate on. Leaving it checked allows it to run "daily". If you uncheck "All" then you can check the specific days of the week (if you had a M/W/F schedule you would just select those days, but still leave "daily" checked so it ran every M/W/F. If you keep the number of devices low (like you have) then more than likely you won't have an issue. But it really causes problems (at least has in the past) when you have a program that triggers devices directly in rapid succession. Simply adding a "wait" can help eliminate possible Insteon traffic issues, but also adds another problem that if the program evaluates during a wait and becomes false (or the opposite of your "IF" condition) then the process might stop midway through the cycle. This is where scenes come in handy that turning on 1 scene (with many devices) will just turn on when the program triggers it. And scenes can have retries if a device doesn't come on (or react) it might retry to make sure it triggers. It's a personal preference at this point. If you adjust your program and it triggers okay with the few things you're turning on then I wouldn't make wholesale changes to make scenes out of everything. Just if you run into issues of only 2-3 of the 4 devices turning on or off then you've got to consider the scene as an option. I'm like you in that I have not designed scenes in my system (aside from some keypad scenes). I usually only trigger 2 or 3 devices with a program and mostly in the off direction so it's not an issue for "popcorn" if something doesn't turn off exactly at the same time. Just a personal preference (again).

@slimypizza is correct - This program is wrong. You have "on" but nothing after it. You've unclicked the "daily" button and it's trying to do it for a specific date, but you've apparently removed the date. Like how you have it: What you would expect to see: The biggest thing about getting program help is understanding that when you share programs as screen shots it makes it a lot more difficult and time consuming for somebody to help. Sharing as text allows people to edit what you should see in a program. When @paulbates asked for it to be shared as text you only shared one of the two programs. Why not share both? They're equally important. Lastly, beyond just enabled and disabled programs you need to also make sure that the folder they're in does not have folder conditions that make the folder false (i.e. not allowing any underlying program to run). One more thing...when you get to this many devices you might want to put a short wait between them so the Insteon traffic doesn't go bouncing into itself all at once. This is why it's suggested to make a scene. As a scene it will all happen at the same time (or near enough...I doubt the dogs care about the popcorn effect).

They shouldn't cause issues being missing as long as the programs continue to work and there are no errors causing the system to loop. The underlying question is how strong is your z-wave network? If you've gone okay since you took the holiday decore down (assuming ~10 months ago) then it's fine. Otherwise, these modules do help keep your z-wave network in a good mesh setup by being available to relay signals to other devices. The z-wave network will heal if/when these are missing. If these are outlet/plugs is there an out of the way area they could be "installed" to meet the WAF test? Understood, but unless you've got hundreds of programs what is the risk of splitting them into a new program? Just copy existing and remove the items that aren't being used all year from one and the all year from the other program. If worried about impact they cause then splitting the program is super simple and probably more favorable to passing the WAF test than the alternative.

@srjacob FYI - removed the .zip file you added and just put the image and log file. Usually better not to use .zip files unless they're huge. Not many will download .zip files for risk of threats inside them. Images are fine to upload as an image and .log files are fine to upload. Typically the exclamation points means IoX is not able to communicate with the device. Close admin console and make sure the plugin is setup correctly. Check in the plugin (web access) that the nodes are found and correct. Maybe restart the plugin. Then re-open admin console and see if the problem is corrected. Remember if you have admin console open and you change something in the plugin you must always restart the admin console for most changes to be read. That's why it's often suggested not to have both open at the same time. Lastly, please include what device and firmware (actual version number) you're using. It might also help to include the plugin version number. Be sure to give actual numbers and not just say "current firmware/plugin" as that's not helpful months down the road if somebody finds this post and thinks they have a similar issue, but firmware or plugin versions might have changed.