South Walean hacker/maker/tinkerer/devbot, with too many projects on the go at any one time to complete any of them.
Most recent activity
(Going further off topic but I don't want to start something new)
I've had a look at the various pieces of code in EspruinoHub and the way it's dealing with the BLE boards. Do you think there would be any mileage in implementing an MQTT conduit between the IDE and a classic board over UART?
Brilliant! That's got it. I have a Puck in range but the battery is dead - better drop into Poundland and grab a stack of their cheapy ones!
BTW, slight topic change - is there a way to have a classic Espruino board plugged into the Pi and to code from my laptop? Just thinking about the whole Chrome Apps closure debacle; being able to plug into the little box on the shelf would be next best to a direct connection.
Yep, that's how it's wired. Fortunately all the pins needed line up - most of the pins are there for physical stability and I've got cut-off headers to support the Pixl.js (top right of the board) where the header goes mad :)
Whilst unable to get EspruinoHub to talk to my Pixl.js board over BLE (see here) I've been using this jig I literally threw together from things lying around the office/workshop/attic (they're all the same place). A scrap of (really horrible) stripboard, some pin headers and one of the most useful cheap boards I've ever found in the usual Chinese outlets - a tiny USB-to-UART board that cost pennies (I think I paid 65p each for them).
It looks horrible but works brilliantly :)
I took a look at
dmesg and there were low voltage warnings every time I refreshed the IDE. Replaced the USB cable with a much better quality one; the warnings have gone but there's no difference made to the problem at hand.
Yep, connecting straight to the Pi hosted version on port 1888. The console logs show everything working as you'd expect - lots of
Initialising lines, and no errors. Connects websockets to the Pi without issue.
I thought for a moment I'd identified something - there was a complaint about parsing JSON from the config - but there was junk in the local storage. Clearing that out got rid of that error but still no luck getting connected. I also connected to the Pi through a Chrome incognito window to make sure that there was nothing else knocking around that could've had an impact (I once had issues with the LastPass extension on another web-based IDE - that caught me out) but there was no difference.
Checked mosquitto is running correctly - it is, and NodeRED can publish and subscribe quite happily to it. Everything looks like it should be working, but no dice :(
I've replaced my office Pi 2 with a Pi 3B+, partly so that I can use it and EspruinoHub to deal with my Puck and Pixl devices. I had it working with a Pi Zero W some time back, but that board has been used in a project since then. My problem is this - the backend can see BLE devices, and continues to see the devices (I've got it running in a terminal at the moment) but the WebIDE installed alongside won't acknowledge them and I can't connect to anything. So far I've...
- rattled through all the repos, running
npm install at every level, hoping that something will spark it up
./start.sh as both standard and root user
- installed the system service
- deleted everything and tried again
Still no luck. Any advice?
No need, I've just found what the problem was (while looking for the log messages). The Offline Mode was, somehow, switched on (and I don't know how or why). Switching that off did the trick.
Maybe being in Offline Mode could be a bit more visible (something in the title bar perhaps) - or, failing that, just add this experience to the knowledge base :)