-
-
Notifications
You must be signed in to change notification settings - Fork 33.4k
La Marzocco integration stopped working altogether #143217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey there @zweckj, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) lamarzocco documentation |
Appear to be having the same/similar issue. Deleted everything LM related from HA & started again. Nothing has worked. Now getting “Failed setup, will retry: Error while communicating with the API” |
Experiencing the same issue since yesterday. The device shows up as unavailable in HA. However, through the LM-App I'm able to control the machine just fine. |
I have the same problem. I noticed it today. The LM app works just fine, though. |
It seems like La Marzocco shut down the old endpoints the integration still uses, this should be fixed with #142098 in 2025.5. |
Since this is completely not working for folks now, any chance we could ask that this get bumped up into 2025.4.3? |
This contains breaking changes and therefore is not allowed in a patch release. Also, this is a major rewrite and really needs to go through beta testing as I still suspect there'll be issues with different machine types. |
Beta testing starts 30th April, long wait unfortunately. |
Is there a way to downgrade the firmware somehow? |
No, there isn't. Even so, the old Cloud APIs are removed so even if you were to downgrade you'd still be left in a half broken state.
You don't have to wait for beta testing to try the nightly docker tags 😎 |
Same Problem here! |
@zweckj is it possible to install an alpha/beta version of the integration so we can help test? |
how do I get to be a beta tester? |
You can install the HA nightlies, but I'm still working on a couple things, so I don't know how helpful this would really be at this stage.
By installing the HA beta once it releases (April 30th), there should be plenty tutorials how to do that. |
I know. I had so many cool automations, like the machine would turn on 30 minutes before my Wake Up Alarm so I could make espresso first thing, or if Home Assistant detected me driving towards home in the afternoon, it would ask me if I wanted to turn on the machine so that it was ready when I walked in the house. Home Assistant even knows how long it takes to warm up based upon the current coffee boiler temperature and would adjust the time to turn on accordingly (approximately 6 degrees F per minute in case anyone wanted to know that). For example, if I was an hour in traffic to get home and the boiler is 78 F, it would know to not turn on until approximately 21 minutes before I was due home. I also have it where when the machine is actually ready, it turns on my Mazzer grider, and set the lights over the machine. All this is dead now and I can't wait for May 7th (or sooner if I get impatient and install beta). |
Spare a thought for those of us that use the shot timer for accurate measurement and drip prediction. There's a 4 second difference between what the Cloud APIs think is the shot timer and what it actually is, now that they've completely removed the local websocket API |
Oh that sucks. Espresso is such a precise art form, those seconds really count! Pouring out a doppio in honor of our fallen brethren. |
Strange, it seems to be working again for me this morning. Perhaps La Marzocco re-enabled the API access? |
Same here @GlenWi, strange |
Same here. Had deleted the integration, but after your comments, I reinstalled it and it seems to work again. Heureka |
Hmm - still not working here. Using LM Gateway v5.0.10 and HA 2025.4.4 |
The problem
The connection to my LaMarzocco GS3 AV stopped working altogether today, and I can't get it to reconnect.
Like many others I made the mistake to upgrade the LMZ Gateway firmware to (now) 5.0.10 some weeks ago. Since then, it worked somewhat (everything worked except unusable temperature sensors). However, today, without any upgrade/action the connection broke and I cannot get it to reconnect at all.
I have read all the other issues related to this LMZ design change, which reflect mostly the fact that the local API is gone. But it seems now the connection to the cloud endpoint is broken too.
Please see debug log attached, let me know if I should look elsewhere for additional info.
What version of Home Assistant Core has the issue?
core-2025.4.2
What was the last working version of Home Assistant Core?
core-2025.4.2
What type of installation are you running?
Home Assistant OS
Integration causing the issue
lamarzocco
Link to integration documentation on our website
https://www.home-assistant.io/integrations/lamarzocco
Diagnostics information
home-assistant_lamarzocco_2025-04-18T10-23-29.718Z.log
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: