-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Espresso out of nowhere #74
Comments
Logs would be great (before/after the event)! ESPHome has a feature which resets the ESP every 15 minutes when not connected to WiFi. This may also be related to #26 |
This is my config with debugging. I also measured everything. I have 3.3v on the tx0 and 5v on the rx0. When i dont connect the display everything works fine. When i connect the display something is ticking inside the coffeemachine. If i remove the debug options and connect the display it works, thicking is over. Measurements are normal. esphome: esp8266: logger: external_components:
api: ota:
wifi: manual_ip: ap: captive_portal: time:
uart:
philips_coffee_machine: sensor:
text_sensor:
button:
switch:
number:
[21:27:17][C][logger:186]: Level: DEBUG |
You only need the debug option on one of the UART (preferably the mainboard one), as they both see the same messages (aside from those which are injected by this component, hence the mainbaord preference). IIRC, I have at some point had an ESP which made a clicking noise when the LED was blinking (fast) or during high WiFi loads. Can you describe the clicking noise further? Is it more of a buzzing sound, how loud is it? Can you locate where it's coming from? (the custom PCB?) Here is a debug version which can cut down on messages even more, but it's only for messages coming from the display and it may require modification based on the machine that is being used. Based on the altered/removed message: are surprise espressos / shutdowns still a thing? Also make sure that the machine is still working as intended without the modification to rule out that something broke. |
The clicking noise is from inside the machine. When i change the debug its al fine. I think something else is going on. This night there was nothing wrong, no turning on automaticly, no ticking and no espressos. This morning the automation worked fine, get my coffee when i woke up. During an hour no strange behavior. But then, there was an update from Esphome. 2024.7.1. After this update, say 10 minutes, the device give me an espresso. I reset the device but no results. Measuements on PCB are normal. [09:16:29][D][uart_debug:114]: >>> 01:03:00:0D:00:00:00:02:12:D5:55:00 Sending this, keeps going on and on. |
Hm, ... this is wired behavior.
If you remove the espresso buttons from the config, does the erratic behavior happen with other beverages? |
Today I do it al over again.
So no hardware problem. Now i go over to the software, starting like you said. Post the results later this day |
I replaced my ESP32 (it stopped working) by a ESP8266 board. Since the change, I'm also getting espressos out of nowhere! @dkwolf1, did you solve it already?
To answer this question, yes it actually brews coffee. I do have some logs from Home Assistant already: Normal espresso procedure:
Random espresso:
|
@xi-s no...i even quit the project. But what you say now is opening my eyes again. I always worked with the 8266...should is be the 32 then... |
Nope, still happening. |
I moved from using GPIO3|GPIO1 + GPIO13|GPIO15 to GPIO3|GPIO1 + GPIO14|GPIO12. So far I'm on 18 hours of "idle" state without random espresso |
Interesting.... Any chance you have serial logging still enabled? Make sure to use |
I made sure to include the Current working config; The only difference between random espresso and normal is the choice of GPIO right now:
|
Hello! I followed this project a while and now I've installed everything. Pcb and picoflex cables, I al worked perfect. But, when the machine is running idle, after let's say 15 minutes he makes an espresso out of nowhere...more people with this problem? I don't have any log files yet, I will try to get them.
The text was updated successfully, but these errors were encountered: