Jura X3C

[mteichtahl]

Has anyone managed to get the stats characteristic to work on an X3C

[Nekonika]

I just want to add something here.
It seems that eather the documentation is wrong or the code is, as in the readme they say that if you read from "Statistics Command" after sending a command and waiting for 1.2s, the command was unsuccessfull if the first byte is 0x0E, but in the code they have a comment (and the code written for) if the first byte is 0x0E the command was processed successfull.
Or did I miss something here?

I am currently working on a similar approach in C# with a "Jura E8". As soon as I have had the time to tinker a bit myself, I could give you some code snippets. That is if you dont mind me having a different machine than you have 😉.

Maybe we could get in touch somewhere else, so that we don't have to spam the issues section on this repo 😉.

[mteichtahl]

I too am seeing this. Happy to connect separately Please note: My working hours may not be your working hours. Please do not feel obligated to reply outside of your normal work schedule!Sent on the go - please excuse mistakes On 6 Mar 2024, at 4:52 am, Nekonika ***@***.***> wrote: I just want to add something here. It seems that eather the documentation is wrong or the code is, as in the readme they say that if you read from "Statistics Command" after sending a command and waiting for 1.2s, the command was unsuccessfull if the first byte is 0x0E, but in the code they have a comment (and the code written for) if the first by is 0x0E the command was processed successfull. Or did I miss something here? I am currently working on a similar approach in C# with a "Jura E8". As soon as I have had the time to tinker a bit myself, I could give you some code snippets. That is if you dont mind me having a different machine than you have 😉. Maybe we could get in touch somewhere else, so that we don't have to spam the issues section on this repo 😉. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>