I didn’t change anything I just rebooted. I also rebooted several times over the last few days with no issues. So I don’t know what happened.
NabuCasa support has been unable to help me.
Unfortunately I am on an older version 2023.3.5 but so much would break if I upgrade that I just have not had the time to bit the bullet and do the upgrade.
Since I just rebooted yesterday I think it should still be able to work today but I don’t know what to do to fix it.
I have tried the following
rebooted machine
restarted the docker instance
restarted HA in the UI
deleted the .cloud folder (backed it up) and restarted
But the errors persist. Does anyone have any suggestions on how to get this working again?
Thanks, I didn’t find the trouble shooting tips myself so that’s helpful. I already have a ticket open but the support folks have been unable to help so far and once they heard I have version 2023.3.5 they of course suggest that might be the issue. I don’t agree since it was working yesterday but I understand their point of view.
Hopefully I can find something in the trouble shooting, thanks for the links.
Such an old copy of HA would suggest perhaps the Nabu Casa modules might be out of date? Seems like they are hitting an API endpoint that might not exist anymore?
I’m guessing but they are probably going to suggest you update as a matter of course
I know, keeping up with the breaking features however scares me and up until now everything was still working.
Since I am using docker is it safe to just update to the latest version and if too much breaks go back to the instance I was running? I think it should work if I backup the ha directory entirely right? I just don’t have time to debug a lot of breaking features. And trying to read through 3 years of release notes is a chore, haha.
There are often database changes between versions, so an upgrade will also update the db. You should do a backup of the docker data folder for your HA instance, then do the update. Then yes, if it fails (or is really horrible with breaking changes you don’t want to deal with) you can restore the old data folder and download an older version of the Docker image and be right back where you were.
‘404 not found’ means the same thing in your browser as well as Nabu Casa - it just ain’t there!
You have to bite the bullet and keep up to date. Its the same as running Windows 3.1 in 2026, you can, but you probably shouldn’t.
Something has got out of sync. Maybe you can revert it, maybe not. If the required interdependency is external, you are sunk. Look forward, not backwards.
Closer reading of the error logs may prove fruitful. You are venturing into territory where your depth of knowledge required is probably going to be far greater than biting the bullet, upgrading, and remedying any possible challenging scenarios that arise.
You cannot postpone the inevitable forever. Fear of the unknown can be debilitating. Expecting technical support for outdated software is a big ask (probably selfish), especially in the fast moving HomeAssistant environment where bug fixes are frequent and common.
Make extensive backups (that are verified) and take the plunge and update. You may be pleasantly surprised!
I have been traveling this week and for the last couple of days I have not been able to access my Home Assistant severs via Nabu Casa. A couple of times it worked briefly but then I would try again a few minutes later and again could not access the servers. At first I was concerned that it was my network but these servers are in two different locations and have nothing in common.
During the first part of the trip I had no issues and I have not applied any updates. The servers are working fine, automations are running and Alexa commands (again via Nabu Casa) work. I just can’t connect lremotely. I’ll be home soon and will take a closer look but this feels like a problem at Nabu Casa.
There was a service interruption February 2nd. No logged interruptions since then, except for a partial outage of apprx. 4 and 2 hours on February 10th and 12th, respectively.
Ironically, I’d venture this process would have taken far longer than the outage did.
It would have been an incredible run of bad luck if each and every time an attempt to fix was made and the servers just happened to be down again. I would even guess that some of the missed updates may have been for resilience and improved troubleshooting as well.
I agree that I need to upgrade. I have wanted to do so for over a year but when I start trying to go through the release notes for breaking changes I see so many that might affect me that I postponed too long.
I am considering upgrading to newer but not latest version. Maybe 2024.1.x or a little later so there are fewer breaking features but maybe I pickup newer nabucasa code.
I agree asking support to help with 2023 version is selfish but they seem willing to try. I will likely start the upgrade process tonight.
I am using docker and I have the full configuration in git so I should be able to take the plunge and revert if entirely necessary.
Losing remote access does make me want to upgrade but what I really don’t want to lose is Alexa voice control, I use it too much and it’s just muscle memory now, if that starts failing then I will be constantly asking Alexa to do things and having it say it can’t connect. It will dive me nuts, haha
It’s interesting that Nabu Casa’s Alexa integration is still working, it’s just remote access that can’t seem to reconnect.
I don’t think that’s the case, all of my attempts where today and while doing so I was monitoring the status page for NabuCasa and they had no reported issues.
I agree that I need to upgrade. I have wanted to do so for over a year but when I start trying to go through the release notes for breaking changes I see so many that might affect me that I postponed too long.
I am considering upgrading to newer but not latest version. Maybe 2024.1.x or a little later so there are fewer breaking features but maybe I pickup newer nubacasa code.
I agree asking support to help with 2023 version is selfish but they seem willing to try. I will likely start the upgrade process tonight.
I am using docker and I have the full configuration in git so I should be able to take the plunge and revert if entirely necessary.
Losing remote access does make me want to upgrade but what I really don’t want to lose is Alexa voice control, I use it too much and it’s just muscle memory now, if that starts failing then I will be constantly asking Alexa to do things and having it say it can’t connect. It will dive me nuts, haha
It’s interesting that Nabu Casa’s Alexa integration is still working, it’s just remote access that can’t seem to reconnect.
Are you sure it isn’t something else like your router, DNS, VPN, or static IP Addressing that is obstructing access? Any other add-ons in your network that may have changed? The device you are attempting access from?
Have you brought everything down and restarted it in correct sequence?
I’ve been working remotely through Nuba Csas since early this morning. I’m in Lima, Peru. The serve is in Stratford Ontario. I’ve not encountered a single issue all day.
Yea that was a good comment. I keep all of my computers, phones, 3d printer, my Tesla etc up to date. For some reason I just let HA fall behind because it just works and I don’t really think about it. I thought I was maybe 1 year behind I can’t beleive it’s 3 years behind, haha
I just read through all the release notes and I don’t see any major breaking changes I am too worried about. So I plan to upgrade to 2026.2 (latest) with zwave-js-ui 10.11.0
It’s the zwave I worry the most about. Having to reinstall all my zwave would be so painful if something goes wrong.
