-
Notifications
You must be signed in to change notification settings - Fork 18
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
Can I make a DevkitV1 esp32 working with tasmoticz #48
Comments
This is debug info; |
not sure what you are doing, but to just answer your questions:
Let’s start simple: |
Hi Joba,
Forgot to enter the MQTT credentials in tasmota, just did i i see this in debug now;
I dont see any new device, looks like idx is empty also see this in debug;
|
so it is not a normal power switch, you just monitor the pin for hi/lo. ok. This has to work first. Tasmoticz does not cause config loss by itself. After that you can change the name of the device (anything but the default) or Tasmoticz will not touch it. I am not sure Tasmoticz will pick up the pin as sensor. Maybe I have to adapt the coding. But first tasmota side needs to work stable |
Can I make a DevkitV1 esp32 working with tasmoticz
I only need to pass through one GPIO port (GPIO1 now) as hardware switch with MQTT
Can't get it to work, just reset everything to default in the esp
What should I enter in the field "Client", it's empty now
This is in my verbose logging;
2024-05-24 09:37:39.059 Tasmota devices: Sending 2 bytes of data
2024-05-24 09:37:39.059 Tasmota devices: c0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �
2024-05-24 09:37:39.110 Tasmota devices: Received 2 bytes of data
2024-05-24 09:37:39.110 Tasmota devices: d0 00 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ю
The text was updated successfully, but these errors were encountered: