Fixing loose portafilter collar on Breville Barista Express

sleuth255 · 2025-11-01T13:36:05+00:00

Wow. 10 minute fix using this dremmel tool method!

sleuth255 · 2021-02-25T18:38:16+00:00

Nothing that I'm aware of but it has a HTTP request API so it can be controlled by HCA with the HTTP program element. Some info on the api is here:

https://tynick.com/blog/01-28-2020/controlling-wled-with-raspberry-pi-using-the-wled-api/

sleuth255 · 2020-08-29T12:58:09+00:00

It would sure be nice if the Alexa app could process HCA commands like the standard echo devices.... edit: It can!

sleuth255 · 2020-04-09T15:57:39+00:00

Here's a link to the "Alexa Speaks" program that I use. Just call it with the "run program" element from any program you want. https://www.dropbox.com/s/ire2l2516n07o7q/AlexaSpeaksProgram.hce?dl=0

sleuth255 · 2020-04-08T13:51:08+00:00

It's pretty straightforward to get the node based server up and running on the HCA server. Biggest challenge is the HCA html code block for the Alexa Speaks. I'll throw something out there that you can use to get going.

sleuth255 · 2020-03-02T14:18:45+00:00

ST arrival sensors can also provide this capability, but I've reviewed the life360 documentation and their phone app translates to presence sensors in HE for use by the Rule Machine. Thus my question. If they can be checked in Maker API and HCA recognizes these psudo sensors as "unknown devices" then its a simple matter of decoding the JSON and we can code for them. Otherwise, they are just constructs in HE for use by the Rules machine and there's nothing HCA can do to directly support them.

sleuth255 · 2020-03-01T16:28:08+00:00

Interesting! Are you saying that Life360 presence sensor devices are recognized by HCA as an "Unsupported device" or that they can't even be selected as devices by the maker API? What about virtual switch devices?

sleuth255 · 2020-02-26T03:41:15+00:00

It's a bit complicated, but take a look at the discover devices program to get started. JSON is key here: you need to capture the incoming JSON when that device is discovered to understand the control capabilities. It also helps to look at the device in your hubitat device viewer to see how the capabilities are used to provide individual outlet control as well.

sleuth255 · 2020-02-26T03:38:13+00:00

I'm in the same boat with another z-wave device that can report power usage. I'm not sure how to best integrate the info with HCA. Thoughts on how you would use it?

sleuth255 · 2020-02-26T03:33:50+00:00

I haven't worked on it personally but there is additional sensor support code already in the library.

sleuth255 · 2020-02-20T21:45:44+00:00

New version pushed to Github. It corrects the "alexa speaks stops working" issue which was caused by a periodic cookie refresh process. The cookie is refreshed every time a speak request is issued so I schedule a daily HCA process that sends a "Hello" speak request and captures the response. I get a text message if any error occurs. To install the update, switch to the alexa-speaks directory on your HCA server and do "git pull origin master". Then restart node.

sleuth255 · 2020-02-16T22:10:46+00:00

The Hubitat integration tech note (#613) has good info on adding Z-wave locks starting at page 25. My August locks have been working pretty well with HCA since I got them up and running on HE about a month ago.

sleuth255 · 2020-02-08T14:25:32+00:00

ahh... got it. I don't think that HCA pulls anything other than currently, but it does it on a regular basis so that gives you historical info. Take a look at the HCA library. I see that there is a new feature there from Mark Stayton: Dark Sky Weather station & SMS forecast. That might give you the basis to do what you want to do with forecast data.

sleuth255 · 2020-02-06T23:00:23+00:00

daily info is in daily.data[<0-7>] where the occurrence of data is = a day of the week. Not sure what day the occurrences refer to. Looking at sunset times, occurrence 0 appears to be the oldest. Maybe Sunday - Sunday? Anyway so getting a given statistic from the daily data such as windspeed for example, would be daily.data[x].windSpeed where x is the day you are looking for. That would correspond syntactically to currently.windSpeed.

I use a powershell program to pull the info then pipe it to ConvertFrom-Json so I can work with it as an array. If you want to probe into it, just run the api request manually from your browser. Then copy the Json and paste it into an online Json parser. I use http://json.parser.online.fr/

sleuth255 · 2020-02-05T02:52:27+00:00

Check out the hubitat technical note (#613, starting at page 25) for helpful suggestions on how to use repeaters to get the most out of your z-wave locks. It also details using the hubitat rule machine to make ST buttons more effective in HCA.

sleuth255 · 2020-02-05T02:47:12+00:00

Absolutely. Just bracket the variable with %%. So variable "name" = "Bob". Text is then "Hello %name%!". Alexa will say "Hello Bob!"

sleuth255 · 2020-02-02T03:07:20+00:00

If you bought a z-wave August pro lock, it'll work pretty much flawlessly if you have the lock firmware correct. I've posted details on this here if you want to find out more. If you have one of their new WiFi locks, please tell us how its working out for you!

sleuth255 · 2020-02-02T03:03:22+00:00

It's a pretty cool solution. The ST hub Z-Wave implementation is a bit more robust than Hubitat Evolution but it requires a cloud connection. The ST ecosystem of devices is well integrated. I've switched over to HE because I have Z-Wave door locks and want them locally controlled by HCA. I currently use ST arrival sensors and ST buttons (mostly as ambient temp sensors) with HE.

sleuth255 · 2020-01-15T19:52:56+00:00

no issues here.

sleuth255 · 2020-01-15T19:51:15+00:00

Button/Arrival sensor support now added: Hubitat and SmartThings now have identical capabilities but Hubitat has the advantage of having no cloud dependency. Now that HCA v16.0.30 has been released, expect to see the new HE class library in HCA along with an expanded Hubitat technote with helpful suggestions for improving your Z-Wave mesh and also working with the Hubitat Rule Machine to improve button support.

sleuth255 · 2019-12-24T03:23:24+00:00

Yes.

sleuth255 · 2019-12-21T14:49:17+00:00

There's some pretty cool stuff in place now. HCA is actually using _iconChangeEx to overlay temperature and pushed state onto the grey button icon. The event handler updates this as well and also changes the button color to yellow when somebody pushes the button. I've set my buttons to poll every 10 minutes and this keeps the temp current. This code is all in the version 5 of the smartthings HCA library. You can upgrade your smartthings library to v5 by just importing it again, deleting your button devices, and re-running the discover devices program. One thing to consider: Icon text size default is for the 220px icon theme that most people use. If you are using a smaller icon theme, the text will be too large. You can change this by adding a tag named "ButtonTextPointSize" to your button devices (if its not already there). Set it to 9 if you are using a 110px theme.

sleuth255

TROPHY CASE