Yes, they changed their API and broke things. Please test pre-release 0.11.1b1
Thanks, happy to⌠if you could provide the link to your github?
Thanks, happy to⌠if you could provide the link to your github?
Try this one: Release v0.11.1b1 ¡ zweckj/lamarzocco ¡ GitHub
if you go to HACS and go to âre-downloadâ you can just select it (as Iâm assuming youâre using my fork already as you got a Micra)
Thanks sorted⌠jumped over to your github and re-added all again. Initial testing appears good
Does this answer refer to the new gateway version? Is it foreseeable when you will release the commits?
Thank you very much and best regards!
No (afaik) this was only regarding zeroconf/discovery. What type of machine do you have?
Iâm using a Linea Mini. Will this also work (locally) with your fork?
according to @mrvautin my fork does work with the Minis. However, it is only cloud based communication. The Micra relies heavily on Bluetooth for local communication and as I have no Mini I have no idea, whether they changed it to use BT as well or stuck to their old version.
I havenât tested the Bluetooth on my Mini but the cloud comms works perfectly. @zweckj if you add your last commits to re-enable Bluetooth into a release, Iâd be happy to test on my Mini.
Thanks! Added pre-release version v0.11.2-beta.1
LM is being pretty aggressive about getting folks to update to the new gateway version, as I canât get past the gateway update dialog to use the app at all. You basically have to update. The integration continues to work, so thereâs that.
As primitive as the original interface is, Iâm sad that they decided to abandon local support. Plus, reverse engineering it was kinda fun. In any case, updating is a one way street and it looks like lmdirect will be EOL. Without being able to test the local interface, it will just rot and will need to be removed at some point.
Iâll update my machine over the weekend and get on the PR over the weekend. @zweckj thanks for being prepared for this .
Two things @rccoleman:
- zeroconf might still be broken in my branch, but the config-flow is not even triggered for me. Thinking they might have changed the domain. How did you discover the one itâs using atm? Wireshark?
- once you upgraded please confirm whether they actually removed the lmdirect endpoints, because then Iâll do a rewrite to remove all the if-elses currently needed to differentiate between direct and cloud
I just used an mDNS listener, canât remember which one. The âDiscoveryâ app on iOS shows it for me now:
Thanks, but nothing. Either something is broken for me or they removed it altogether.
This whole change is so disappointing, your heroic work excepted, of course. It has only downside for IoT integration, as far as I can tell.
If only they added more than that one measly HTTP endpoint, but also POSTs as well. Would be such a clean solution⌠But no, they rely on a mix of HTTP, WebSockets, Bluetooth and Cloud instead. Such a terrible design⌠Iâm also sad if they indeed removed the old interface, especially as you spent so much time on it.
Itâs the future, I guess. If thereâs something still there, Iâll find it .
New gateway update - new set of warnings
Using - [v0.12.0-beta.6]
Logger: lmcloud.lmlocalapi
Source: runner.py:179
First occurred: 08:49:04 (3 occurrences)
Last logged: 08:53:17
Unmapped message from La Marzocco WebSocket, please report to dev: [{âBrewingStoppedGroup1StopTypeâ: âVolumeâ}, {âBrewingSnapshotGroup1â: â{âgroupConfigurationâ:{âgroupNumberâ:âGroup1â,âcapabilitiesâ:{âgroupTypeâ:âAV_Groupâ,âboilerIdâ:âCoffeeBoiler1â,âboilerTemperatureâ:95,âhasScaleâ:false,âhasFlowmeterâ:true},âdoseâ:{âdoseIndexâ:âDoseAâ,âstopTargetâ:0,âdoseTypeâ:âPulsesTypeâ},âdoseModeâ:{âbrewingTypeâ:âPulsesTypeâ}},âbrewingInfoâ:{âdoseIndexâ:âDoseAâ,âstopReasonâ:âManualâ,âtimeâ:59.778999328613281,âstopTypeâ:âVolumetricâ,âvolumeâ:0}}â}, {âBrewingStoppedGroup1StopReasonâ: âManualâ}, {âBrewingStoppedGroup1DoseIndexâ: âDoseAâ}, {âBrewingStoppedGroup1Timeâ: 59.779}, {âBrewingStoppedGroup1VolumeTargetâ: 0}, {âBrewingStoppedGroup1Volumeâ: 0}]
Unmapped message from La Marzocco WebSocket, please report to dev: [{âBrewingStoppedGroup1StopTypeâ: âVolumeâ}, {âBrewingSnapshotGroup1â: â{âgroupConfigurationâ:{âgroupNumberâ:âGroup1â,âcapabilitiesâ:{âgroupTypeâ:âAV_Groupâ,âboilerIdâ:âCoffeeBoiler1â,âboilerTemperatureâ:95,âhasScaleâ:false,âhasFlowmeterâ:true},âdoseâ:{âdoseIndexâ:âDoseAâ,âstopTargetâ:0,âdoseTypeâ:âPulsesTypeâ},âdoseModeâ:{âbrewingTypeâ:âPulsesTypeâ}},âbrewingInfoâ:{âdoseIndexâ:âDoseAâ,âstopReasonâ:âManualâ,âtimeâ:14.850000381469727,âstopTypeâ:âVolumetricâ,âvolumeâ:0}}â}, {âBrewingStoppedGroup1StopReasonâ: âManualâ}, {âBrewingStoppedGroup1DoseIndexâ: âDoseAâ}, {âBrewingStoppedGroup1Timeâ: 14.85}, {âBrewingStoppedGroup1VolumeTargetâ: 0}, {âBrewingStoppedGroup1Volumeâ: 0}]
Unmapped message from La Marzocco WebSocket, please report to dev: [{âBrewingStoppedGroup1StopTypeâ: âVolumeâ}, {âBrewingSnapshotGroup1â: â{âgroupConfigurationâ:{âgroupNumberâ:âGroup1â,âcapabilitiesâ:{âgroupTypeâ:âAV_Groupâ,âboilerIdâ:âCoffeeBoiler1â,âboilerTemperatureâ:95,âhasScaleâ:false,âhasFlowmeterâ:true},âdoseâ:{âdoseIndexâ:âDoseAâ,âstopTargetâ:0,âdoseTypeâ:âPulsesTypeâ},âdoseModeâ:{âbrewingTypeâ:âPulsesTypeâ}},âbrewingInfoâ:{âdoseIndexâ:âDoseAâ,âstopReasonâ:âManualâ,âtimeâ:46.540000915527344,âstopTypeâ:âVolumetricâ,âvolumeâ:0}}â}, {âBrewingStoppedGroup1StopReasonâ: âManualâ}, {âBrewingStoppedGroup1DoseIndexâ: âDoseAâ}, {âBrewingStoppedGroup1Timeâ: 46.54}, {âBrewingStoppedGroup1VolumeTargetâ: 0}, {âBrewingStoppedGroup1Volumeâ: 0}]
Constant log entry:
2023-07-16 08:53:39.420 DEBUG (MainThread) [lmcloud.lmcloud] Using local status object
Hi, iâm thinking of getting one for a coffee shop, so the api feature interests me, anyways got some questions i hope you guys can answer
- Looks like recent fw broke the connection to HA? what if we downgrade OR not upgrading the FW?
- How helpful & accurate the api count for auditing ingredients usage and products ?
- If it is not reliable is there other coffee machine with API like this?