Hi all, 

I complained to odoo about this problem and eventually got through to the project manager that was overseeing the development of the new IoT box. He looked into the problem and eventually came back to say that the problem is probably caused by the signal from the printer to the draw not being long enough. 

He said that they couldn't reproduce the issue as they have their servers and testing all on the same internal network so there was no latency caused by the server being out on the internet and the POS locally in the store. 

We coded the double click for Mike's solution & it did solve the problem nicely at the time. The odoo project manager said they would not be updating the postbox code as they were developing the new IOTbox. I'm not sure they did anything different for the IOTBox coding. 
​
Something else you need to be aware of is that the posbox won't work over https. So if your domain uses https: you have to add exceptions into your apache files. This is also still the case with the new IoTbox and the pos. It's fine for other IoT devices but the pos still needs HTTP:  !!

If anyone needs help solving these issues then you can email me at steve@betterbusinessresults.com