Update training to latest releases

[SergioGasquez]

No description provided.

[Vollbrecht]

Thanks for working on this!

A couple of notes. In the book we still use the static uuid in the mqtt examples. In my testing it seams that all major broker provider somehow now blocking this uuid ;D i think just to many peole run the examples ;D If i change the topic creation to not using the uuid it works on hivemq / mosquitto / emqx. So if either the mqtt example could generate a uuid in a build.rs and write it into the cfg file or the host-client is maybe something that we could add to mitigate that problem.

[Vollbrecht]

Two more things on the to-do list.

• in every .cargo/config.toml -> change idf version to ESP_IDF_VERSION = { value = "tag:v5.2.2" } and remove the panic_imidate_abort for a better .unwrap/() experience.

• in every Cargo.toml add a [[bin]] section such that rust-analyzer doesn't topple over building test's like the following.

[[bin]]
name = "hardware-check"
harness = false # We can't use the default rust libtest harness for a crosscompile target

[SergioGasquez]

Thanks for the input @Vollbrecht! I think I addressed all the review comments but the UUID one, which can be implemented in a following PR

[Vollbrecht]

Thanks for the input @Vollbrecht! I think I addressed all the review comments but the UUID one, which can be implemented in a following PR

Yeah the uuid thing was quite strange ;D can you actually communicate using that hard coded UUID through a public broker with the host-client and the esp? It never worked for me till i changed it.

[Vollbrecht]

LGTM! Thanks.

[Vollbrecht]

also one little thing, could you co-author your first commit with juliankrieger julian.krieger@me.com as he did also some of the changes the same way but for 0.48 so we can close #243

[SergioGasquez]

can you actually communicate using that hard coded UUID through a public broker with the host-client and the esp?

Didn't tried with a public broker, I did in the past, and it worked, but not recently.