The other nice part of `hledger` is the web UI (`hledger-web`), which is handy for checking out your transactions.

Looks really cool! Can I use it totally locally on a non-internet connected VLAN? Or do I need to use an app / cloud service?

Apple | 3D UI Frameworks Engineer | Full-time | On-site

The Technology Development Group (TDG) is looking for an 3D UI Framework Engineer to help build frameworks that will drive the next generation of interactive experiences for our platform.

We work in the AR/VR space. Positions available in Santa Clara Valley and Boulder, CO.

https://jobs.apple.com/en-us/details/200167625/3d-ui-framewo...

I love HomeAssistant, and use it to power my whole house. I automate most lights, my whole house audio setup, my security system, and more. I highly recommend it.

I recently wrote about how to do a declarative model for automations, which I use throughout the house: http://peterhajas.com/blog/declarative_home_automation.html

I’ve used 4K 39”/40” televisions (originally 3, now 1) for the past 8 years. I find that the panels look great, and they give me a huge working area. They’re also really reasonable - $250 - $350 for a good TV. They last a while.

Smaller 4K/5K panels (with more pixels per inch) are nice, but I never understood the push for density. I’d rather have more workspace with lower density.

Higher PPI makes things clearer and easier to read for me.

Hi-DPI panels gives you more choice for UI density.

I use NodeRed a lot for my smart home and local network as glue between different pieces. It works really well for “hit this API, apply this transformation, and then return it when I send you a GET at /something” or “listen for MQTT, get this key out of the message, and rebroadcast it”.

Do you use it on it's own, or with other automation software like home assistant or openhab?

I have similar process setup as original poster, instead of MQTT, I use home assistant Node-RED pallete which exposes all home assistant entities to nodered.

Node-RED automation is SO much better than home assistant automation or Huggins, ability to deploy modified flows when nodes on same flow are kept running is AMAZING!, makes dev cycle so much faster.

I use home assistant's builtin zwave, homekit controller, homekit bridge, Sonos, and InfluxDB, everything else is commented out. It's all running on used $50 HP Prodesk G2 with Ubuntu server with HASSOS in VM, VS.Code server in docker. Uses about 7 watts/hr.

I use it with HomeAssistant. I like HA automations for many things, but I really prefer NodeRed for gluing together systems or sketching things.

I use Node-RED to do home automation with Home Assistant, and I like it. As others have mentioned, it's easier to do than YAML automations - especially because you can throw in a JS "function node" when you need to just write a few lines.

Something I wish they'd get to is looping support. It's unusual that you need a third party extension to do a for-loop. Fingers crossed this can make its way into NR proper in a future release.

> Something I wish they'd get to is looping support. It's unusual that you need a third party extension to do a for-loop.

Out of curiosity, what do you need a for loop for?

I've so far only created a single loop: it randomly changes the colors of a couple lights in my office.

This uses a delay component and a switch (controllable from Home Assistant) called "office_lights_cycle". The switch both initially triggers and breaks the loop. When executed, it picks a random color for one light, sets the other to a complementary hue 90° away, sets them with a transition time of 300s (very slow fade), and the loop triggers again a few minutes later.

https://i.imgur.com/XM53DO4.png

Instead of looping through things I split items, process in parallel, and then join.

I’m curious - how do you split items up and process them in parallel?

A map call?

Not actually parallel, but I presume that's what they meant.

How are you integrating Node-RED into Home Assistant? How does Home Assistant talk to Node-RED? I recently set up Home Assistant (love it) and an MQTT broker for some sensors and I can think of many ways in which Node-RED could also be involved but don't know which is considered canonical.

node-red-contrib-home-assistant-websocket is considered the canonical, it's the one built into the community Node-Red plugin. https://github.com/hassio-addons/addon-node-red

And if you are not using supervisor, for the other side of the pipe, companion component hass-node-red - https://github.com/zachowj/hass-node-red.

Not GP, but I just expose node-red flows via http and hit those from hass. There's probably a more elegant way, but having them communicate via http also lets me hit the flows via flic buttons or Apple Shortcuts without having to go through hass (which I never let see the public internet).

If you're using the hassOS version of homeassistant, you can activate plugins, and one of those is Node-RED with the necessary integrations.

Using Haas Core unfortunately.

Are we sure that this isn’t generational values changing? I wouldn’t be surprised if there was a moral change associated with generation / upbringing more than age.

One thing I wish some of these browser plugins did is cleanly compose with the existing “is the browser in dark mode?” CSS selector. Every one I’ve tried will clobber colors on sites that have supported dark mode. I haven’t checked if Dark Reader works differently.

It supports marking a domain as an exception to its own dark mode. Quite nice, actually :)

How does licensing work? Does this give me a file I put on my machine? I have my dotfiles checked into git, so I'd rather not commit the license publicly.

You get a license code that you paste into an editor with TabNine installed. The autocompletion engine sees it and completes the registration. Not sure where it gets saved ultimately.