Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

firmware update from 1.18.22 to 1.18.33 changes IP conf #1530

Open
wiltet opened this issue Feb 4, 2025 · 2 comments
Open

firmware update from 1.18.22 to 1.18.33 changes IP conf #1530

wiltet opened this issue Feb 4, 2025 · 2 comments

Comments

@wiltet
Copy link

wiltet commented Feb 4, 2025

Describe the bug
when update (in my case) from 1.18.22 to 1.18.33
--> "configure IP" all settings will be set to "192.0.0.0"
--> results in that the device will not be discoverable anymore
--> reboot to AP mode and set all to 0.0.0.0 to resolve the cause

Firmware:

  • Version: 1.18.33
  • Device: Plug_Elivco_LSPA9_WL2S_LN882HKI
  • Chip/model: LN882HKI/BK7231T

Template:
{
"vendor": "Tuya",
"bDetailed": "0",
"name": "Full Device Name Here",
"model": "enter short model name here",
"chip": "LN882H",
"board": "TODO",
"flags": "1024",
"keywords": [
"TODO",
"TODO",
"TODO"
],
"pins": {
"0": "LED_n;0",
"3": "Btn;0",
"7": "BL0937CF1;0",
"10": "WifiLED_n;1",
"11": "Rel;0",
"12": "BL0937CF;0",
"19": "BL0937SEL;0"
},
"command": "backlog startDriver NTP; ntp_setServer 192.168.1.1; ntp_timeZoneOfs +1",
"image": "https://obrazki.elektroda.pl/YOUR_IMAGE.jpg",
"wiki": "https://www.elektroda.com/rtvforum/topic_YOUR_TOPIC.html"
}

@divadiow
Copy link
Contributor

divadiow commented Feb 4, 2025

I have not been able to replicate this with a fresh LN 1.18.22 set to 0.0.0.0 OTA to 1.18.33

and neither with fixed ip 1.18.22 -> 1.18.33

@wiltet
Copy link
Author

wiltet commented Feb 4, 2025

Hm...
Not shure if it was set to "0.0.0.0" or "hu.hu.hu.hu" before. But I never did set something specific in "configure IP".
After the update I made today from 1.18.22 to 1.18.33 this happend. Same with a secound of these devices, but from a older build (think it was v1.17.822, but no guaranty). Where all updated over OTA with the web application, btw.
Luckily there is still AP mode. Better than solder again. :)

I do have one more of the same devices with v1.17.822 and identical configs. I'm pretty shure same thing will happen if I flash to 1.18.33.
Is there something I can do to help and find the problem?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants