Getting new values from the device is very slow about eq3btsmart

[dbuezas]

Uhm... I see. Maybe I'll go back to polling, as the advertisments don't seem to correlate to valve changes as I thought.
I could make the polling interval configurable too, in your case you probably prefer to use a bit more battery but have a faster update rate

[dbuezas]

Do you know if the calor up updates the data to the phone in real time while you are connected?

[wjarka]

Actually it still didn’t update Valve change from one of those so it’s over 4 hours now.

I don’t remember if I ever used the mobile app for it, so can’t answer it now. Could check tomorrow if that’s helpful:)

[wjarka]

So yeah, I think polling could work better for me, definitely:). Or whatever makes it update faster :)

[dbuezas]

I just made a new release (v1.0.0) that should work much better. Can you update and tell me if this solved the issue?
Updates from the device to HA should take at most 5 minutes now (2.5 minutes on average)

[wjarka]

Does it use polling?

Because I was thinking that this dongle I have was not really... reliable? And since proxies didn't work for me I was going to try to pair it today and get proxies working and see if the problem persisted. However, let me install the update and see if that fixes it :)

[wjarka]

Definitely works faster. Let me know if you would like to test the push state once I fix the proxies.

Maybe - due to a poor reliability - it didn't pick the advertisement?

[wjarka]

Actually, that one thermostat I tested yesterday didn't pick up changes after over 5 minutes, so it may not have been related to the push vs poll. Let me fix the proxies later and see if that changes anything.

The other ones work faster. However, yesterday, the other ones were slower too, so there is definitely an improvement ;)

[dbuezas]

Push state didn't work well, i also tried adding notifiers to all characteristics with no success.
So back to polling, I think it is now far better than even the standard component (back then when it actually worked)

I still need to find out what is broken with the BTProxy, so if you test it, do send me some logs :)

[dbuezas]

I'll close the issue as v1 fixes it. Feel free to reopen it if the problem reappears (it shouldn't :) )

[wjarka]

@dbuezas what logs should I look at? I guess disconnect the dongle and then watch logs right? I think I sent some already in the proxy issue, but if there is more I can look at - pointing me in the right place would be appreciated;)

[dbuezas]

I mean both the Home assistants logs, and EspHome logs (add a logger component with level: debug first)
I hope I can also give it a try today

[dbuezas]

And yes, disconnect the dongle first to ensure the component uses the btproxy.
BTW, I just realized that if esp32_mqtt_eq3 works, then there should be a way for this to work too. Interestingly, I didn't see any special mention to pairing there...

[wjarka]

I am completely new to ESP, just used the HA flasher to install BTproxy so I will have to figure out how to even access logs from it.

I’ll give it a try when I have some time ;)

[wjarka]

Or did you mean ESPHome integration logs from HA?

[dbuezas]

Oh, EspHome is awesome to explore! I think you'll have lots of fun with that too.
But anyway I just checked and the logger component is already included in the default BTProxy, so yes, just click LOGS inside the EspHome panel of home assistant (make sure to install the "EspHome addon" first)

[wjarka]

Interestingly - when I adopt the device via ESPHome - it seems to break the proxy altogether and nothing connects via the proxy.

Editing the config file and reinstalling makes it be offline in ESPHome, so I am a bit confused.

[wjarka]

Disregard. Wrong Wi-Fi password will do that. I mistyped it and it was stored in secrets ;)

[dbuezas]

Haha, there are so many moving pieces...

I also did some tests and did fix one half of the issue (characteristic handles are off by one between linux and EspHome, so switched to UUIDs), now we need to wait for pairing support in esphome.

[dbuezas]

Hey @wjarka, in v4 you can set the scan interval yourself. The default is 1/minute, but you can do 10 seconds if you wish. I haven't measured battery consumption though

[wjarka]

@dbuezas do you think after all the improvements in the meantime - maybe you could see if the passive scan for getting values wouldn't work? :) Could be a good way to go around the BT Proxy instabilities :).

[dbuezas]

I tried, but I didn't find any relevant data in the broadcasted data except discovery stuff "hey, I'm here, this is my mac, my name is CC-RT-BLE and and I offer these services & characteristics". I found no actual temperatures or any useful data.
It would be really nice if the EQ3 didn't require a connection...

[wjarka]

Gotcha. Yeah, bummer :)

[dbuezas]

Partially inspired by your comment in another issue

I don't want it to be longer than 1 minute because of one of my automations that needs to react as quickly as possible (long story).

I decided put a relay before my hot water pumps and use the valve state to turn them on/off. It's saving me 800Wh per day!

[wjarka]

Nice! It’s amazing how you can optimize by some very small automations like this :)