Error: environment variable not found #106
Comments
|
|
I'm working on it, I think I got some deps wrong, will update as soon as I make progress. |
|
Make sure to have a direct dependency on |
|
ok finally, got it working # didnt touched things above from the template in the Cargo.toml file
[dependencies]
log = { version = "0.4.17", default-features = false }
embassy-futures = "0.1" #use embassy
async-io = { version = "=1.12" } #use async-io
esp-idf-sys = { version = "0.33", optional = true, default-features = false, features = [
"native",
] }
esp-idf-hal = { version = "0.41", optional = true, features = [
"embassy-sync",
"critical-section",
] }
esp-idf-svc = { version = "0.46", optional = true, features = [
"embassy-time-driver",
] }
embedded-svc = { version = "0.25", optional = true }
rs-matter = { path = "../rs-matter/rs-matter", default-features = false, features = [
"esp-idf", # use needed features
] }
[target.'cfg(target_os = "espidf")'.dev-dependencies]
esp-idf-sys = { version = "0.33", default-features = false, features = [
"binstart",
] }
[build-dependencies]
embuild = "0.31.2"
# For compatibility with ESP IDF
[patch.crates-io] # Patch crates
polling = { git = "https://github.com/esp-rs-compat/polling" }
socket2 = { git = "https://github.com/esp-rs-compat/socket2" }only use sadly I have an out of memory error |
|
|
Oh and one more thing: since you've created a separate binary crate - put in your ... and delete the existing ones. You really need opt-level = 3 for all the memory optimizations to kick-in. And by default, the |
|
thanks a lot, changed opt-level and after some testing, set it to but the search is going on 🙈 |
|
You are hitting #100. To workaround it, temporarily downgrade to esp idf v4.4. |
|
After that, if you are using a Google Controller, you'll likely hit #102 as well, which we are analyzing right now. |
|
Ok, thanks. |
|
@Zercerium Can you try if #107 fixes the provisioning issue for you? Note that provisioning might still generate an error at the end (device not found - that's an old issue because we don't properly implement true subscriptions) but the device should afterwards be nevertheless visible. |
|
ofc The Alexa App says: "Something gone wrong, an unexpected error occurred, please try again later" (Translated) following the log, say if u need more infos Log |
|
OK the culprit is this one: ... which means it fails just before it can establish a valid CASE session, and this is very different from the problem I fixed in my branch Can you open a new issue for this? Something like "Provisioning with Alexa/Echo Hub fails with Invalid Cert error during the Case3 step". I still don't have an Echo device, but I'll order soon. Perhaps other folks can shed some light (@kedars?). |
|
yeah, opened an issue for it. #109 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cargo generate esp-rs/esp-idf-template cargoexport MCU=esp32; export CARGO_TARGET_XTENSA_ESP32_ESPIDF_LINKER=ldproxy; export RUSTFLAGS="-C default-linker-libraries"; export WIFI_SSID=ssid;export WIFI_PASS=pass; cargo build --no-default-features --target xtensa-esp32-espidf -Zbuild-std=std,panic_abortexpected: successful build
outcome:
error: failed to run custom build command for rs-matter v0.1.1Error: environment variable not foundquite not sure which env variable is not set
The text was updated successfully, but these errors were encountered: