Forceu
Grocycode stockentry barcode not processed
So I've attached a labelwriter to my Grocy instance to print datamatrix-codes with stockentry (due date). In the changelog and code I see that this should be processed in Barcode Buddy but it isn't. It's being recognized as Unknown Barcode, while Grocy itself handles it fine:
Not sure where to search for, running 1.8.1.4 in Docker
Thank you for raising the issue. Are you using a physical barcode scanner? I just saw that the default script included in Barcode Buddy does not transmit colons, which is probably the reason why it is not recognised. Does it work if you paste the content of the barcode into the entry field on the Barcode Buddy main page (by clicking on the "add barcode" button)?
Alright, thanks! In case please update your grabber file to one of the changed files in 666dfb7. :)
Thanks, that was a quick one. Any change you push a new release as well? I'm using the Docker-version of BB and I see it relies on versions. :-)
The change should be automatically applied to the latest-dev image, if not let me know!
@Forceu ,
Thank you for your work on this amazing project. I am new to Grocy and working on using BBuddy to automate my Grocy inventory operations. I've got a physical barcode scanner attached to an Android tablet and I am having the exact same issue as described above. On the tablet I can confirm the GrocyCode scans correctly as grcy:p:380. When I scan via the app I get the error that a product can't be found for GRCYP380 and then allows me to add the barcode from the Unknown Barcodes menu. I have Barcode Buddy deployed with Docker Compose using the latest-dev image. I have looked in the docker container and changes described in the following Commit are indeed present. Anything I can do to troubleshoot?
@Forceu
Thank you for the quick response. To further test I sent some test payloads to the BarcodeBuddy API through Postman and those requests with the colon are being handled properly. I think this is specifically related to the Android app and is note in this Bug. You can likely close the issue here and I can add any detail in the android repo if needed. I am not much of a Java developer but I will have a look as well.