A new way to flash the modules

[BeanieBots]

Weird!
The hardware has not changed.
I get this error on two boards when trying to revert to 1.44.2 using the tool kit.
No error when flashed with 1.47.2
Conclusion: Once flashed with 1.47.2, you can't go back to 1.44.2
Is this correct? Has anyone else had a similar issue? or even tried to revert?

[cicciocb]

Weird!
The hardware has not changed.
I get this error on two boards when trying to revert to 1.44.2 using the tool kit.
No error when flashed with 1.47.2
Conclusion: Once flashed with 1.47.2, you can't go back to 1.44.2
Is this correct? Has anyone else had a similar issue? or even tried to revert?

No, this is not possible.
However, could be a problem linked to the web flasher

[BeanieBots]

Sorry to repeat, but just to be 100% clear, are you saying it is NOT possible to go back to 1.44.2?

[cicciocb]

Sorry to repeat, but just to be 100% clear, are you saying it is NOT possible to go back to 1.44.2?

I agree, it is not clear.
It should be possible to go back and flash the module with any version.

So, rolling back to the 1.44.2 is possible without losing any existing data

[BeanieBots]

Ok, thanks for making it clear.
The only outstanding mystery is why I now get "flash read err, 1000" on two devices when reverting to 1.44.2 which did not have this error before.
(this is repeatable having re-flashed with both several times)
Also, I've now had several instances of corrupt files with 1.47.2 which is why I tried to revert.
I know Robin eluded to this happening with earlier firmware but I've only personally experienced it with 1.47.2

I'll continue to persist with 1.47.2 because the recently added (save/load to PC) buttons make non-device dependant backups much easier

EDIT: FWIW, file corruption has occured both with and without SD enabled.

[AndyGadget]

I also have not been able to revert from 1.47.2 to 1.44.2 by reflashing.
(Edit - Ignore, I had the 1.47.2 image loaded in the old toolkit )

I've had problems with MQTT on 1.47.2.
I'll try to get some time tomorrow to strip the program down to basics and post here.

[Electroguard]

Rather than revert back, obliterate the current unwanted with something non-Annex (perhaps overwrite with an appropriate size bin file), then flash with required version of Annex as if first time.

[AndyGadget]

Rather than revert back, obliterate the current unwanted with something non-Annex (perhaps overwrite with an appropriate size bin file), then flash with required version of Annex as if first time.

That was going to be my next step

[AndyGadget]

I have a program running on an ESP8266 which picks up the current colour from the Cheerlights project.
Both this and the MQTT test in the manual work fine.

I've now tried both these programs on ESP32 with 1.44.2 and 1.47.2 (both with the modified syntax) and neither connect to the relevent MQTT server.
(I've never tried MQTT on ESP32 before - I've just had a little 8266 Cheerlights Glowy Cat chugging away in a corner for ages.)

Code: [Local Link Removed for Guests]

pause 1000
' MQTT SSL test program
' Using mosquitto test server
onmqtt mqtt_msg
wlog mqtt.setup("mqtts://test.mosquitto.org",1)
wlog mqtt.connect("","") ' No login / pass required
wlog mqtt.subscribe("/AnnexTest") ' subscribe to the topic /AnnexTest
wlog "connection : ";MQTT.Connected()


for z = 1 to 5
  ' send messages to the topic /AnnexTest
  wlog mqtt.publish("/AnnexTest", "Annex"+str$(z))
  pause 500
next z

wait

mqtt_msg:
wlog "TOPIC  : "; mqtt.topic$
wlog "MESSAGE: "; mqtt.message$
return



'' This should return the name of a colour from the Cheerlights server
'wlog bas.resetreason ' 12 - Software reset CPU
'wlog "***"
'onmqtt LogMessage
'wlog "MQTT connecting"
'wlog mqtt.setup("mqtt.cheerlights.com",1)
'wlog mqtt.connect("", "")
'wlog mqtt.subscribe("colour")
'
'wlog "connection : ";MQTT.Connected()
'
'wait
'
'LogMessage:
'Message$ = mqtt.message$
'wlog Message$
'return

[cicciocb]

Try to use mqtt:// instead of mqtts://

Just tested on the web simulator and both programs below work well :

Code: [Local Link Removed for Guests]

pause 1000
' MQTT SSL test program
' Using mosquitto test server
onmqtt mqtt_msg
wlog mqtt.setup("mqtt://test.mosquitto.org",1)
wlog mqtt.connect("","") ' No login / pass required
wlog mqtt.subscribe("/AnnexTest") ' subscribe to the topic /AnnexTest
wlog "connection : ";MQTT.Connected()


for z = 1 to 5
  ' send messages to the topic /AnnexTest
  wlog mqtt.publish("/AnnexTest", "Annex"+str$(z))
  pause 500
next z

wait

mqtt_msg:
wlog "TOPIC  : "; mqtt.topic$
wlog "MESSAGE: "; mqtt.message$
return

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

' This should return the name of a colour from the Cheerlights server
wlog bas.resetreason ' 12 - Software reset CPU
wlog "***"
onmqtt LogMessage
wlog "MQTT connecting"
wlog mqtt.setup("mqtt://mqtt.cheerlights.com",1)
wlog mqtt.connect("", "")
wlog mqtt.subscribe("colour")

wlog "connection : ";MQTT.Connected()

wait

LogMessage:
Message$ = mqtt.message$
wlog Message$
return