stream pointer vanished / http_request error

[bert1111]

*Describe the bug I had some wifi issues (broken antenna) which were resolved but suddenly the s0 meter vanished from my network. I installed the latest update through the website with a usb cable. I can set the network and then after a few seconds I see stream pointer vanished. And device connection is lost again. I did find that there is a bug somewhere with esp home but not yet solved. Is there a workaround? Strange thing is that it has worked for two months before the wifi problem.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[huizebruin]

Do you see a ssid with the name S0tool*** with your mobile? Than its not connected to your wifi network.

And than you must connect it again to your network. you can connect to the s0tool ssid. and go to 192.168.4.1 and there you can connect to your wifi network again.

[bert1111]

no that ssid doesn't appear anymore. it has something to do with this issue. https://github.com/esphome/issues/issues/5949. I don't know if you're aware of this.

[huizebruin]

What i heart it was fixed an little time ago. But it doesn't when i see this. i will contact some of my other Dutch users on my discord if they also have the same error after the update or flashing the s0tool.

What version of Home assistant and ESPHome are you using?

[bert1111]

Firmware: 3.6.2 (ESPHome 2024.9.1) Versie | core-2024.9.3 Installation type | Home Assistant OS What does appear to work is not finish the flashing by skipping the search for wifi networks. Than the s0tool network appears. Go to the url you mentioned above. Set the wifi there. The watermeter is now connected for a few minutes were it previously disconnected after a few seconds with mentioned error.

[bert1111]

Nope. It's gone again. Same error [http_request.arduino:137] Stream pointer vanished!

[huizebruin]

When u use the same esp it stores the ssid and password in his esp. That's why you don't see the selecting ssid (wifi) list.

[bert1111]

I think I'm not explaining it good enough. Or I don't understand it enough. I'll try again but be clearer of the steps I'm taking.

So the watersensor was working fine up until last night with version 3.6.1. Today I saw in HA that all watermeter sensors were not available. I reinstalled via the webpage to version 3.6.2. And from the moment I select my wifi network I lose connection with error http_request.arduino:137] Stream pointer vanished!

The last thing I tried was reinstalling via the website and skipping the set wifi part. Then the s0*** network appears. I chose that network and set the wifi via 192.168.4.1 like you said. Then the s0 network disappears because it is connected to my home wifi. So I do see my ssid to connect with in the list.

After that, it is connected and is visible again on my network until it starts giving the http_request.arduino:137] Stream pointer vanished! error. This was the case first after a few seconds with the first way. And with the skipping the set wifi part, but setting through the 192.168.4.1 after a few minutes.

[bert1111]

This is the log after succesfully connecting to my wifi. And after this it even appears the device crashes after waiting a while. Page does not respond

`[I][safe_mode:041]: Boot seems successful; resetting boot loop counter [I][captive_portal:032]: Captive Portal Requested WiFi Settings Change:

[W][component:157]: Component wifi set Warning flag: scanning for networks [I][wifi:540]: - 'xxxxxxx [I][wifi:313]: WiFi Connecting to 'xxxxx'... [I][wifi:617]: WiFi Connected! [W][component:170]: Component wifi cleared Warning flag [W][component:170]: Component api cleared Warning flag `

[huizebruin]

I will look if i can remove the http sensor for now

[scns]

I hope that Will fix the issue.

When there is a fix i Will test The fix first thing tomorrow

[bjornpri]

Identical problem here on a Wemos D1 Mini V4.0.0 Type-C USB. Has been working fine for a long time. Until 3.6.2: Works after install, stops working with same issue explained in this thred after power recycle.

[huizebruin]

i'm pushing now a version online without the ota update and http update . https://github.com/huizebruin/s0tool/actions/runs/11085402377

[huizebruin]

https://github.com/huizebruin/s0tool/actions/runs/11085452651 this looking better

[huizebruin]

@bjornpri and @bert1111 Would you try it out to flash it from https://s0tool.nl

I uploaded the changes.

https://github.com/huizebruin/s0tool/actions/runs/11085452651/job/30801987513

[bjornpri]

I tried twice. No change. Is there a visual change I can look for so we know I have the new version?

[huizebruin]

I named the version inside of the basis file 3.6.3

[bjornpri]

Is still says 3.6.2 every where. I tried a third time. No change. After install i visit the device and it looks good. Then without removing power i press the restart link in the web UI and it comes up with the same issue.

I do not connect it to ESPHome I just restart it right after flashing.

[scns]

The release build is not yet started. @huizebruin, van you publish 3.6.3?

[scns]

I named the version inside of the basis file 3.6.3

I think that is not working because The firmware on the website is not updated on The site.

[huizebruin]

Its building right now https://github.com/huizebruin/s0tool/actions/runs/11085685338

[scns]

Build is done!

[scns]

@bjornpri @bert1111 can you try again?

[huizebruin]

It should now be online, i flasht a spare part one now from the website to 3.6.3.

[bjornpri]

Almost. It survives all kinds of resets. but... I can not add it to ESP Home:

INFO ESPHome 2024.9.1 INFO Reading configuration /config/esphome/s0tool-watermeter-202f4c.yaml... INFO Updating https://github.com/huizebruin/s0tool/@main INFO Detected timezone 'Europe/Oslo' Failed config

update.http_request: [source /data/packages/b59da29a/esphome/components/s0tool-watermeter-update.yml:2]

Component update.http_request requires 'platform: http_request' in component 'ota'. platform: http_request name: Firmware Update id: update_http_request source: https://s0tool.nl/s0tool-watermeter/manifest.json

[scns]

Almost. It survives all kinds of resets. but... I can not add it to ESP Home:

INFO ESPHome 2024.9.1

INFO Reading configuration /config/esphome/s0tool-watermeter-202f4c.yaml...

INFO Updating https://github.com/huizebruin/s0tool/@main

INFO Detected timezone 'Europe/Oslo'

Failed config

update.http_request: [source /data/packages/b59da29a/esphome/components/s0tool-watermeter-update.yml:2]

Component update.http_request requires 'platform: http_request' in component 'ota'.

platform: http_request

name: Firmware Update

id: update_http_request

source: https://s0tool.nl/s0tool-watermeter/manifest.json

@bjornpri Did you remove your old entry in esphome?

[huizebruin]

im adding it to my beta machine.

[bjornpri]

It failed while verifying the yml file with the error: Component update.http_request requires 'platform: http_request' in component 'ota'.

I added it in ESPHome and I broke it again. I'll try once more deleting old stuff and restarting HA.....

It autodiscovers and I can 'adopt' it... I adopt it and I get this during install:

[huizebruin]

I've been testing it now a couple of times. But it's working here now good and no losses that the device is going offline.

[huizebruin]

Adopt first to ESPHome and after that to Home assistant.

But did you delete it from your esphome dashboard also?

[scns]

I think The repo needs to be refreshed on your'e instance.

In the worst case you have to wait till tomorrow. (24 hrs)

I had with my own projects The same.

Sounds weird but sometimes you have to wait. The device in the integration is still working if it has the same name

[bjornpri]

Adopt first to ESPHome and after that to Home assistant.

But did you delete it from your esphome dashboard also?

That is what I did. Deleted every thing i HA and ESPHome. It fails validating the yaml while adopting in ESPHome. I states it is missing OTA.

[bjornpri]

im adding it to my beta machine.

ESPHome 2024.8.1? Im using 2024.9.1.

[huizebruin]

or try clean build files , then validate , then install

[bjornpri]

While selecting "Clean Build Files":

[scns]

Just wait at least 24 Hours 😅

[bjornpri]

It seems that ESPHome 2024.9.1 requires the platform: http_request to be able to properly adopt the device. I can controll it by setting new values and restart it from HA but the enteties in HA will not update. The API wil probably not work without he API encryption key...? Yes?

And when I add it (the OTA: -plattform: http_request) ESPHome is happy and starts updating the device, and when its done, it is broken, back to this original issue.

[scns]

I Will test tomorrow.

[bjornpri]

I Will test tomorrow.

Thanks

[huizebruin]

Me to and hopefully we find a solution for the problem.

[scns]

I flashed this morning my production S0 tool. And everyrhing worked fine.

Import in ESPhome, no problem. And the device came online in HA. I Will monitor of the device stay's online.

[bjornpri]

Im testing this morning. Same issue.

My tool's yaml file seems to be missing platform: http_request' in component 'ota'. @scns does your tools yaml file contain the ota component?

[huizebruin]

@bjornpri at at line 4 after yaml@main maybe is that it.

[bjornpri]

@huizebruin What at line 4? Where? Line 4 in the yaml file there is no ..@main In the output log there is the timezone on both @scns and mine after ...@main.

If i put in: ota:

• platform: esphome
• platform: http_request

the device validates and updates but brakes after update, with the original issue.

[huizebruin]

Do you flash it by this link https://s0tool.nl/Installation.html ? or do you hit the install button inside the esphome dashboard ?

remove the s0tool out of your esphome dashboard and than flash it .

[JGeeforce]

Yesterday at 23:23 S0tool was suddenly available. Long story short, this morning I clean build files, deleted the device in ESPhome and did a new install by connecting it to the USB port. It's back again.

[bjornpri]

Yes. I use this:

[bjornpri]

Do you flash it by this link https://s0tool.nl/Installation.html ? or do you hit the install button inside the esphome dashboard ?

remove the s0tool out of your esphome dashboard and than flash it .

Done this 3 times now. No sucsess

[huizebruin]

im testing that one at his moment too

[bjornpri]

The flash is good. Works fine. Does not breake the device. Stands reboots. All fine so far.

[bjornpri]

@huizebruin Does your ESPHome yaml file for your device include:

ota:

• platform: esphome
• platform: http_request