Meater thermometer

Feature Requests
191

the beta seems to work great for meater now. Had an issue with insteon thermostat but they are working on that now.

1 Like
192

Did you already tested new integration at 2022.5? I manage to install it and logged in but no devices or entites found.
I suppose there might be some leftovers of the custom component. I only deleted meater folder from custom components folder. Any clue what else Iā€™m missing?

193

Ok, it was a bug and fixed in the 2022.5.1.

194

same issue with 2022.5.1
No devices are added.

195

Are the probe(s) actively connected to your phone? As in not in the charging block?

196

I have a meater plus not meater block and the probe is not in the box and actively connected to the phone while I was adding the integration, in fact I even tried a cook cycle just to be sure.

197

Just a guess. Try to reinstall integration. For me it started working straight after 2022.5.1. Have you uninstalled it from Custom components and restarted hass?

198

I can confirm that the issue was fixed for me on 2022.5.1. On 2022.5.0 I could log into my account, but no probes were detected.

199

I uninstalled it from custom components before 2022.5, which as you all know did not show any devices
Then with 2022.5.1, I removed it from integrations and added it back.
Same thing.

Iā€™m seeing this in the logs.

ERROR (MainThread) [homeassistant.components.meater] Timeout fetching meater_api data

What endpoint it is trying to reach?

Checking in case my pihole is blocking.

200

So what fancy chart is everyone using then for their cooks! Integration is working just fine here!

201

ApexCharts is pretty neat.

202

Probably the one in the code meater-python/meater/MeaterApi.py at 23fb07a66b7edc2b04cf07de623fab445cb3032b Ā· Sotolotl/meater-python Ā· GitHub

203

Hereā€™s my issue.
I tested the endpoint with postman.

Before starting the App and connecting to the probe, I got this

{
    "status": "OK",
    "statusCode": 200,
    "data": {
        "devices": []
    },
    "meta": {}
}

Then I started the app and connected the probe, and I got this.

{
    "status": "OK",
    "statusCode": 200,
    "data": {
        "devices": [
            {
                "id": "REDACTED",
                "temperature": {
                    "internal": 22.4,
                    "ambient": 23.6
                },
                "cook": null,
                "updated_at": 1652022185
            }
        ]
    },
    "meta": {}
}

I figured everything looks good, letā€™s add the integration.
The integration came up empty, and now even with postman Iā€™m getting empty devices.
The app shows proper connection to the device.

What could be the issue?

204

Looks like something for a github issue.

205

Hey @floyduww I notice the API version of this sort of took over this thread. Iā€™m wondering if your local version of this was still making any progress?

Thanks for all your work thus far.

2 Likes
206

Would it be possible for you to share the yaml? Iā€™m new to ApexCharts. Much appreciated

1 Like
207

@jcallaghan,
Were you ever able to make this ESPhome integration? That would have been awesome!
I have the meater integrated using the cloud solution, but would be nice to have a ESPhome proxy, and free up my phone to other use cases.

208

Hey, any chance you know anything about using an esphome proxy? Iā€™d like to use that instead of the cloud-based / Api approach

209

Donā€™t suppose you ever got an answer about the awesome charts @sjabby created?
I am a hack and would love to have that in my dashboard but have not used Apex Charts before.
Many thanks

210

Hi Rev;

I still have some of Floyduwwā€™s original scripts. I havenā€™t used them in a while, can share if you like to test? There were two versions, I remember something about a google comms protocol.

All I know is recently, the meater app (android) doesnā€™t work with my old scripts, but I havenā€™t been bug searching properly to find out why.