u/TheTwelveYearOld

In the BIOS settings I changed graphics mode from hybrid to "dgpu" only. I can't power it on even when I hold the power button for 60 seconds with nothing plugged in. I've also tried powering on while connected to my monitor via USB-C (thunderbolt port on the left), and HDMI. When I just leave the device it seems to boot loop: show the rog logo, black screen with fans on, and repeat ~1 min later. Holding ESC or F2 doesn't do anything.

Model: Rog Zephyrus G16 GU605MY (2024), intel core ultra 185h and 4090 mobile.

In the BIOS settings I changed graphics mode from hybrid to "dgpu" only. I can't power it on even when I hold the power button for 60 seconds with nothing plugged in. I've also tried powering on while connected to my monitor via USB-C (thunderbolt port on the left), and HDMI. When I just leave the device it seems to boot loop: show the rog logo, black screen with fans on, and repeat ~1 min later.

Model: Rog Zephyrus G16 GU605MY (2024), intel core ultra 185h and 4090 mobile.

In the BIOS settings I changed graphics mode from hybrid to "dgpu" only. I can't power it on even when I hold the power button for 60 seconds with nothing plugged in. I've also tried powering on while connected to my monitor via USB-C (thunderbolt port on the left), and HDMI. When I just leave the device it seems to boot loop: show the rog logo, black screen with fans on, and repeat ~1 min later. Holding ESC or F2 doesn't do anything.

Model: Rog Zephyrus G16 GU605MY (2024), intel core ultra 185h and 4090 mobile.

I have the slzb ultima set to OTBR (openthread border router) and have it paired to home assistant as such. When I try adding the matter integration, it asks for an address: ws://localhost:5580/ws, I have no idea what to put in. For OTBR I did 192.168.1.60:8080. I looked this up and didn't find any answers.

I have the slzb ultima set to OTBR (openthread border router) and have it paired to home assistant as such. When I try adding the matter integration, it asks for an address: ws://localhost:5580/ws, I have no idea what to put in. For OTBR I did 192.168.1.60:8080. I looked this up and didn't find any answers.

We've had this rule for quite a while now, we don't want future demos of the game spoiled, including leaks: unreleased and unannounced game content. A video of a demo 6 concept is going around but unfortunately contains leaks, please don't post anything from it nor share links. We're all impatient for demo 6, good things come to those who wait.

I have an SLZB Ultima. Would all of the following work in Home assistant or the app?

• locking and unlocking
• fingerprints
• setting PINs

I have an SLZB Ultima. Would all of the following work in Home assistant or the app?

• locking and unlocking
• fingerprints
• setting PINs

I have a doorknob (Thorbolt MK1) which is has features locked to the app. I’m thinking of getting a Homepod mini (apparently a new one is coming out soon), and connecting my zigbee button which is paired to Home Assistant, via the Homekit Bridge integration. So when I press the button the door is locked or unlocked using a Homekit automation rather than an HA one. Thoughts?

I have a doorknob (Thorbolt MK1) which is has features locked to the app. I’m thinking of getting a Homepod mini (apparently a new one is coming out soon), and connecting my zigbee button which is paired to Home Assistant, via the Homekit Bridge integration. So when I press the button the door is locked or unlocked using a Homekit automation rather than an HA one. Thoughts?

On Home Assistant I successfully connected a home-kit only thread doorknob: Thorbolt MK1, but when I sync thread credentials to it, trying to lock and lock the doorknob remotely doesn't work. Everything else works: when I click identify the doorknob beeps 3 times, and beeps when I toggle muting. Locking and unlocking only works if I don't sync thread credentials (apparently its then only connected via bluetooth).

I tried restarting home assistant and unplugging my thread router (SLZB Ultima) for 30 seconds, and I still have the issue, when I did I watched the doorknob go from unconnected to HA to connected.

On Home Assistant I successfully connected a home-kit only thread doorknob: Thorbolt MK1, but when I sync thread credentials to it, trying to lock and lock the doorknob remotely doesn't work. Everything else works: when I click identify the doorknob beeps 3 times, and beeps when I toggle muting. Locking and unlocking only works if I don't sync thread credentials (apparently its then only connected via bluetooth).

I tried restarting home assistant and unplugging my thread router (SLZB Ultima) for 30 seconds, and I still have the issue, when I did I watched the doorknob go from unconnected to HA to connected.

On Home Assistant I successfully connected a home-kit only thread doorknob: Thorbolt MK1, but when I sync thread credentials to it, trying to lock and lock the doorknob remotely doesn't work. Everything else works: when I click identify the doorknob beeps 3 times, and beeps when I toggle muting. Locking and unlocking only works if I don't sync thread credentials (apparently its then only connected via bluetooth).

I tried restarting home assistant and unplugging my thread router (SLZB Ultima) for 30 seconds, and I still have the issue, when I did I watched the doorknob go from unconnected to HA to connected.

I have no idea what's causing the error / why my darwin build is trying to get libdrm. --show-trace output:

error:
       … while calling the 'derivationStrict' builtin
         at «nix-internal»/derivation-internal.nix:37:12:
           36|
           37|   strict = derivationStrict drvAttrs;
             |            ^
           38|

       … while evaluating derivation 'darwin-system-26.11.15abb8c'
         whose name attribute is located at «github:NixOS/nixpkgs/b7c2ada94fe99c15b0dbcf4d11fd7850b957a436?narHash=sha256-IItrdb7Puk05RqOBWZYFC5X6Wl1sJmCfh5MWVHw5iMM%3D»/pkgs/stdenv/generic/make-derivation.nix:651:11

       … while evaluating attribute 'activationScript' of derivation 'darwin-system-26.11.15abb8c'
         at «github:nix-darwin/nix-darwin/15abb8c98f336cd8bd840d71059adebabe60bf04?narHash=sha256-0tLW8Ff5yt8AH97jw4ZpFJ0OCJ122zIlgWGDmOfU/VU%3D»/modules/system/default.nix:89:7:
           88|
           89|       activationScript = cfg.activationScripts.script.text;
             |       ^
           90|

       … while evaluating the option `system.activationScripts.script.text':

       … while evaluating definitions from `/nix/store/21f6lm3b151nxsniikgsjlvid75vdi67-source/modules/system/activation-scripts.nix':

       … while evaluating the option `system.activationScripts.applications.text':

       … while evaluating definitions from `/nix/store/21f6lm3b151nxsniikgsjlvid75vdi67-source/modules/system/applications.nix':

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: Refusing to evaluate package 'libdrm-2.4.134' in /nix/store/1dffznc7fgw6xnzssy1h4waxz63i11qa-source/pkgs/by-name/li/libdrm/package.nix:69 because it is not available on the requested hostPlatform:
         hostPlatform.system = "aarch64-darwin"
         package.meta.platforms = [
           "x86_64-linux"
           "aarch64-linux"
           "i686-cygwin"
           "x86_64-cygwin"
           "i686-freebsd"
           "x86_64-freebsd"
           "aarch64-freebsd"
           "x86_64-solaris"
           "arc-linux"
           "armv5tel-linux"
           "armv6l-linux"
           "armv7a-linux"
           "armv7l-linux"
           "i686-linux"
           "loongarch64-linux"
           "m68k-linux"
           "sh4-linux"
           "microblaze-linux"
           "microblazeel-linux"
           "mips-linux"
           "mips64-linux"
           "mips64el-linux"
           "mipsel-linux"
           "powerpc-linux"
           "powerpc64-linux"
           "powerpc64le-linux"
           "riscv32-linux"
           "riscv64-linux"
           "s390-linux"
           "s390x-linux"
           "aarch64-netbsd"
           "armv6l-netbsd"
           "armv7a-netbsd"
           "armv7l-netbsd"
           "i686-netbsd"
           "m68k-netbsd"
           "mipsel-netbsd"
           "powerpc-netbsd"
           "riscv32-netbsd"
           "riscv64-netbsd"
           "x86_64-netbsd"
           "i686-openbsd"
           "x86_64-openbsd"
           "x86_64-redox"
         ]
         package.meta.badPlatforms = [ ]

       a) To temporarily allow packages that are unsupported for this system, you can use an environment variable
          for a single invocation of the nix tools.

            $ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1

          Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,
                then pass `--impure` in order to allow use of environment variables.

       b) For `nixos-rebuild` you can set
         { nixpkgs.config.allowUnsupportedSystem = true; }
       in configuration.nix to override this.

       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
         { allowUnsupportedSystem = true; }
       to ~/.config/nixpkgs/config.nix.
┏━ 1 Errors:
 ⋮
┃            "s390-linux"
┃            "s390x-linux"
┃            "aarch64-netbsd"
┃            "armv6l-netbsd"
┃            "armv7a-netbsd"
┃            "armv7l-netbsd"
┃            "i686-netbsd"
┃            "m68k-netbsd"
┃            "mipsel-netbsd"
┃            "powerpc-netbsd"
┃            "riscv32-netbsd"
┃            "riscv64-netbsd"
┃            "x86_64-netbsd"
┃            "i686-openbsd"
┃            "x86_64-openbsd"
┃            "x86_64-redox"
┃          ]
┃          package.meta.badPlatforms = [ ]
┃
┃        a) To temporarily allow packages that are unsupported for this system, you can use an environment variable
┃           for a single invocation of the nix tools.
┃
┃             $ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1
┃
┃           Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,
┃                 then pass `--impure` in order to allow use of environment variables.
┏━ 1 Errors:
 ⋮
┃            "s390-linux"
┃            "s390x-linux"
┃            "aarch64-netbsd"
┃            "armv6l-netbsd"
┃            "armv7a-netbsd"
┃            "armv7l-netbsd"
┃            "i686-netbsd"
┃            "m68k-netbsd"
┃            "mipsel-netbsd"
┃            "powerpc-netbsd"
┃            "riscv32-netbsd"
┃            "riscv64-netbsd"
┃            "x86_64-netbsd"
┃            "i686-openbsd"
┃            "x86_64-openbsd"
┃            "x86_64-redox"
┃          ]
┃          package.meta.badPlatforms = [ ]
┃
┃        a) To temporarily allow packages that are unsupported for this system, you can use an environment variable
┃           for a single invocation of the nix tools.
┃
┃             $ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1
┃
┃           Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,
┃                 then pass `--impure` in order to allow use of environment variables.
┃
┃        b) For `nixos-rebuild` you can set
┃          { nixpkgs.config.allowUnsupportedSystem = true; }
┃        in configuration.nix to override this.
┃
┃        c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
┃          { allowUnsupportedSystem = true; }
┃        to ~/.config/nixpkgs/config.nix.
┣━━━
┗━ ∑ ⚠ Exited with 1 errors reported by nix at 17:54:06 after 2s
Error:
   0: Failed to build Darwin configuration
   1: Command exited with status ExitStatus(Exited(1))

Location:
   crates/nh-core/src/command.rs:1044

Right now ffmpeg fails to build (a PR already got pulled but anyway), I commented ffmpeg packages in my nix condiguration and it still failed to build showing ffmpeg.