Replies: 1 comment 1 reply
-
|
Could be. As we are still actively working on this branch, so this happens from time to time. More complex changes often require work from both Abasz and myself, so there are quite some moments when this happens. We try to be as clean as possible, making sure code always executes even when not complete, but in complex code like the PM5 emulator you can't see everything. Testing sometimes identifies a serious issue which requires quite some time to resolve (like we had last week, where CPU load went skyhigh on longer sessions), which easily could appear in a development branch as we completing our tests takes weeks. Once a week I do a clean install to check the installation procedure, but we can't keep testing all scenario's all the time. So please do not update on any development branch on a structural basis, as it can contain a lot of issues. Hence the warning that people should contact us before using a development branch. Found the cause of your MQTT issue, which is now fixed. Thanks for reporting it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I used new-ble-api until Commits on Apr 5, 2025 successful.
After that it is not possible for me to use new-ble-api.
Downgrade to 0.9.6-(in-development) works.
Even a fresh installation on raspi3 doesn't work.
Commands used are updateopenrowingmonitor.sh -b "new-ble-api"
and updateopenrowingmonitor.sh -b "0.9.6-(in-development)"
log.txt
config.txt
Beta Was this translation helpful? Give feedback.
All reactions