I'm Dr. Azzy
I live and work in the People's Republic of Cambridge, near Boston, MA. I test the web gateway and web development framework for a database software firm for a living. I'm in my late 20's. I own pinball machines, with all the maintenance that entails, and have made modifications to them as well. I also play pinball competitively.
I play (well, not so much anymore) Ragnarok Online, and wrote the AzzyAI homunculus and mercenary AI.
In addition to the Espruino, I own 2 Linortek Fargo units (these are microcontrollers with ethernet ports, that run a webserver which controls relays - nothing you couldn't do with an espruino, but wrapped up very nicely, with a decent web interface). I use one of them for lighting-control in my bedroom. I also have boatloads of other electronic parts, many used/pulls, and many of them manufactured before I was born.
My plans with Espruino include a remote monitoring system for a summer cottage, more advanced lighting control and environment monitoring in my apartment.
I'm not a real doctor (I'd be happy to write you a prescription - but it'll be on the back of a cocktail napkin, and it'll be for a cocktail);
Most recent activity
Is there ever any reason not to pretokenize?
I think the local tunnel and IFTTT approach is madness; in fact avoiding the use of anything that required an outside service other than Alexa itself (which doesn't require a hole in the firewall, since it initiates the connections) was a key design requirement for me...
You're communicating between a device in your house, the Echo, and another device in your house.... And you're going to go outside the house, then make a call back in from the outside internet through a hole you've poked in your firewall?!
- This adds points of failure (whatever means you use to get through the firewall, external service that could be shut down or made a pay-for service in the future at the whim of an external organization) which are out of your control.
- This adds a tunnel from the outside internet to your Espruino. This strikes me as very dangerous; I have no confidence that the Espruino HTTP server will hold up to an aggressive attack - I operate under the assumption that there exists an unknown vulnerability (probably several) by which a malformed request could execute arbitrary JS, and hence no Espruino should be exposed to incoming connections.
- Your IP address changes occasionally, meaning you need to either set up a domain name and have it autoupdate (which is often finicky) or keep changing the IP address every time it changes.
I don't have code for doing this on an Espruino, but what I do at my place is have a Raspberry Pi running this code:
The clock call is (as you might be able to guess) a call that goes straight to an Espruino based device without much of an API. The hardware is so twitchy on that thing that I'm afraid to dig around in there to connect to board and upload new code.
Note that the pong part of it (used to control my pingpong lights, and set them to one of 100 specific scenes, telling it the scene number as if it was the brightness of a Hue lightbulb) doesn't quite work currently.
Whole thing generally works well.
I was under the impression that the SK6812's are WS2812 clones (albeit with a varying number of channels - there are ones that just have cool and warm white, and ones that have RGBW ), and the timing of the control signal is close enough that most control schemes meant for WS2812 will work for SK6812 (is the 6805 the same electrically? I would assume it is, just with different package).
Man, I have had so little time to work on the fun kind of projects lately. I've got a bunch of SK6812 RGBW and WW/CW LEDs, but they've been sitting in a bin for months without being turned on.
Hm, that doesn't look bad - like, I can't see for sure due to the lighting, but you should have to really work at it to damage the traces under the solder mask - and i don't see any other signs of excessive heat (which is usually involved when people damage things while soldering) or scraping - the ways you can cause problems while soldering something are pretty much bridging two connections that shouldn't be bridged (could you have done this somewhere? maybe between Vcc and Gnd?), or getting the pads too hot for too long with a soldering iron that is set to too high of a temperature or isn't temperature controlled, or being rough with the soldering iron and scraping the solder mask off the top of a trace; it doesn't look like that happened anywhere here.
Find his address and mail him paper money
Oooh... mayhaps I should set one of these up before I next hit the casino!
If we're talking about very feature rich terminal programs - for physical serial ports, I use hTerm. It has a bit of a learning curve, but it lets you do almost anything you could imagine doing to a serial port.
I never use PuTTY except for connecting over the internet; I realize some people use it for local serial, but the featureset seems to be terribly sparse for that...
The ESP8266 in particular doesn't have as much space in the flash to save code to as it does RAM to store the code you have uploaded. So you can get into situations like yours, where your code fits in memory, but you can't save it because even compressed, there's not enough space in the flash for it.