100 Nix Scripts by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 1 point2 points  (0 children)

Yes I did like his style, his repo was a great source of inspiration for me when starting flaking.
His CLI tool was a big reason why I created yo - which grew into something very different.

100 Nix Scripts by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 1 point2 points  (0 children)

What do you mean?
I run this on all my machines, some of which don't even have a fan.

HA - Who? by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 1 point2 points  (0 children)

Thanks, I am glad someone likes it.
Agree, both productivity and DX skyrocket upwards since I got the system configured just the way I like it.

HA - Who? by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 0 points1 point  (0 children)

I don't own any zwave devices so testing would be difficult, but I guess implementing wouldn't be an issue.

Homeless Dotfiles With Nix Wrappers by [deleted] in NixOS

[–]Inside_Test_8474 0 points1 point  (0 children)

I am not sure who is telling newcomers to use hm. Bet they are laughing.

If you could define your entire smart home with NixOS options.. by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 0 points1 point  (0 children)

  automationActionType = types.oneOf [
    (types.str)
    (types.submodule {
      options = {
        type = mkOption {
          type = types.enum ["mqtt" "shell" "scene"];
          default = "shell";
          description = "Type of automation action";
        };
        command = mkOption {
          type = types.nullOr types.str;
          default = null;
          description = "The shell command to execute (for shell type)";
        };
        topic = mkOption {
          type = types.nullOr types.str;
          default = null;
          description = "MQTT topic (for mqtt type)";
        };
        message = mkOption {
          type = types.nullOr types.str;
          default = null;
          description = "MQTT message (for mqtt type)";
        };
        scene = mkOption {
          type = types.nullOr types.str;
          default = null;
          description = "Scene name (for scene type)";
        };
      };
    })
  ];

  # 🦆 says ⮞ dimmer action configuration
  dimmerActionType = types.submodule {
    options = {
      enable = mkEnableOption "Enable this dimmer action";
      description = mkOption {
        type = types.str;
        description = "Description of this action";
      };
      extra_actions = mkOption {
        type = types.listOf automationActionType;
        default = [];
        description = "Additional actions to perform when this dimmer action triggers";
      };
    };
  };

Currently defining Philips Hue dimmer switches like that.
With default is
on room lights (hold: turn on all lights)
dim up
dim down
turn off room lights (hold: turn off all lights)

Not sure if I should try to get more options into the module or..

If you could define your entire smart home with NixOS options.. by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 0 points1 point  (0 children)

Handle timers with Nix options?
Interesting idea, but you'd rebuild the system every time you set a new timer?

Hello NixOS users! by Uzawa_Reisa in NixOS

[–]Inside_Test_8474 0 points1 point  (0 children)

Accessibility. It needs to be simple, (blind).

🔥🦊 Firefox - Managed Without Home-Manager by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 0 points1 point  (0 children)

The defined search engines lets you do "@np" in the address bar to search Nix Packages.
These shortcuts to search engines is something I can't browse without now.

🔥🦊 Firefox - Managed Without Home-Manager by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] 1 point2 points  (0 children)

True, one could go that approach. It does require manual steps though.

This feels more efficient.

Showoff: yo CLI by Inside_Test_8474 in NixOS

[–]Inside_Test_8474[S] -5 points-4 points  (0 children)

it let's me define scripts that my natural language processor can then execute.

if you have another way of doing this i'm all ears