Skip to content
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

Trigger firmware update via MQTT. (ESP Only) #953

Merged
merged 1 commit into from
May 23, 2021

Conversation

h2zero
Copy link
Collaborator

@h2zero h2zero commented May 21, 2021

If enabled in user_config.h this will trigger the OMG to update it's firmware from the link
provided in the MQTT message.

Example message:

{"version": "test ",
 "password": "OMGPASSWORD",
 "url": "https://github.com/1technophile/OpenMQTTGateway/releases/download/v0.9.6/esp32dev-ble-cont-firmware.bin"
}

If the firmware version in the message is not the same as the current OMG version the device will self update using the link in the url of the message.

@h2zero h2zero force-pushed the mqtt-https-update branch 3 times, most recently from 2fcfe7a to 21df632 Compare May 21, 2021 04:37
@1technophile 1technophile added this to the v0.9.7 milestone May 21, 2021
main/User_config.h Outdated Show resolved Hide resolved
main/main.ino Outdated Show resolved Hide resolved
@1technophile
Copy link
Owner

1technophile commented May 22, 2021

Would be nice to update the docs also:
https://docs.openmqttgateway.com/use/gateway.html

@1technophile
Copy link
Owner

I think defining 2 test environments (ESP32 & ESP8266) could help for the CI of this, here is an example:

[env:esp32dev-tls-test]

Or we may update these ones so that they cover also OTA

@h2zero
Copy link
Collaborator Author

h2zero commented May 22, 2021

Would be nice to update the docs also:
https://docs.openmqttgateway.com/use/gateway.html

Yes that can be done as well, once the process is finalized. I think adding a port parameter to the JSON message should be added and therefore would need to be documented as well.

@h2zero
Copy link
Collaborator Author

h2zero commented May 22, 2021

I think defining 2 test environments (ESP32 & ESP8266) could help for the CI of this, here is an example:

[env:esp32dev-tls-test]

Or we may update these ones so that they cover also OTA

Good plan, will do.

main/main.ino Outdated Show resolved Hide resolved
main/main.ino Outdated Show resolved Hide resolved
@h2zero h2zero force-pushed the mqtt-https-update branch 4 times, most recently from d7426c1 to c00aae9 Compare May 23, 2021 17:27
@h2zero h2zero marked this pull request as ready for review May 23, 2021 17:28
@h2zero h2zero changed the title Trigger firmware update via MQTT. Trigger firmware update via MQTT. (ESP Only) May 23, 2021
docs/use/gateway.md Outdated Show resolved Hide resolved
If enabled in user_config.h this will trigger the OMG to update it's firmware from the link
provided in the MQTT message.

Example message:
{\"version\":\"test\",\"password\":\"OMGPASSWORD\",\"url\":\"https://github.com/1technophile/OpenMQTTGateway/releases/download/v0.9.6/esp32dev-ble-cont-firmware.bin\"}

If the firmware version in the message is not the same as the current OMG version the device will self update using the link in the url of the message.
@1technophile 1technophile merged commit 295d39b into 1technophile:development May 23, 2021
@h2zero h2zero deleted the mqtt-https-update branch May 24, 2021 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants