Hi everyone,
I’ve been working on a custom interface overlay all weekend and I am completely stumped. I’m trying to use a TamperMonkey script that hooks into the PixelBlaze web interface. The goal is to create an interactive dashboard that lets me trigger pattern changes, upload animations, and display dynamic information in real-time.
So far, the TamperMonkey script is working well — I’m able to inject UI elements and run WebSocket commands. However, I keep getting a persistent 404 error in the console:
nginx
CopyEdit
GET http://192.168.0.21/blockly/blockly.js net::ERR_ABORTED 404 (Not Found)
I’ve combed through the TamperMonkey script — there’s no reference to Blockly in the user code. I checked the HTML via DevTools and confirmed that the original PixelBlaze index
page has this line around line 179:
html
CopyEdit
<script src="blockly/blockly.js"></script>
But I haven’t found any subsequent JavaScript that actively uses Blockly methods (e.g. Blockly.inject()
), which makes me wonder:
Is Blockly still being used by the current firmware?
Or is this script tag legacy or vestigial?
I tried using TamperMonkey to remove or block the <script src="blockly/blockly.js">
tag, but the script still gets requested on load. It looks like it’s baked into the index
page itself, and editing the HTML from within DevTools isn’t persistent or effective.
So here’s what I’d love help with:
- Is Blockly still used by the PixelBlaze interface, or can it safely be removed/ignored?
- If it is needed, is there documentation or examples of what it’s doing?
- Is there a clean way to override or stub that script so it doesn’t throw 404s?
I’m not trying to modify the core PixelBlaze firmware — just overlay some tools on top of the existing interface without causing errors or collisions.
Any insight from folks who’ve dug into this would be hugely appreciated!
Thanks so much,
Ezra