olavt

Are the gym_soccer environments supposed to be registered automatically by gym by doing the "pip install -e ." command, or are there any manual steps required after that?

It would certainly help to have a timestamp at the node level.

Not sure, but I don't think something crashed. It's more some kind of issue related to inconsistencies in reachability status of the nodes. Either at the Matter SDK level, or...

I did the same upgrade on another installation today with the same results. Here's the complete log: 2024-05-10 06:30:51.304 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging... 2024-05-10 06:30:51.305 (MainThread) INFO [matter_server.server.stack]...

The device was working 100% fine just before the upgrade. It was sending attribute updates every 2.5 seconds. Stopped the running Python Matter Server, started the new version and got...

I re-testet today by upgrading from 5.10 to 6.0.1 and I could not reproduce the issue.

I upgraded to 6.1.2 and experienced the issue with device becoming unavailable.

It could be related to not specifying these options when starting Python Matter Server: --storage-path /data --paa-root-cert-dir /data/credentials I thought it would use /data per default.

Hm, it was interviewed quite recently: "date_commissioned": "2024-02-20T23:11:43.174090", "last_interview": "2024-02-22T15:38:30.664012", "interview_version": 6,

I re-tested today. Running Python Matter Server using Docker on a freshly formatted Raspberry Pi 4 and a clean data directory. Added two Matter over Thread devices. This is the...