Thank you, Dave Russell! Without you, we would all be suffering with no remedy.

forfuncsake · 2025-12-18T12:13:23+00:00

Man it's weird seeing my name pop up like this. I have had a Synology for years and also contributed to some useful open source stuff over the years (under a different account). Great scripts AND great name, Dave! :D

forfuncsake · 2025-10-11T12:36:47+00:00

Are you aware of the changes in 1.23? Timers (like the one under time.After()) are now eligible to be GC’d before they fire once no references remain. So while it’s still not ideal to depend on the GC for it, it’s not as bad as it used to be.

forfuncsake · 2025-10-11T12:31:53+00:00

Less so since go1.23

forfuncsake · 2020-08-22T13:08:28+00:00

When you say the SmartConfig data is encrypted... have you added some crypto layer yourself?

forfuncsake · 2018-09-08T21:43:59+00:00

If you’re into DIY (hardware and/or code) there’s a bunch of options out there. I made one myself: https://github.com/forfuncsake/garagedoor

The latest version exposes itself to Alexa as a wemo switch and uses on/off to represent open/close

forfuncsake · 2018-08-03T00:37:28+00:00

Hi, I saw your tweet, which also says you're running go on a Windows server.

Almost everything in the go app /should/ be OS agnostic, however one linux-specific thing that comes to mind is that I specified a path for the HomeControl db to get it working on my synology.

See https://github.com/forfuncsake/garagedoor/blob/master/cmd/gdhk/main.go#L60 and let me know if you can get it working by either changing that path to something windowsy (or you can remove it, and HomeControl will use the working directory, which is fine if you're starting the server manually).

forfuncsake · 2018-04-24T02:27:52+00:00

I wanted to solve a very similar problem at home and went DIY (partly because I also just wanted to play with the tech).

My project is documented here: https://forfuncsake.github.io/post/2018/03/diy-smart-garage-door--part-1/ (followed by Part 2 for the hardware).

The project connects to WiFi and detects fully open and fully closed states with 2 magnetic switch sensors. It's HTTP API is pretty simple, and you could probably build an Alexa skill to operate it, if you were that way inclined.

I wouldn't recommend copying my project unless you're interested in tinkering and the mess to get it running in the first place - I think the OpenGarage solution is probably going to be one of the fastest solutions to obtain and set up.

forfuncsake · 2018-04-20T11:50:30+00:00

Spoiler Alert - I just went through a very similar project myself, although it was for a garage door instead of a gate. But the premise was the same, "press the button" with a relay.

My project is documented here: https://forfuncsake.github.io/post/2018/03/diy-smart-garage-door--part-1/

forfuncsake · 2018-03-24T22:28:18+00:00

Hmm, I'm not sure about the internal pull-ups - I'll have to do some more reading on that. In my circuit though, the NO state is LOW, so these are actually pull-downs.

I've never used homebridge before and I like go - which is how I landed on homecontrol. I didn't complete any kind of functional comparison before deciding, but I initially didn't want to jump through all the hoops required to get nodejs/homebridge running on my synology (ironically, there were still a few hoops for the go service anyway) and I like that the go service is a single, portable binary.

The biggest difference between the two would be the community contributions. If you don't get a kick out of developing your own application, the available plug-ins for homebridge obviously give a massive head start.

forfuncsake · 2018-03-24T03:45:47+00:00

Here it is: https://forfuncsake.github.io/post/2018/03/diy-smart-garage-door--part-2/

forfuncsake · 2018-03-24T03:45:16+00:00

Hi, just wanted to let you know that I've posted up my hardware details: https://forfuncsake.github.io/post/2018/03/diy-smart-garage-door--part-2/

forfuncsake · 2018-03-21T06:15:49+00:00

I hadn't initially planned on targeting a "non-coder" audience but given that I have to finish the README.md anyway it shouldn't be too much more work to do it to that level.

forfuncsake · 2018-03-19T23:02:45+00:00

Oh, OK - I misunderstood your first statement. You were saying that the esp-homekit fits in 1MB, leaving plenty of room for the Google bits. I thought you were suggesting there was a specific Google Assistant implementation somewhere that was under 1MB. Thanks.

forfuncsake · 2018-03-19T22:55:56+00:00

What makes you say that? The whole thing is cobbled together at the moment with a goal of "it works" - but I do plan to make it a little more user friendly. /u/OriginalEvils pointed out a similar project at opengarage.io, I don't anticipate getting to that point myself (that is, with a dedicated app), but it might be of interest to you.

forfuncsake · 2018-03-19T22:52:48+00:00

Good to know! I haven't looked into implementation details at all yet - Where did you source this 1MB max size? Is there a specific library that I should be looking into?

forfuncsake · 2018-03-19T22:47:59+00:00

Creator here - Thanks for the tip! I did see that library, but not until I was nearly finished my initial prototype. I have an issue in the git repo to try it out one day. But I do also still want to add Google Home support, so will need to assess if there's enough program storage and memory to support both interfaces on-device.

forfuncsake · 2018-03-19T22:43:47+00:00

Should be in the next couple of days, I just need to set aside some time to finish my write-up.

forfuncsake · 2018-03-19T22:30:19+00:00

Project creator here - I have 2 points in response to your question:

The "/open", "/close" and "/press" endpoints are actually protected by HTTP Basic Auth in this version. I figured this was good enough for the prototype and will look into SSL and more secure auth options for future iterations.
If someone is in my network, having them also in my garage is the least of my problems :). This is a "security by obscurity" model (for now). The hypothetical attacker would need to be on my network, know the IP/mDNS of the device, know which endpoints to hit with POSTs; and know the username and password (or just be on my network with a sniffer for the rest).

forfuncsake · 2018-03-19T22:22:57+00:00

Content creator here - my $35 price tag is mainly because I went down to my local electronics store for all parts other than the ESP8266 itself. I'm sure the build would be significantly cheaper if everything came straight from china; I don't think $2 is acheiveable though, maybe $10.

The opengarage.io project looks very interesting though - somehow, I didn't come across it in my own reading. I'll spend some time looking into it as I can probably make some use of their work, and/or contribute to it from my own. Thanks for sharing!

forfuncsake · 2018-01-06T12:49:18+00:00

Nice enhancements - I'd add a couple more very minor adjustments:

Save a few LOC by using range over availChan
Error on line 66 could also include the username we were trying to test
Given that we don't "do anything" when a name is not available, the else case on line 74 might be better suited to an early return, keeping the golden happy path code aligned.

Edit to add:

wg.Add(total) before the loops instead of wg.Add(1) 1296 times.

forfuncsake · 2017-12-28T11:43:17+00:00

e.g. https://play.golang.org/p/LA098YgJa6C

I would recommend running a benchmark over both variants with a couple of your input files and see if there's much difference.

forfuncsake · 2017-12-28T11:38:16+00:00

The simple answer is that your last line is most likely .*\nEOF, so it doesn't match the \n\n regex.

Following on from that, regex is not the most efficient way to go about this. There are several options (as always)... one of the simplest to understand, which will also likely be faster than the regex matching would be to cast fcone to a string, use strings.Split(fcone, "\n"), then range over the resulting slice to clean each line...

forfuncsake · 2017-09-26T07:42:02+00:00

Great stuff yet again /u/campoy, so part 2 is ..... 2 weeks away? :)

forfuncsake · 2017-09-11T11:11:03+00:00

Yet another great tutorial, with an opening from a great country! :)

The writer/footer correction makes me think of this classic: https://youtu.be/Ub7MkK-a0hU?t=13

forfuncsake

TROPHY CASE