Skip to content
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

Closed
megamarco833 opened this issue Oct 7, 2020 · 31 comments
Closed

support for WT32-ETH01: esp32 wifi + ethernet lan #9496

megamarco833 opened this issue Oct 7, 2020 · 31 comments
Assignees
Labels
enhancement Type - Enhancement that will be worked on fixed Result - The work on the issue has ended

Comments

@megamarco833
Copy link

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...

@arendst
Copy link
Owner

arendst commented Oct 8, 2020

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.

@arendst arendst added the question Type - Asking for Information label Oct 8, 2020
@megamarco833
Copy link
Author

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.

thanks for kindness reply.
Yes, there is not the USB but i see that there are pins for GPIOs and GND 5V / 3v3 so i think that soldering pins are ok to flash and then to power on :-)

As it is supposed to be LAN8720 compatible it might already work with Tasmota ESP32.

Just give it a go.

yes, correct.
i'm searching for a device that is cheap (like 5-6€) and can be flashed with tasmota and that can be connected by LAN cable with some free GPIOs to connect relays and pushbutton.
that's why i find this one, the Olimex is too expensive :(
maybe some one has some other device to suggest? :-)

@Jason2866
Copy link
Collaborator

As arendst already wrote the board you have linked will probably work.
We have no other boards and suggest nothing we havent tried.

@sfromis
Copy link
Contributor

sfromis commented Oct 8, 2020

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.

@techman83
Copy link

techman83 commented Oct 9, 2020

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.

@ascillato2
Copy link
Collaborator

Closing this issue as it has been answered.


Support Information

See Docs for more information.
See Chat for more user experience.
See Community for forum.
See Code of Conduct

@arendst
Copy link
Owner

arendst commented Oct 22, 2020

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.

@arendst arendst reopened this Oct 22, 2020
@arendst arendst self-assigned this Oct 22, 2020
@arendst arendst added enhancement Type - Enhancement that will be worked on and removed question Type - Asking for Information labels Oct 22, 2020
arendst added a commit that referenced this issue Oct 23, 2020
- Support for fixed output Hi or Lo GPIO
- Support for ESP32 based Wireless-Tag WT32-ETH01 (#9496)
@arendst arendst added the fixed Result - The work on the issue has ended label Oct 23, 2020
@arendst
Copy link
Owner

arendst commented Oct 23, 2020

With latest commit the WT32-ETH01 is fully supported using below template:

{"NAME":"WT32-ETH01","GPIO":[1,1,1,1,1,1,0,0,1,0,1,1,3840,576,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,1],"FLAG":0,"BASE":1}

To use the ethernet connection use the following defines during compile time:

#define USE_ETHERNET
  // Wireless-Tag WT32-ETH01
  #define ETH_TYPE          0                    // [EthType] 0 = ETH_PHY_LAN8720, 1 = ETH_PHY_TLK110, 2 = ETH_PHY_IP101
  #define ETH_ADDR          1                    // [EthAddress] 0 = PHY0 .. 31 = PHY31
  #define ETH_CLKMODE       0                    // [EthClockMode] 0 = ETH_CLOCK_GPIO0_IN, 1 = ETH_CLOCK_GPIO0_OUT, 2 = ETH_CLOCK_GPIO16_OUT, 3 = ETH_CLOCK_GPIO17_OUT

or use the online command EthType 0, EthClockMode 0 and EthAddress 1

@Blackra1n5
Copy link

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

@Jason2866
Copy link
Collaborator

With Arduino IDE you cant flash Tasmota32.
Do as described here https://tasmota.github.io/docs/ESP32/

@arendst
Copy link
Owner

arendst commented Oct 28, 2020

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!

@Blackra1n5
Copy link

Blackra1n5 commented Nov 1, 2020

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.

@angus51
Copy link

angus51 commented Dec 1, 2020

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/

@efirshik
Copy link

efirshik commented Dec 3, 2020

+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).

@vanelm
Copy link

vanelm commented Dec 22, 2020

Same problem here. Have black one (v1.2). Tried with TX0/RX0 and TXD/RXD with grounded IO0 and IO2

@1danielsan
Copy link

Hello Everybody! I am trying to flash wt32-eth1 chip!
I successfully flash it using https://www.espressif.com/.../flash_download_tool_v3.8.5.zip
esp32 flash
(using tasmota32.bin instead of webcam.bin, of course)
configured correct template on module:
{"NAME":"WT32-ETH01","GPIO":[1,1,1,1,1,1,0,0,1,0,1,1,3840,576,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,1],"FLAG":0,"BASE":1}

used the online command EthType 0, EthClockMode 0 and EthAddress 1, as Theo said before.
(I get "command" : "Unknown" for every command entered..)

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!

@Jason2866
Copy link
Collaborator

Jason2866 commented Dec 23, 2020

@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
Edit: use ONLY the additional ESP32 files from here https://github.com/arendst/Tasmota/tree/development/tools/Esptool/ESP32

@efirshik
Copy link

efirshik commented Dec 24, 2020

@Jason2866 trying your tasmota32-ethernet.bin with template for wt32-eth01 and commands for up ethernet. wifi work, but ethernet dont up :(

@1danielsan
Copy link

as found here:
https://community.home-assistant.io/t/esphome-ethernet-connectivity-feature-request/110390/64

should it be:

Settings for WT32-ETH01

ethernet:
type: LAN8720
mdc_pin: GPIO23
mdio_pin: GPIO18
clk_mode: GPIO0_IN
phy_addr: 1
power_pin: GPIO16

@19leva89
Copy link

19leva89 commented Jan 7, 2021

Good afternoon, tell me, can I use WT32-ETH01 to receive a signal via WI-FI and transmit it to the network via LAN? Make a repeater out of it.
cf1269cc319007ceb4abac240a214c72
Something like that.

@angus51
Copy link

angus51 commented Jan 9, 2021

Good afternoon, tell me, can I use WT32-ETH01 to receive a signal via WI-FI and transmit it to the network via LAN? Make a repeater out of it.
cf1269cc319007ceb4abac240a214c72
Something like that.

It can be possible, but you will need to develop a specific firmware, and will have a bad throughtput. Find an orange pi zero, a little more expensive, but ready to use.

@19leva89
Copy link

19leva89 commented Jan 9, 2021

It can be possible, but you will need to develop a specific firmware, and will have a bad throughtput. Find an orange pi zero, a little more expensive, but ready to use.

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!

@Jason2866
Copy link
Collaborator

No, not with Tasmota. There are no plans to implement.

arendst added a commit that referenced this issue Jan 27, 2021
Add support for ESP32 ``Module 5`` Wireless Tag Eth01 (#9496)
Jason2866 added a commit to Jason2866/Tasmota that referenced this issue Feb 12, 2021
* 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>
Repository owner deleted a comment from Mitko939 Oct 16, 2021
@szuler1979
Copy link

szuler1979 commented Nov 9, 2021

I have a little problem with Tasmota and Ethernet (in summary – Ethernet doesn’t work without wifi connection):

  • I have successfully flashed WT32-ETH01 using FT232RL FTDU module, ESP_Flasher and tasmota32-ethernet.bin (from https://github.com/tasmota/install/raw/main/firmware/unofficial/tasmota32-ethernet.bin)
  • after flashing I have connected to WT32-ETH01 via wifi, set my wifi user and password,
  • at that point I could connect to WT32-ETH01 via my network (through wifi but ethernet didn’t work)
  • I have copy and pasted template {"NAME":"WT32-ETH01","GPIO":[1,1,1,1,1,1,0,0,1,0,1,1,3840,576,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,1],"FLAG":0,"BASE":1}
  • after restart I have typed in console EthType 0, EthClockMode 0 and EthAddress 1
  • from this point Ethernet started to work – I have internal ip address 192.168.0.161 for wifi connection and for Ethernet 192.168.0.162
  • pinging Ethernet address showed that this is really cable connection (3ms rather than 100ms on wifi connection - also green led is flashing next to Ethernet port)
  • I wanted to have only Ethernet connection due to my wifi problems (that was the reason I chose esp32)
  • BUT when I turn wifi off (wifi 0 in console or changing wifi configuration to non existing wifi), I also loose Ethernet 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?

@barbudor
Copy link
Contributor

barbudor commented Nov 9, 2021

Turn Wifi off : https://tasmota.github.io/docs/Commands/#wifi

@szuler1979
Copy link

As I wrote before - I turned wifi off (command "wifi 0" in console) but after that I lost also my ethernet connection

@sfromis
Copy link
Contributor

sfromis commented Nov 9, 2021

My WT32-ETH01 board with tasmota32-ethernet.bin v10.0.0 works fine without wifi connected. In fact, I have a small Berry script networkflipper.be running after boot to detect if both Wifi and Ethernet are connected, and in that case turn off Wifi.

tasmota.set_timer(30000,
  def()
    import string
    var eth = string.find(tasmota.cmd('Status 5')['StatusNET']['Hostname'], '_eth') > 0
    if tasmota.cmd('Wifi')['Wifi'] == 'ON' == eth
      tasmota.cmd('Wifi ' .. (eth ? 0 : 1))
    end
  end)

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 _eth

@isarrider
Copy link

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"?

@szuler1979
Copy link

szuler1979 commented Jun 12, 2022 via email

@paulb-smartit
Copy link

@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 Edit: use ONLY the additional ESP32 files from here https://github.com/arendst/Tasmota/tree/development/tools/Esptool/ESP32

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

@Jason2866
Copy link
Collaborator

@paulb-opusvl Ethernet support is default since a while in Tasmota for ESP32.
There is no need for searching and using the additional needed files for ESP32.
All needed is in factory firmware. Easiest flashing is via Tasmota WebInstaller.
Please read always the docu. Things changes fast in Tasmota.

Repository owner locked as resolved and limited conversation to collaborators Aug 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Type - Enhancement that will be worked on fixed Result - The work on the issue has ended
Projects
None yet
Development

No branches or pull requests