Geddy

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.