Hi,
have you been able to look into and fix the problem yet?
Now that many devices can be read out via Bluetooth, all that’s missing is a nice GUI for the values.
It would be ideal for boats and campers.
Hi Dirk,
I’m currently working on a new version that will allow the raw data to be included in the node output. I have also ported many tests from the Python library to this project. I hope to have everything ready for testing by the end of the week, and then I can proceed with the release.
The advantage of this approach is that I’ll be able to incorporate your raw data and the expected output into my automated tests. This way, I can test and fix any issues, ensuring that it won’t break again, as the functionality will be tested before each release.
@DirkW the new 1.3.1 is ready to test. It includes that new option. If the output is still wrong please turn it on and send me the full message output including the decryptedData. Even if this works it would be great if you can send this to me so that I can add it to the automated tests.
I have the new version and rebooted the GX device.
After a quick test, the values for Smart Battery Sense are now correct.
However, I don’t see any difference in the debug message whether I activate or deactivate the checkbox for decryptedData.
After rebooting again after changing the checkbox, I get the following message (I did not re-enter the key).
Hi Dirk,
The decrypted data is outside of the message payload—just see this picture. So, you need to change the setting in the debug node to see the whole object.
I have no idea why that issue with the credentialSecret happened, this is entirely outside of my component.
Besides that, it’s great to read that the parsing is now correct.
Any news from you?
Hi @DirkW
I thought that I answered you and that it was your turn to test the new version.
We can also have a direct chat, I’m just based in NZ, so we would need to align the time.
regrads
Konrad
Hi @konne
Okay, okay, as a non-native speaker, I must have misunderstood something…
New Zealand, I’d be happy to come by for testing.
regards
Dirk
I recently tried on v3.70~35 large but could not even get the node installed, it ran up cpu until it bugged out the installer. Some remain are visible in pallete manager stating MODUKE_NOT_FOUND. Can’t uninstall or reinstall.
I could use some help removing the failed node installation as well. No matter what I try, I cant figure out how to remove it’s remains.
@UpCycleElectric I’m happy to make a short meeting with you. RE 3.70 I will start test it with 3.70 as soon as this is release, but I will not test BETA versions.
Still I’m happy to have a look and check what is making the issues with 3.70.
Can you maybe share you email or send me a DM if possible and I will ping you to find a slot for a meeting.