-
Notifications
You must be signed in to change notification settings - Fork 223
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
unable to open settings / http://192.168.0.197/#/settings keeps loading #841
Comments
Can you take a screenshot of your developer console with the network tab open? |
Can you reload the page while it's open? Also try loading |
|
errr, sorry, And if you could also take a screenshot of the dev console after reloading the page |
Assuming Is this a new install or did you upgrade from an older version? Serial logs ( |
{"firmware":"milight-hub","version":"1.13.0-beta1","ip_address":"192.168.0.197","reset_reason":"External System","variant":"nodemcuv2","free_heap":19080,"arduino_version":"3.1.2","free_stack":1200,"flash_used":983090,"flash_total":0,"flash_pct_free":0,"queue_stats":{"length":0,"dropped_packets":0}} I did had the previous version (and was working good) but i had to wipe the esp to flash the new firmware i update the screenshot in my prevues comment I hope that helps |
Oh no, that's a drag! Sorry you're running into trouble. Yeah, it looks like your settings file is empty (if you could try loading Did you have to erase flash because you had issues after upgrading? Could you check serial logs? |
[No is ju=] http://192.168.0.197/settings empty No, I just couldn't figure out how to update wifi settings logs: |
Looks like you have the baudrate set to 115200. Try setting it to 9600. |
--- Miniterm on /dev/cu.usbserial-0001 9600,8,N,1 --- Setup complete (version 1.13.0-beta1) |
Okay yeah that confirms there's something going on with flash:
I would try the following:
Let me know what you see |
Hi, I have the a similar problem with the webpage interface: My settings gives the follwing output: the about gives the following I was using the firmware 1.13.0 on the device, it happened twice on different ESPs, I'm using nodemcu lua v3 from Ali, just using FUT103 It did work perfectly. I was able to set up 20 bulbs, up to one day, the webpage is not accessible anymore. and more interesting: my HomeAssistant is still able to adresse the bulbs via the ESP through MQTT, it just seems the webpage down. tried on firefox, chrome and chrome incognito. and the switch between dark and bright does work last time I just flashed it again, but the problem reoccurred now. Any ideas on that? |
Ack, that's annoying! Sorry you're running into issues. I'm guessing there's some kind of UI error that isn't being surfaced. Can you include a screenshot of your dev console? |
But the use of the software is FANTASTIC btw.... Thanks a lot here is a video of using it with the open console https://www.youtube.com/watch?v=6GhWM_SSM6I and top and bottom part Thanks for your help |
Perfect, thank you. Can you share the output of |
|
Hello, got the exact same issue. I'm undating to 1.13.1 beta 2, just in case it changes something. Keep you updated. I've created almost all my bulb in one day, then the day after, the interface was no more responding like it is explained in this issue. And the console output of the main page:
tryLoadUrl @ (index):51
tryLoadUrl @ (index):51 |
And, just a big thanks for this solution which is so good for those like us who are using miboxer bulbs ! AMazing work from all aspects, even security one! |
What is the model number of the device you're trying to control?
esp8266 nodemcuWhat firmware version(s) have you tried?
[1.13.0-beta2/beta1]
Which ESP8266 board are you using? (nodemcu, d1_mini, etc.)
Which radio type are you using? (RGBW, RGB+CCT, etc.)
CCT
Have you tried controlling the device with a physical remote?
Yes
Output of http://milight-hub.local/about and http://milight-hub.local/settings
/about
"... /about output. put between the ```s"
/settings
"... /settings output. put between the ```s"
The text was updated successfully, but these errors were encountered: