Nice!! Glad to see it helps!

Nice! Glad to hear things help

Thanks! Definitely a lot of new folks jumping in with the Cloudcutter stuff and it is definitely different from Tasmota.

Awesome job! Glad to hear it helps

Glad you enjoyed it!

I do plan to dive into some more aspects of things. Thank you!

Glad it helped!

No problem 👍glad people are learning things

That is the big key to things. Baby steps and don't try to do this stuff all at once. Keep building on top of what you learned.

That's the plan! Continue to dig a little deeper into things.

Glad I could help!

Yup. Isolation is key here.

​@@digiblurDIYIt is key but most users don't do it, they just have 1 WiFi SSID and connect devices to it. Using a Password Manager is not a lot of work

Thank you!

Awesome. I still use both myself and use what works best for the project. Great to know both.

@@digiblurDIY In the title you mentioned Beken Devices. Did I miss that?

Nope, all the same since ESPHome supports it as of a few months ago.

digiblur.com/2023/08/19/updated-tuya-cloudcutter-with-esphome-bk7231-how-to-guide

Yes. You can swap to esp32 for the BT Proxy.

Glad to hear that!

The voltlink cp2102 will spoil you for any application like this.

Right. You don't have to understand how to write it to be a pro at it, just read it and make it work. You can copy and paste all the fluff needed is what my point was on that.

Is it using a secondary MCU?

Yes. It would need to be esp32 based though.

@digiblurDIY I understand it would need to be ESP based, but is that yes, it is possible to add a Bluetooth proxy to an existing, for example, ESPCam, mmwave,etc ?

Glad it helped! And many thanks!

I doubt it would be damaged. You do need to set it up with the right driver or PWM assignments.

@@digiblurDIY Thanks for the reply. As mentioned, bulb works OK for everything (RGB, CW, WW, soft On/Off, etc) EXCEPT power On/Off from wall AC which makes me nervous about experimenting. Can you point me to another bulb w/esp8266 setup where the firmware install code specifically addresses switch power to specific pins?

@psubo3b not sure I understand the AC off?

@@digiblurDIY The Bulb is in a ceiling fixture controlled by standard AC power wall switch. Under Tasmato firmware (outside of HA) the bulb would turn On/Off when the wall switch was toggled (Yes, I understand that with AC Power Off the bulb is Offline). After conversion to ESPHome the bulb no longer responds to that same wall switch control. So somehow, other than "color" control etc which works OK, the firmware installed code is missing something for support of AC power switch - BUT I'm concerned that experimenting (Sonoff S31 "binary sensor" and "switch" code) MIGHT send 120 volts to a wrong pin in a way that could cause damage... (Not sure other bulb firmware examples online seem to not contain any AC On/Off code - Many other bulbs must be in sockets where Users want simple switch control.) Thanks for trying to help!

@psubo3b are you keeping power on the device all the time? I do this with Tasmota switches and bulbs and let the relay stay active all the time and the wall switch sends commands to the light over device groups. Best of both worlds thing.

Pop open the controller and see what chip is inside

ah, ok, i need to have one in hand first. I was hoping to know before I buy one, but Ill go ahead and buy it so i can find out what chip is in it. I didnt see it in HA Esp data base. ty.@@digiblurDIY

Indeed! I do want to continue and move on to setting up some sensors, drivers etc that people will run into on typical household devices

I started using zigbee, only have 2 wall switches and 2 motion sensors. My motion sensor always goes offline, why do not know. So I am planning on making esp32 sensor instead. Thanks

Yes even multiple are supported esphome.io/components/sensor/dallas

@@digiblurDIY 👍☺️

More or less the same difficulty to get flashed the first time - if you need to solder for Tasmota the first time, you will for ESPHome on the same devices (unless you already have Tasmota - you can usually flash ESPHome from Tasmota's web interface). ESPHome doesn't need MQTT for Home Assistant, but can use MQTT if you need to for some reason (eg if you want to use it without Home Assistant, or need to interoperate with some other system, or just prefer to stick with MQTT instead for some reason). Tasmota plays better if you want to run without any automation server. I have an outdoor light that uses Tasmota's coordinates based sunset/sunrise functionality to switch on at sunset and then turn off at 11pm every night. This would be harder to do with ESPHome where it lives because there's no HA or ESPHome server at that location. ESPHome seems to be better if you've got a bunch of very similar devices with matching configs (other than their names) because you can create one yaml config for the base device and include it, and just change the device names. Like if you bought 20 of a specific model of light bulb, and they all need to have the same GPIO settings, same wifi SSID, etc.

The flashing part is the same for manual processes of ESPHome or Tasmota. You can do the OTA Cloudcutter process for newer Beken devices but Tasmota doesn't support those chips were ESPHome does. There are so many differences between the two and it really depends on the project for which one I'm going to use.

BDM pins ukposts.info/have/v-deo/rGCgbKSEmaeAtHU.html

I know they were working on a few things with BT too but not sure. I do know that device groups is working with it on an external component which is pretty cool.

There's not really just one. It all depends on what you are doing. I can suggest one model to you after that.

Have you tried it using the IP address?

Currently running Tasmota on my ifan myself but I do know there are ESPHome configs out there for it, just a little more advanced though given the various relays and such to lock out for each speed.

What's the error?

@@digiblurDIY When I try to run "docker run --rm --net=host -v "${PWD}":/config -it ghcr.io/esphome/esphome " it says: "Traceback (most recent call last): File "/usr/local/bin/esphome", line 33, in sys.exit(load_entry_point('esphome', 'console_scripts', 'esphome')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/esphome/esphome/__main__.py", line 1040, in main return run_esphome(sys.argv) ^^^^^^^^^^^^^^^^^^^^^ File "/esphome/esphome/__main__.py", line 1003, in run_esphome return PRE_CONFIG_ACTIONS[args.command](args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/esphome/esphome/__main__.py", line 517, in command_dashboard return dashboard.start_web_server(args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/esphome/esphome/dashboard/dashboard.py", line 1507, in start_web_server app.listen(args.port, args.address) File "/usr/local/lib/python3.11/dist-packages/tornado/web.py", line 2207, in l isten server.listen( File "/usr/local/lib/python3.11/dist-packages/tornado/tcpserver.py", line 183, in listen sockets = bind_sockets( ^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/tornado/netutil.py", line 162, i n bind_sockets sock.bind(sockaddr) OSError: [Errno 98] Address already in use" I have absolutely no idea what I am doing wrong.. I might be dumb; I dont have a lot of experience in this topic and I am new to it so sorry in advance if this is a stupid question

Looks like something is already in use there so it can't start. What all do you have running? That looks like you are using docker run and not docker compose?

@@digiblurDIY I reinstalled everything and somehow now I got it, I got a dashboard but it is not visible in home assistant. Is there a way to create the dashboard in home assistant gui?

You could add it into the menu in as if you need it there