apostolakisl Posted August 14, 2018 Posted August 14, 2018 I don't know if anyone else has had this. But yesterday when I started to mess around with some new stuff, Google home wasn't synced. When I went to save my changes, I got an error that it failed authentication. I hadn't made any changes to anything, so I don't know why this would have happened. I also found that one of my google home commands was missing from list and none of the remaining ones worked until I resynced. Quote
apostolakisl Posted October 3, 2018 Author Posted October 3, 2018 This has happened again. Google home reported that it was not connected to ISY upon issuing it a command. I tried the "send spokens" to Google and it failed, I believe it said it failed authentication. I had to use the Google "home" app and remove ISY then add it back in. Again, I had not changed anything with my google account or my ISY/portal account. Quote
Michel Kohanim Posted October 3, 2018 Posted October 3, 2018 Hi @apostolakisl, Would you please send your UUID + link to this post to support@universal-devices.com? With kind regards, Michel Quote
bmercier Posted October 4, 2018 Posted October 4, 2018 This is an issue that happens once in a while. @apostolakisl, this will sound weird, but please try this. In your list of spokens, please add one or two devices, even if you don't use them. Please use devices that regularly changes state, once a day or more. It would be long to explain, but it seems the issue is that google loses track of the "agentUserId" which uniquely identifies the user sending. When requesting to send spokens, this makes a request using your agentUserId. In addition, when devices changes states, the same authentication mecanism is used. I think that making regular requests such as sending devices states helps. In your case, all you have are scenes and programs, which don't have states. Adding devices that sends states could help. In parallel I will also reopen an older ticked with Google. Thanks, Benoit Quote
apostolakisl Posted October 4, 2018 Author Posted October 4, 2018 15 hours ago, bmercier said: This is an issue that happens once in a while. @apostolakisl, this will sound weird, but please try this. In your list of spokens, please add one or two devices, even if you don't use them. Please use devices that regularly changes state, once a day or more. It would be long to explain, but it seems the issue is that google loses track of the "agentUserId" which uniquely identifies the user sending. When requesting to send spokens, this makes a request using your agentUserId. In addition, when devices changes states, the same authentication mecanism is used. I think that making regular requests such as sending devices states helps. In your case, all you have are scenes and programs, which don't have states. Adding devices that sends states could help. In parallel I will also reopen an older ticked with Google. Thanks, Benoit OK, I added a device that is used very often so it should be sending lots of updates to Google. Quote
apostolakisl Posted November 1, 2018 Author Posted November 1, 2018 On 10/3/2018 at 8:01 PM, bmercier said: This is an issue that happens once in a while. @apostolakisl, this will sound weird, but please try this. In your list of spokens, please add one or two devices, even if you don't use them. Please use devices that regularly changes state, once a day or more. It would be long to explain, but it seems the issue is that google loses track of the "agentUserId" which uniquely identifies the user sending. When requesting to send spokens, this makes a request using your agentUserId. In addition, when devices changes states, the same authentication mecanism is used. I think that making regular requests such as sending devices states helps. In your case, all you have are scenes and programs, which don't have states. Adding devices that sends states could help. In parallel I will also reopen an older ticked with Google. Thanks, Benoit So far so good since I did as you suggested. Quote
bmercier Posted November 1, 2018 Posted November 1, 2018 1 hour ago, apostolakisl said: So far so good since I did as you suggested. Excellent, thanks for the feedback! Benoit Quote
MWareman Posted November 1, 2018 Posted November 1, 2018 In my case, I had only added spoken to scenes. I regularly had to remove and reauthenticate because the connection got broken. I just started the process of switching to putting the spoken son the controlling device (so you can ask Google the current status) and implementing programs and scenes to keep the scene consistent when the device is controlled in this way. Hopefully, this change will stop my accounts from getting disassociated as well... time will tell... If this is indeed the issue, then there really should be a keepalive ping implemented in the Portal.... Quote
bmercier Posted November 2, 2018 Posted November 2, 2018 On 11/1/2018 at 10:02 AM, MWareman said: In my case, I had only added spoken to scenes. I regularly had to remove and reauthenticate because the connection got broken. I just started the process of switching to putting the spoken son the controlling device (so you can ask Google the current status) and implementing programs and scenes to keep the scene consistent when the device is controlled in this way. Hopefully, this change will stop my accounts from getting disassociated as well... time will tell... If this is indeed the issue, then there really should be a keepalive ping implemented in the Portal.... Yes, I think that would be a good idea. The "ping" would need to be a valid request. If there are no devices for which we can send a status, then, the only valid request we could send is a sync request. The same as when clicking the "Send spokens to Google Home". Benoit 1 Quote
SteveKlos Posted December 2, 2018 Posted December 2, 2018 I'm having a similar problem and I'm finally trying to track down what's going on. I regularly have to unlink and re-link the ISY Portal in Google Home. Unfortunately, Google's updated the app and the linking unlinking is more difficult to discover in the current version. I'm also kinda tired of having to setup the rooms in Google Home. I have spokens on all modules that are used regularly, so I don't think this necessarily helps resolve the problem. By spokens, I'm assuming you mean the words that are included in the my.isy.io portal... It appears that you're working on this (which is awesome) - is there anything we can do to provide additional information on what's happening? Quote
apostolakisl Posted February 6, 2019 Author Posted February 6, 2019 Well, after a long time of not going down, the link went down again. So perhaps putting devices into the google home that update often (multiple times per day) doesn't entirely fix this issue. Quote
Michel Kohanim Posted February 6, 2019 Posted February 6, 2019 @apostolakisl, Do you get Permission Denied errors? We have already opened a support ticket with Google. Something quite screwy is going on there. With kind regards, Michel Quote
apostolakisl Posted February 7, 2019 Author Posted February 7, 2019 22 hours ago, Michel Kohanim said: @apostolakisl, Do you get Permission Denied errors? We have already opened a support ticket with Google. Something quite screwy is going on there. With kind regards, Michel When I asked my google home to turn on a light, it responded with something to the affect of "universal devices is not available right now". It definitely did not say anything about permissions nor did it use the word error. Having experienced this before, I went directly to "google home" app on my phone, removed Universal Devices, then added it back in. This fixed the problem and I got no errors adding it back in. Quote
Michel Kohanim Posted February 7, 2019 Posted February 7, 2019 @apostolakisl, Thanks so very much for the update. We have submitted a ticket to Google. Haven't heard back. With kind regards, Michel Quote
asbril Posted February 7, 2019 Posted February 7, 2019 3 hours ago, apostolakisl said: When I asked my google home to turn on a light, it responded with something to the affect of "universal devices is not available right now". It definitely did not say anything about permissions nor did it use the word error. Having experienced this before, I went directly to "google home" app on my phone, removed Universal Devices, then added it back in. This fixed the problem and I got no errors adding it back in. I have not experienced this issue. Quote
Michel Kohanim Posted February 7, 2019 Posted February 7, 2019 @apostolakisl, Can you please send your UUID to support@universal-devices.com and include this link ? With kind regards, Michel Quote
sanders2222 Posted February 25, 2019 Posted February 25, 2019 For more recent information on this problem, see Could not update settings. Please check your connections. Quote
apostolakisl Posted April 21, 2019 Author Posted April 21, 2019 (edited) My google home is now saying things like the following: "ok, turning on the pond air pump on. . . sorry I couldn't reach universal devices" for some items, but for others, it just works. This is hard to explain since the same universal devices ISY controls both items. I tried this multiple times back and forth, the one device works every time, the other device gives the error message. EDIT: OK, so I actually checked the pond air pump, and it does turn it on and off even though it says it couldn't reach universal devices. Edited April 21, 2019 by apostolakisl Quote
bmercier Posted April 21, 2019 Posted April 21, 2019 My google home is now saying things like the following: "ok, turning on the pond air pump on. . . sorry I couldn't reach universal devices" for some items, but for others, it just works. This is hard to explain since the same universal devices ISY controls both items. I tried this multiple times back and forth, the one device works every time, the other device gives the error message. EDIT: OK, so I actually checked the pond air pump, and it does turn it on and off even though it says it couldn't reach universal devices. I would suggest to unlink and reliable. You may have devices that existed in ISY Portal that are no longer there, or were recreated, which would assign them a different ID.Sent from my iPhone using Tapatalk Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.