-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
support for WT32-ETH01: esp32 wifi + ethernet lan #9496
Comments
This device does not support PoE; it lacks the hardware to provide it. It also has no nice power connection like a USB socket so you'll need to solder power connectors yourselves. As it is supposed to be LAN8720 compatible it might already work with Tasmota ESP32. Just give it a go. |
thanks for kindness reply.
yes, correct. |
As arendst already wrote the board you have linked will probably work. |
While the board is not PoE compatible, it may be possible to do a "fake PoE" by just supplying power over a couple of wires not needed. If you use a full cat5e cable, you should be able to run the lower speed of 100Mbps (probably a lot more than enough) over 4 wires, leaving two pairs for power/ground. Of course, careful splitting needs to be done in parallel at both ends, and better not connect such to standard ethernet devices. From photos it appears that not all the 8 RJ45 pins are connected to something. |
If you really want Active PoE (803.2at) then you could spring for a wESP32*, buy an Active PoE splitter that breaks out the power and leaves you with data/power or do as @sfromis suggested, passive PoE. Which you can either make a cable or just buy a pair of passive PoE leads, data/power in at one end and data/power out at the other. The wESP32 is pretty nice, well designed and well made. It comes at a cost, worth it IMO though. *I haven't checked Tasmota on mine yet, I really should dig mine out and try it. |
Closing this issue as it has been answered. Support InformationSee Docs for more information. |
I have two of them and try to get tasmota running with the eth interface. As there is almost no documentation available it's a bit of trial and error to get it going. For now eth doesn't work. |
- Support for fixed output Hi or Lo GPIO - Support for ESP32 based Wireless-Tag WT32-ETH01 (#9496)
With latest commit the WT32-ETH01 is fully supported using below template:
To use the ethernet connection use the following defines during compile time:
or use the online command |
How have you guys been flashing the WT32-ETH01. I'm currently trying to flash through Arduino IDE and not using Tasmota. I'm sorry if this is off topic but this seems to be one of the only results with WT32-ETH01 |
With Arduino IDE you cant flash Tasmota32. |
As any esp8266 or esp32 without an usb connector; ground gpio0. Also use the correct flash mapping which is default present on platformio. Time to get rid of arduino ide and upgrade to pio! |
I've been trying to flash with grounding GPIO 0, using TXD, RXD, and CH340. But I haven't gotten any luck flashing these WT32-ETH01 boards. I have no problems flashing normal ESP32s and ESP8266 using the same setup. |
Hi. I came accros the same problem. I have a WT32 ETH v1.2 (black) Ground IO0 (the pin next to TX0 and RX0), and use TX0 and TX0 to flash (not TXD & RXD). I use this link to flash https://tasmota.github.io/docs/ESP32/ |
+1, dont flash, and dont read chip_id with esptool. only debug info if connect any ground tx0 and rxd. AT commands in standart firmware dont work in txd rxd pins, i mean send work, but dont come answer. 115200 none/8/1 wt32-eth01 v1.2 (black). |
Same problem here. Have black one (v1.2). Tried with TX0/RX0 and TXD/RXD with grounded IO0 and IO2 |
Hello Everybody! I am trying to flash wt32-eth1 chip! used the online command EthType 0, EthClockMode 0 and EthAddress 1, as Theo said before. but when I connect the cable there is no way to understand if it is using it... (from a network scan it is connected only via wifi) is there something missing? is it mandatory to compile instead of using precompiled development binaries? (I am new to platformio and I don't know how to insert all files needed... is there a tutorial somewhere?) Thank you very much! |
@1danielsan you have to compile a version with ethernet support. Ethernet support is in no precompiled firmware. You can try my unofficial build https://github.com/Jason2866/Tasmota-specials/raw/firmware/firmware/tasmota32/other/tasmota32-ethernet.bin |
@Jason2866 trying your tasmota32-ethernet.bin with template for wt32-eth01 and commands for up ethernet. wifi work, but ethernet dont up :( |
as found here: should it be: Settings for WT32-ETH01 ethernet: |
The 5 Mbps bandwidth is fine for me. And the dimensions of the board are very important to me, they should be minimal, orange pi zero is large for me! |
No, not with Tasmota. There are no plans to implement. |
Add support for ESP32 ``Module 5`` Wireless Tag Eth01 (#9496)
* Fix compile error on enable sensor debug * Update NeoPool support extended types * Fix redox unit * Fix hydrolysis unit * HA discovery via MQTT for BLE MI sensor devices * Add 'MI32Option5 1' to only accept sensors if they have a BLEAlias * Refactor TX2x sensor float outputs * Clear MI sensors when setting 'mi32Option5 1' * Document CmndSetoptionBase() * Fix warnings * Add light synonyms Add commands ``ChannelRemap``, ``MultiPWM``, ``AlexaCTRange``, ``PowerOnFade``, ``PWMCT``, ``WhiteBlend``, ``VirtualCT`` as synonyms for ``SetOption37, 68, 82, 91, 92, 105 and 106`` respectively * Fix compile error * Refactor dtostrfd * Refactor dtostrfd * Add Modbus errorcode * Add Zigbee SetOption synonyms Add commands ``ZbNameKey``, ``ZbDeviceTopic``, ``ZbNoPrefix``, ``ZbEndpointSuffix``, ``ZbNoAutoBind``, ``ZbNameTopic`` as synonyms for ``SetOption83, 89, 100, 101, 110 and 112`` respectively * Make USE_BLE_ESP32 the default for sensors. * belt and braces fix test failure * Fix PMS3003 sensor message lenght and CRC chk * Refactor TX2x sensor * Refactor ext print usage * Update changelog * Clarify file name functionality * rename + soime explaination * Add Sensor83 99 cmnd write to eeprom * Refactor some IP addresses * Refactor some IP addresses * Add support for ESP32 ``Module 5`` Wireless Tag Eth01 Add support for ESP32 ``Module 5`` Wireless Tag Eth01 (arendst#9496) * Add template place holders * Support trailing silence in buzzer tune Support trailing silence in buzzer tune (arendst#10694) * Remove unwanted persistance * Add commands ``BuzzerActive``, ``BuzzerPwm`` as synonyms for ``SetOption67, 111`` respectively Add commands ``BuzzerActive``, ``BuzzerPwm`` as synonyms for ``SetOption67, 111`` respectively * refactor dtostrfd * add L1MusicSync mode * cleanup * Use dgr name for MQTT if SO88 * Added macro for SO synonyms and MQTT * Add support for once off speed and fade * Add Sonoff L1 Music Sync control Add command ``L1MusicSync <0|Off>|<1|On>|<2|Toggle>, 1..10, 1..100>`` to control Sonoff L1 Music Sync mode sensitivity and speed (arendst#10722) * Initial support for ZStack 3 * Zibee add ``SetOption120 1`` or ``ZbEndpointTopic`` to add the endpoint as suffix in topic when using ``SetOption89 1`` * Respond to fade2 and speed2 * Merge fade2 with speed2 * Forgot changelog update * Change L1 music sync defaults * Revert "Merge pull request arendst#10736 from emontnemery/once_off_speed_fade_fix" This reverts commit aa8a23e, reversing changes made to f6111e9. * Update changelog * Zigbee more synonyms * Update changelog * Fix subStr related exceptions * Zigbee fix ZbNoAutoQuery synonym * XNRG7 ADE: Set Debug log level from 3 to 4 for ADE comms It is better for visualization while checking * In case of lost comms with PZEM, avoid losing Today Energy * Refactor Sensor83 cmnd * Add Sensor83 TakeOver cmnd * fix ip crashes * Update xdrv_13_display.ino * Add Sensor83 switch light relay cmnd * NeoPool cleanup polling * Refactor command line arguments * Refactor command line arguments * Refactor command line arguments * Refactor command line arguments * Update stale-actions.yml * Use espressif32 platformio 3.0.0 * Deleted duplicated entries in i18n.h The entry: #define D_ZIGBEE_NOT_STARTED "Zigbee not started" is duplicated in i18n.h from all language files. This produces a warning while compiling due to redefinition if changing the language in my_user_config.h * Return to previous output of IPADDRESS1 command * Update af_AF.h * change solo1 to release_v3.3-solo1-bd65eb8d1 * add and fix new string ops in rules * Add strict rule scale parameters * Change NeoPool Sensor83 to prop. cmnds * Add MAX31865 specific setting per sensor * Fix IrRemote_Full JSON message (arendst#10680) * Revert comment * Add demo for driver/sensor settings file storage (arendst#10786) * Fix IrRemote_Full JSON hash value (arendst#10680) * Fix IrRemote_Full JSON leading zeroes (arendst#10680) * ESP32-S2 * Oops * s2 toolchain * Refactor File Settings Demo * Add optional SSE demo * Prep support ESP32S2 * ESP32S2 toolchain is there * Cleanup webserver * refactor + bugfixes * Prep ESP32S2 * Fix ETH_ADDR related warning * Zigbee refactor sending ZCL packets * fix regression * Update xsns_62_esp32_mi.ino * Revert ESP32S2 ethernet defines * Prep ESP32S2 * Prep ESP32S2 * Prep ESP32S2 * Prep ESP32S2 * LITTLEFS.h casing for ESP32 * Publish more precise Free Heap metric * Zigbee command ``ZbScan`` to do an energy scan on each radio channel * Reduce code size * fix i2s audio * Update AudioOutputI2SNoDAC.cpp * Allows individual control of power and mode Power and mode must be individually controllable. Some devices may not function properly if the mode is also turned off when the power is turned off. see. crankyoldgit/IRremoteESP8266#1402 * Prep ESP32S2 * Add fragmentation translations * ESP32 increase number of relay GPIOs from 8 to 28 * Add Server to HTTP header (arendst#10831) * BLE_ESP32 (xdrv_79): Start scan as soon as we are connected to a device - saves missing a few adverts. iBeacon (xdrv_52): Clean up BLE_ESP32 based driver; add commands and advert timing. Remove HM10 code - it's in the other one..... * Add timeout initialise * Add additional #if for CONFIG_IDF_TARGET_ESP32 * update comment * Increase number of switch GPIOs from 8 to 28 * Increase number of button GPIOs from 4 to 8 * Allow BLE when ethernet only connected Allow BLE when ethernet only connected (arendst#10753) * ESP32 Increase number of interlock groups from 4 to 14 - Removed migration support for versions before v8.1.0 (Doris) - ESP32 Increase number of interlock groups from 4 to 14 * Clean settings code * Increase ESP32 SwitchText to 28 * Fix long SwitchText message logging * Update Italian language * Platformio esp8266 2.6.3 * Platformio esp8266 2.6.3 * Update af_AF.h * Create fy_NL.h * Update fy_NL.h * Update platformio.ini * Update platformio_tasmota32.ini * Update platformio_tasmota_env.ini * Update platformio_tasmota_env.ini * Update platformio_tasmota_env32.ini * Update af_AF.h * Update fy_NL.h * Applied standardization to WiFi Changed Wifi and wifi to WiFi for the purpose of standardization * Corrected some Dutch words onmiddelijk requires a double L. i and e where wrongfully ordered in Windsnelheid. * Update nl_NL.h * update max31855 json temperature name publication For using the thermostat function, publication of the measured temperature was using the wrong name. Changed to the common used name. * Add read buffer function to TasmotaSerial * if pulse is not specified, let the lib use its default value * Preview of Berry language for Tasmota32 * sns_53_sml: make ebus correctly interpret signed values Signed-off-by: Sven Ebenfeld <sven.ebenfeld@gmail.com> * xsns_53_sml: add option to emit ebus sync only telegrams Signed-off-by: Sven Ebenfeld <sven.ebenfeld@gmail.com> * fix wrong test on pulse * add variant FY and build map files * Add files via upload * Update Tasmota_build_master.yml * Update Tasmota_build_master.yml * Consolidate ESP specific functions * Enable higher PWM frequencies for ESP32 LEDC peripheral of ESP32 allows higher PWM frequencies than the ESP8266. Higher frequencies come with reduced available bit depth (as by https://esphome.io/components/output/ledc.html). New max value of 50 kHz to include at least the frequency for 4-pin pwm fans and a bit more. * Add no_share_mask support, DevGroupSend channels in hex, AND/OR operators, Use dynamic log buffer * Add support for transistor-based output without DAC Add support for transistor-based output without DAC (arendst#10875) * Add SDM72 Modbus energy meter * Update xdrv_27_shutter.ino * Update xdrv_27_shutter.ino Fix shutter pwm command to include device number and update loggin information. * Prepare RISCV * Add DGR device map support * Use device map for received power item * Update xdrv_27_shutter.ino Add #define to turn off servo in ShutterPowerOff. * Rename DevGroupDevice to DevGroupTie * Use # prefix for color channel hex value * Fix DevGroupSend invert operator default value * Bring ModeSet value out of the for loop, this ModeSet is repeated for every other value on the webpage. * move renderer, add touch display slider * warning if ESP8266 firmware is too big * Bump version to 9.2.0.7 * Default disable ESP32 BLE due to instabilities * Fix NTC calculation for ESP32 Fix NTC calculation for ESP32 (arendst#10906) * Use Arduino ESP32-S2 RC6 * fix teleinfo standard mode * add 7 seg number font * better impl of ebus negative values * json subroutines, sendmail shortcut * tasmota32-ble * Tasmota variant ESP32 bluetooth * Add dummy fade2 (arendst#10916) * Delete xdrv_85_esp32_bluetooth.ino No need for this file and it takes up precious driver numbers. * correct order * Delete tasmota_template.h * Update tasmota_template.h * Update tasmota_configurations_ESP32.h * Update tasmota_template.h * bluetooth in repo firmware * bluettoth in branch release-firmware Co-authored-by: Norbert Richter <norbert.richter@prsolution.eu> Co-authored-by: Simon Hailes <simon@yellaumbrella.tv> Co-authored-by: Theo Arends <11044339+arendst@users.noreply.github.com> Co-authored-by: Stephan Hadinger <stephan.hadinger@gmail.com> Co-authored-by: s-hadinger <49731213+s-hadinger@users.noreply.github.com> Co-authored-by: lonmi <mikaelonen@yahoo.com> Co-authored-by: blakadder <arguson@gmail.com> Co-authored-by: Paul C Diem <PCDiem@FoxValley.net> Co-authored-by: Erik <erik@montnemery.com> Co-authored-by: Adrian Scillato <35405447+ascillato@users.noreply.github.com> Co-authored-by: gemu2015 <gmutz2010@googlemail.com> Co-authored-by: Adrian Scillato <39969427+ascillato2@users.noreply.github.com> Co-authored-by: crispy78 <42983001+crispy78@users.noreply.github.com> Co-authored-by: Barbudor <barbudor@barbudor.net> Co-authored-by: Naoki Sawada <hypweb+github@gmail.com> Co-authored-by: bovirus <1262554+bovirus@users.noreply.github.com> Co-authored-by: RvDesign <r111222@gmx.net> Co-authored-by: Sven Ebenfeld <sven.ebenfeld@gmail.com> Co-authored-by: Thomas A <arthofer.thomas@gmail.com> Co-authored-by: mikep1998 <44448320+mikep1998@users.noreply.github.com> Co-authored-by: Yves De Muyter <yves@alfavisio.be>
I have a little problem with Tasmota and Ethernet (in summary – Ethernet doesn’t work without wifi connection):
Is it normal? Why I can't have Ethernet connection without wifi connection? Then what is the point having Ethernet connection? What am I doing wrong? |
Turn Wifi off : https://tasmota.github.io/docs/Commands/#wifi |
As I wrote before - I turned wifi off (command "wifi 0" in console) but after that I lost also my ethernet connection |
My WT32-ETH01 board with tasmota32-ethernet.bin v10.0.0 works fine without wifi connected. In fact, I have a small Berry script
I did not do anything to make it work without Wifi, and am using the same template and Ethernet settings as you posted. Are you aware that the host name changes with Ethernet? It is the Wifi-related host name suffixed with |
did you get it working in "airplane mode"? |
To be honest I gave up and switched to ESP Home - work like a charm.. 12 cze 2022 19:14 Alex ***@***.***> napisał(a):
As I wrote before - I turned wifi off (command "wifi 0" in console) but after that I lost also my ethernet connection
did you get it working in "airplane mode"?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Just because others may search and come across this. The links are now 404, but I found the files here: https://github.com/arendst/Tasmota-firmware/tree/main/static |
@paulb-opusvl Ethernet support is default since a while in Tasmota for ESP32. |
Have you looked for this feature in other issues and in the docs?
yes
Describe the solution you'd like
i know that tasmota is at beta stage for esp32, and i fint this very cheap device that can support also the LAN connection
https://www.aliexpress.com/item/4000349581141.html?spm=a2g0o.cart.0.0.79283c00NvKUI3&mp=1
it will be great if tasmota firmware can be used on this device that cost less than 6€
the advantage could be that if wifi is not good we can use lan cable, maybe it could be PoE powering?
and maybe is it possible to use the free GPIO to connect devices such as relays?
it would be great to connect for example some relay for domotic usage and having it cable by lan instead of wifi only
Describe alternatives you've considered
Olimex ESP32-PoE
i see that in tasmota this device seams to be supported, but it cost more than 3 times...
my knowledge is not so deep to understand if Olimex has more feature than the proposed cheaper device
THANKS to all for support, hope that I do not write anithing wrong...
The text was updated successfully, but these errors were encountered: