-
Notifications
You must be signed in to change notification settings - Fork 84
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
Column "IP address" shows "0.0.0.0" in case of ETH connection #266
Comments
Good one. I'll fix that later this week. (And hopefully release that thing :D ) |
Also, can you pls paste here the result of |
|
i'm working on it right now. what tasmota version are you using with this? |
The "Shelly Pro 4PM" is running Tasmota v14.1.0 and another device "WT32_ETH01" with v14.2.0 |
Hello @jziolkowski , is there a Windows exe file available for tests? Thanks |
I'll prepare a pre-release later today |
Please have a look to the screenshot from version tdmgr_2024.9.3_x64: .) Both devices connected by ETH doesn't show the IP address (DHCP used) Which logs are you needed? Thanks! |
Pls send me that sorting issue is weird, it works on my side. Tho I don't have any 0.0.0.0 address present. I'll have a look. |
Shelly Pro 4PM
WT32_ETH01
|
check this build: https://github.com/jziolkowski/tdm/releases/tag/pre2024.9.4.dev10 |
Hi @jziolkowski please have a look to "Gateway", in case of an ETH connection this column should be taken from "StatusNET"."Ethernet"."Gateway" And in the case of an ETH connection, the symbol in the “Device” column should be suppressed or replaced with another one. Thanks again! |
Ah fair point. Sigh. Seems I'll have to get some eth esp32 devices. |
For example, a WT32 ETH01 would indeed be helpful. |
@jziolkowski please reopen this ticket, thanks. |
...by the end of this week at the latest. |
No problem at all, just letting know ;) |
@jziolkowski both devices are connected to 192.168.7.x/24
|
Ok this is weird. I have unit test for that and based on the example payloads you provided it should be working. |
Another issue is that tasmota remembers the gateway IP of the wifi interface. So even if you're disconnected from wifi then this address matches the value check I'm using and returns the set value. In tasmota WiFi is the main interface, so I think I need to follow the same approach in TDM. Maaaaybe the gateway check should check if the wifi IP address is 0.0.0.0 and then decide which GW value to use. However, I still have no idea why it insists on the 0.0.0.0 address in your example. Can you tell me which version are these devices of yours? |
Both devices are running version 14.2.0, thanks. |
Hello
using a Shelly Pro 4PM connected over ETH and Wifi is disabled.
In case of
{"IPAddress1":"0.0.0.0 (0.0.0.0)"}
the alternative IP address{"IPAddress2":"192.168.7.1"}
shall be used for this column and for calling the "WebUI".Thanks!
The text was updated successfully, but these errors were encountered: