[Bug]: there is no launch after the update about firefly_luciferin

[whakru]

@sblantipodi
I have found a solution to all the problems! the application did not work correctly due to the presence of Russian words in the installation path. in my case ( C:\Users\Юлия\AppData\Local\Firefly Luciferin) I reinstalled the app in (C:\Firefly Luciferin) everything started working fine! and the firmware has been updated. It remains for you to solve this problem) I think you can just change the default installation path.

[whakru]

@sblantipodi
I will help with any information as far as possible. A little later I will try to update the microcontroller via usb. since the new version of the application does not see the microcontroller via wifi.
#79

[whakru]

Please take in mind that when you open Firefly Luciferin it can take some seconds to detect the ESP, wait 30 seconds in the worst case ever.

yes of course, I waited more than 10 minutes. The device was accessible through a browser. but it didn't show up in the app. Tried restarting the device, also tried restarting the computer. gave no result. Perhaps the problem is really temporary on the side of the router. but what is strange is that the device is available in the local wifi network. As soon as I have time, I will definitely try to reboot everything. it will be in a few days.

[whakru]

I have seen that you selected a baudrate of 2000000. This is not really recommended if not if very special case.

this did not cause problems for me earlier, but I understood you and will take this into account in the future.

[sblantipodi]

Hi @whakru,
thanks for your continued interest in Luciferin :)

I'm going to look at all the defects you opened soon.
I have deleted my FireflyLuciferin.yaml and created a new one with your config.

I then started Firefly Luciferin app v2.7.3 and no issue occurred.
I'll try to reproduce it with a different firmware version like the one you used Glow Worm Luciferin v.5.3.1.

I'll keep you posted.

[sblantipodi]

@whakru I'm not able to reproduce this one.
as I said, I used your config file with an ESP running the old 5.3.1 firmware.

sometimes routers may have some disconnections problems with the ESP devices,
latest firmware should mitigate this problem when using DHCP.

Please take in mind that when you open Firefly Luciferin it can take some seconds to detect the ESP, wait 30 seconds in the worst case ever.

I leave this issue open, if you would like to try to reproduce it we can still investigate further to understand
if there is an issue in Luciferin or if it was a temporary problem of the ESP beeing disconnected.

[sblantipodi]

I have seen that you selected a baudrate of 2000000.
This is not really recommended if not if very special case.

Generally ESP8266 doesn't handle baudrate over 15000000,
I'll leave the baudrate to the default 500.000 value if you use the WiFi stream.

If you want to use the USB cable instead of the WiFi stream (not really recommended if you have a good wifi signal) a baudrate that is too big for your microcontroller may create problems to the PC while connecting to the microcontroller.

[whakru]

After 10 minutes, nothing was found, although the device is available at the local address. http://192.168.31.84/

[sblantipodi]

@whakru please open the browser to
http://192.168.31.84/

on the right top corner you can access the firmware settings. what is the device name?
is it the same selected in the "Settings" -> "Mode tab" -> "Output device"?

Do you see the device in Firefly Luciferin as soon as you start the software?

Can you show me a screenshot of the "Mode tab" and one of the "WiFi/MQTT tab" please?

[whakru]

@sblantipodi

I clearly have a problem with the application, it does not start after clicking the save button.

[sblantipodi]

@sblantipodi
I have found a solution to all the problems! the application did not work correctly due to the presence of Russian words in the installation path. in my case ( C:\Users\Юлия\AppData\Local\Firefly Luciferin) I reinstalled the app in (C:\Firefly Luciferin) everything started working fine! and the firmware has been updated. It remains for you to solve this problem) I think you can just change the default installation path.

Thank you very much for reporting the problem, I really appreciate your continued support @whakru.

I'll fix it.