bmercier

Hi, First of all, I would not call it a "database failure". The database itself was never corrupted or had loss of any data, which a "database failure" would imply. I'm not sure of all that you did, but all that was needed is to relink. To answer your question, no there is no upload function. The download of the spoken exists to keep a reference, or to create documentation on the spokens. It is not meant to be a backup process. I'm not sure if you deleted them or not, but you should not. Now regarding your program spoken - Are you saying that when you edit existing spokens that are programs, the Spoken and Alternate Spokens fields are empty? I'm not sure why that would be. I looked up your account, and edited the same one as in your screenshot "Siren-1second (0065)", and I do see the spokens. I see it for all of your programs. I'm thinking that you might have a browser extension that fills these fields, actually clearing them with an empty string.

@BEdgar Whenever you need support, please open a ticket. We don't actively monitor the forum. There were other threads related to Google Home not working, and as far as I can tell, everyone has their Alexa or Google Home working. The Google Home issue is not related to any changes in the eisy/polisy or Portal. The problem has been explained here: So back to your Google Home problen, after linking, even though it does not show as Linked, it probably is Linked. Can you check if you can see the status of devices and control them? Could you create one more spoken and click "Send To Google"? I had that problem, but creating a spoken and sending it to Google made it appear as Linked. One more thing to try, I would suggest to Delete your Home and create a new one. Go to Settings | Delete this Home There is something wrong in your Google account, something needs to be reset. By experimenting, the "Send to Google" should be able to fix it.

Yes I've seen that. But my question is - Were you able to reproduce the problem?

@Panda88 Were you able to reproduce the problem?

@johnstonf Even though it does not show as Linked, it probably is. Can you check if you can see the status of devices and control them? Could you create one more spoken and click "Send To Google"? One more thing to try, I would suggest to Delete your Home and create a new one. Go to Settings | Delete this Home Something needs to be cleared in your account.

Then I have no clue why Google would not show it as Linked. That's not something we can control.

Why would you say that? As I explained, this was cause. Google could not refresh the access token during the outage. The refresh token Google has is no longer valid, so you have to re-link. Nothing else changed.

@johnstonf, I'm sorry that you are still experiencing issues with the Google smart home integration. I don't know why it would not show as Linked after Linking. That would be a question to ask Google support. This kind of trouble can happen when using multiple Google accounts, so perhaps it used to be linked with a different google user id than what you are using now? That's the only thing that comes to mind. If that can help, there has been no changes to the Google integration in a long time. The only thing that the outage caused is that Google could not refresh the access tokens if it happened to be due for refresh during that period. If the google smart home integration does not show as Linked after linking, there is not much we can do to fix it.

So here's what happened. There were 2 bugs in the code of the proxy servers that were dormant. They had no effects, unless a proxy server had a hard stop... which happened last night. The first bug had the effect that some units were trying to connect to a no longer existing proxy server. The second bug is more complicated to explain, but it was also caused by the hard stop. This one was causing the HTTP 500. The hard stop was caused by AWS stopping one of our proxy instance unexpectedly. This was NOT a graceful shutdown. This is usually caused by the failure of the underlying hardware. Both bugs have been fixed and are in production.

This should be fixed for everyone now. Currently doing additional checks. Will post a summary later.

Should be working now

@Sir @hum099,Can you please try a reboot?

Currently investigating. Some units are having trouble with Portal.

I would like to add some context to the disk space as I have seen comments questioning the low disk space. I agree 5% is low and it was due to be increased very soon. But keep in mind, this is not a file server or a windows workstation where a single video added can add GB's to the storage space. In these cases, even 20% free disk space would be low. In the case of this server, the storage space grows very slowly, like not even 1% in a year, and does not need much temporary space either. It grows slowly, linearly with new users registering for an account. We are talking just a few KB's at the most, not even 1KB if you don't add spokens and such. For those more technical, the database on this server is MongoDB. We learned the hard way that MongoDB will refuse write operations if the free disk space is smaller than the database itself (or perhaps the size of the collections - I read conflicting information on the subject). That was completely unexpected. But regardless, it won't happen again.

Did "Universal Devices" end up being listed as Linked in the Home app?

Thanks for the video. This is not normal. Looks like account linking is successful, but it won't show it as linked after linking. I suspect something needs to be reset in your Google account. Not sure if you use multiple Google account, but one possibility I'm thinking of is it might have been linked previously using a different google account on this same device.

Details on the outage here:

There has been an unplanned portal outage on 2025-01-01 from about 4:30 UTC to about 13:35 UTC. Starting at about 13:35 UTC, my.isy.io started responding, and ISY/Polisy/eisy could start reconnecting. At 13:50 UTC, the vast majority of the units had reconnected and portal was fully functionnal. Root cause The root cause was a lack of disk space for the database server. There was actually disk space left (5%) which should have been sufficient, but the database server stopped responding to requests as the space left was below a certain threshold. Our monitoring did not alert us as 5% left was considered sufficient as the disk space grows very slowly. The solution was to allocate more disk space. Impacts Due to the length of the outage, services using oAuth like Alexa and Google Home may have become unlinked. To fix this, they just have to be relinked. Alexa relinking: Open the Alexa app, Click the 3 bars at the bottom, then Skills & Games Search for "isy" and choose "ISY Optimized for Smart Home V3" Click "Disable Skill" (If instead you see "Enable to use", then skip to step 5 Click "Enable to use", and when prompted enter your portal user and password Google home relinking: Open the Google Home app Click on Settings Click on Works with Google If you see "Universal Devices" under Linked Click on Universal devices, then "Unlink account" Find "Universal Devices", click on it. Tip: type "Universal" in the search box at the top When prompted enter your portal user and password.

Portal was down for a few hours. Please try again, it should be working now.

Problem has been resolved. It may take a few minutes for all units to reconnect to portal.

This means that your eisy is indeed not connected to portal. For your undertanding, the connectivity from eisy to portal is initiated by eisy. If everything else works on eisy, then it could be a bad internet switch or port, patch cord, or perhaps the router not allowing internet access to eisy.

Contact & motion sensor events are debounced. There can't be more than 1 event within a 30 seconds period. So this is likely the reason if you are testing 2 doorbell rings within 30 seconds. This is implemented within our Alexa skill.

I would suggest to try a different browser, or perhaps try incognito mode (If using Chrome). I believe a browser extension is probably interfering somehow. You could also try to press F12 and look at the browser console, then navigate to my.isy.io. You may see in the console an error message that could give you a clue.

There's nothing to do with the file. This was just a way to test that there's no networking issue preventing access to the certificate. If that was the case, that could have been a reason for the error message you are getting. At this point, I'm not sure why you are getting this error.

In addition, I would try this; Check if this link works from your computer (The same device you are using for https://tesla.com/_ak/my.isy.io): https://my.isy.io/.well-known/appspecific/com.tesla.3p.public-key.pem This is supposed to download a public key. One of the potential causes for the error you are having is that it can't download this public key.