BREAKING CHANGE: in JSON responses, the button status list is now an array instead of an object. This affects HTTP GET /buttons responses and the deviceStates WebSocket event body. Using an object was unnecessarily complicated and based on a bad assumption.
See documentation for details.
Default mapping fixed: The "player start" buttons are now buttons 49 and 50 on device 1 (instead of 0 and 1). I moved their button numbers to the top of cal1.xml. The XML mapping files are read in reverse order to maintain compatibility with the 100 Button Jam sample Unity project, so moving player start numbers to the top puts them at the end of the list, where the server expects them.
The test page now tries to reconnect every 10s in HTTP polling mode if a poll fails.