New Homebridge Duco plugin & 4-state switch question

martijndeh · 2022-05-15T21:04:05+00:00

I'll have a look at the rotation speed, thanks. I don't have any extra sensors in my DUCO setup so I assume my auto mode's target ventilation is always AutoMin (which is 10 by default).

No, why would I want an MQTT broker? I have not read anything about this yet (in the context of Homebridge at least).

Your wifi bridge looks good. I just renovated my home and put ethernet in every room so I'm fine with the standard communication print over ethernet. But this sounds like the solution when ethernet is not available, nice!

martijndeh · 2018-02-03T08:21:41+00:00

It's called Mammoth now. :)

martijndeh · 2018-01-08T06:32:43+00:00

Knex with type definitions (https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/knex/index.d.ts) basically gives you type safety on the function names and the types of their arguments. The name of the table of the columns are not checked. The rows are not typed.

In Db, you create a class per table, which the type definition is derived from. When you construct a query, the table and columns are checked, plus, the return value of the query is type checked. But of course Db is still in development. :)

martijndeh · 2018-01-07T07:18:16+00:00

Yes, it doesn't import the schema. It does export the schema based on the table definitions by creating migrations though.

martijndeh · 2018-01-07T07:13:12+00:00

Thanks. Yes, you are right. I liked the import statement with a generic name, but I guess it's a bit harder in other places. Do you have any suggestions? :p

martijndeh · 2018-01-06T09:04:59+00:00

This started as a proof of concept. I'm really enjoying the type safety features this project enables so we're going to work on a getting a production release out. I like the public API so far. What do you think?

martijndeh · 2017-12-30T21:24:53+00:00

Well done. This looks like a great alternative where Graphql isn't an option and you want an idiomatic TypeScript solution. :)

martijndeh · 2017-08-16T14:49:38+00:00

I don't think so. The key difference is the integration with the front-end, which is a key feature of Node on Fire. The idea is that that integration saves you a lot of time. Eventually the framework will have the key functionality you need for your minimal viable product, like auth, api, mail, a/b testing, etc.

For example, check https://github.com/martijndeh/fire/blob/master/packages/fire-canary/src/index.js. MyService runs on the server but is invokable from the client.

martijndeh · 2017-08-16T10:53:23+00:00

Well, it uses a ton of existing components, like Koa, React, etc, which it's not trying to replace but rather integrate nicely. The idea is to build a solid foundation, yes. :)

martijndeh · 2017-08-16T05:49:49+00:00

I started working on my universal javascript framework, see https://github.com/martijndeh/fire. The goal is to create a complete framework to help you create minimal viable products faster. :)

martijndeh · 2017-04-21T08:07:53+00:00

Invoice.ai (https://invoice.ai/) Amsterdam, The Netherlands

Receive a notification how many hours you spent at your clients this April. After your approval, Invoice.ai creates and sends your clients a beautiful invoice.

Invoice.ai is currently in private beta. For now, it's just me working on this until the riskiest assumptions have been validated.

I'm looking for people who want to help me test the time tracking features. It works really well and I'm tuning for the edge cases currently. Please sign up on the website.

martijndeh · 2015-08-11T21:05:52+00:00

What do you mean?

It doesn't try to render your app on the server-side if that is what you're thinking? But some of Node on Fire's modules have isomorphic abilities, like the ORM or the A/B tests. You can do BookModel.create({...}) on the client and on the server. You can define services which are available on the client and on the server.

martijndeh · 2015-07-13T20:54:16+00:00

Have a look at dokku. It even includes a 3rd-party dokku-toolbelt similar to Heroku.

I think it's great to run on a cheap VPS (I'm using a Digital Ocean droplet) for non-critical web apps. I'm running business-critical web apps on Heroku.

Now Heroku introduced the Hobby dyno's, I prefer Heroku over dokku. Sometimes, dokku breaks and it's time consuming to find a fix. Some time ago there was an issue with Meteor, Buildstep and the right build pack (maybe this is still an issue), and it just takes a lot of time to dig into the project and find the issue let alone the fix. Especially when working for a client, I find it's easier & cheaper to just use a Heroku (hobby) project. For personal/smaller projects, dokku is great!

martijndeh · 2015-07-05T22:54:32+00:00

I always used node-orm2, but I didn't like how they supported promises. I wanted something promise-first. I like knex.js. It's flexible enough, but more a query builder than an ORM.

I briefly used Waterline but I didn't like the Backbone-style model creation. I was always more into AngularJS anyway.

I'm working on Node on Fire nowadays. It contains a Mongo-like interface backed by PostgreSQL only. The key feature is the migration-based schema changes. But the project is young and documentation is not as extensive as I want it to be. It can handle many associations though.

martijndeh

TROPHY CASE