My kettle has been sat in he cupboard since the demise of Appkettle, they say it’s the little things in life, but I really did get a kick out of coming into the kitchen and the kettle starting to boil this morning!
I have to admit, that after almost 7 years of using Home Assistant, this was my first custom addon. Not only got my kettle up and running again, but also did something new… thanks again
Ok I’ve made some tweaks and set up a repo for this which can be added from HA. I’ve added HA autodiscovery topics so no need to manually configure the sensors any more. I’ve also added min/max level settings so the fill level can be calibrated to your particular device, enjoy!
Hello Longmover, thanks for making the add-on for AppKettle. I’m new to Home Assistant. I use Homey for Home automation. To test my Home Assistant installation I used my Philips Hue lights and they work.
For my AppKettle I followed the instructions.
Blocking the IP of the AppKettle from the internet
Config the mqtt_host, mqtt_usr and mqtt_pwd
Running the AppKettle add-on.
It discovers the IP and MAC adress of my AppKettle. After a short period I get a time out.
What goes wrong? And how can I fix it? Thanks in advance.,
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting AppKettle
Kettle IP: 192.168.1.92
Kettle IMEI: GD0-*****-1aeb
Traceback (most recent call last):
File "/appkettle_mqtt.py", line 761, in <module>
['160', '1640']
Sent broadcast messages, waiting to hear back from kettle...
Discovered kettle with following parameters:
- Name: AK_Kettle
- IP: 192.168.1.92
- IMEI: GD0-*****-1aeb
- Wifi SSID: Vaka**********ink
- Software version: 0.4.9
argparser()
File "/appkettle_mqtt.py", line 757, in argparser
- Device Status: 000400005d6402850000
main_loop((args.host, args.port), args.imei, args.mqtt, args.calibrate)
File "/appkettle_mqtt.py", line 494, in main_loop
mqttc.connect(mqtt_broker[0], int(mqtt_broker[1]))
File "/usr/lib/python3.11/site-packages/paho/mqtt/client.py", line 914, in connect
return self.reconnect()
^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/paho/mqtt/client.py", line 1044, in reconnect
sock = self._create_socket_connection()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/socket.py", line 851, in create_connection
raise exceptions[0]
File "/usr/lib/python3.11/socket.py", line 836, in create_connection
sock.connect(sa)
TimeoutError: timed out
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Welcome! I’m glad you’ve got a use for this. I think, based on the output, that it’s a problem with your MQTT configuration. If you haven’t got it already I’d recommend installing MQTT Explorer, connecting to your broker and monitoring the messages coming in. If you don’t see an appKettle topic then for some reason the MQTT messages aren’t getting through, have you configured the MQTT port? If not set it to 1883 and restart the addon.
This morning I got it working by using my native homeassistant account in stead of the extra account I made under settings. I also did a renewed installation of the MTTQ broker en your AppKettle add-on.
I also recently scrapped this kettle - it was just very painful to use, with the beeping on boiling, and complaining if it was too full even if it was half full. In all honesty, the world doesn’t need internet connected kettles
Hi,
even since 2017 not so many things changed with a kettle, the appkettle is from 2017, pretty unsexy and not available to buy
Goal: just want to let the Water Boil (HA or Alexa) - if I plan to drink a Tea/Coffee and for not waiting in the kitchen longer as necessary.
Do you have similar solutions like this running? How did you managed it?
I found the 40€ Aigostar and the Nedis SmartLife for 62€ - both with Apps/Wifi Interfaces. Probably Tuya & Co - and integratable into HA.
Would take one of theese in worst case.
Would prefer to hack one of the simple ones actually, putting a small 3.3V power supply PCB including a tiny esp32 with tasmota on it.
Thats just what I did with a Hayden kettle with the switches in the base. I am currently in the process of changing the static blue leds with adressable ones on a board with wled. And becouse I used the inbulit temperture sensor signal I know the water temperture, so change the led colour from blue ( cold ) all the way to red at ( boiling ) I have a 1 farard supercap that keeps the led lit for long enough when the kettle is removed from the base for pouring .
There was enough space in the base? You connect to the switches with an optocoupler (pc817?). Did you used a separate power supply PCB or something from the internal “base electronic”? Any pictures?
yes there was enough space in the base for the d1,a small 240 to 5v power supply and a relay,(to press the boil button) The PCB power supply could not supply extra current to drive the D1. I do have a spare base that I want to re do with optocouplers and use them for the other buttons for differant tempertures. Sorry no pictures, I will get some when I modify this new base with octocoouplers.
Thanks mate. I got the Aigostar today. Currently, it’s available at Kaufland for 35€. It’s quite straightforward to use, although it’s another product reliant on cloud services. The Tuya app isn’t compatible; instead, it requires the “AigoSmart” app. Unfortunately, there’s no API, and the manufacturer doesn’t seem interested in providing one. I’m considering returning it and creating my own solution. An ESP32-C3 would be compact enough for the job - flashing Tasmota on it. Typically, you’d need one or more PC817 for the buttons. With some luck, you might find a 5v or 3.3V power source inside the base. I need to figure out which kettle i can order and has enough space in the base.