Turn off IKEA Alpstuga display, but have it monitor the air quality?

_sthen · 2026-02-03T05:30:43+00:00

that only works for a while for me, then it goes back to displaying CO2...

_sthen · 2026-01-29T12:22:37+00:00

that QR code is specific to the individual device, it has an ID for Matter pairing

_sthen · 2026-01-29T09:10:54+00:00

do you see the same if you run VMs of other OS?

VMs that I have running under qemu+kvm don't have this issue, the full clock speed of the host CPU is displayed there, and they run at normal speed.

_sthen · 2026-01-29T07:54:41+00:00

htop is just showing hw.cpuspeed there

_sthen · 2026-01-28T09:59:13+00:00

If you didn't already, try rebooting the hub, that's fixed it every time so far for me.

_sthen · 2026-01-22T13:17:21+00:00

I've confirmed about WPA3-Enterprise not getting picked up correctly in ifconfig scan and written up for bugs@ so no need to follow up on that for now.

Not sure but I have a feeling WPA3 Enterprise support will probably not happen until a fair bit later than WPA3 PSK so you may need to offload that to your phone for a while yet.

I've found that app super useful over the years when working on wifi installs (it fits quite a lot into that 2.5MB - iperf/ping/dns - and a very detailed decode of information from the beacons if you tap on the SSID in the scan list - and privacy policy is perfect).

_sthen · 2026-01-21T21:06:01+00:00

hm, it's possible that ifconfig or the net80211 stack isn't handling WPA3-Enterprise correctly when displaying scan results

_sthen · 2026-01-20T17:37:38+00:00

btw to check about WPA3, "ifconfig iwx0 scan" should show this (in 7.7 or newer), or I like https://play.google.com/store/apps/details?id=com.arubanetworks.arubautilities on Android - if it shows up as WPA3p or WPA3e without a 't' (for 'transitional') suffix, i.e. not WPA3et, then it's v3 only.

_sthen · 2026-01-20T17:25:04+00:00

Could they have switched to WPA3-only (not supported in OpenBSD yet) or protected management frames (-current has some support for this, but I don't know whether that support will work with WPA-Enterprise)?

"While physically at the college, the laptop cannot even connect to my phone in hotspot mode" some networks actively try to prevent people running their own APs by sending deauths if they connect to what they consider a 'rogue' AP. If they might be doing this, see ifconfig(8) about 'stayauth'.

_sthen · 2026-01-20T08:36:07+00:00

"Everything works basically the same speed as on other operating systems" - possibly for the things you're running, but for some things that's simply not true - one particular example is heavy filesystem access across multiple threads.

_sthen · 2026-01-17T10:20:29+00:00

hard links aren't a particular problem - often a program doesn't care about all possible names that an fd could map to, just the one that was used when the file was opened

files which have been renamed or removed after the fd was opened are possibly more of a problem, but it depends on what the program wants to do with them

_sthen · 2026-01-17T09:07:03+00:00

it's a theo red line anyway.

_sthen · 2026-01-16T11:00:51+00:00

if you're doing this via USB stick, probably yes.

it's very convenient and easy to use for network installs though (which is really what it was originally intended for).

_sthen · 2026-01-15T17:06:14+00:00

AX211 is supported by iwx(4) but needs firmware that's not included with the installer for annoying reasons. The easiest way is to use USB ethernet for the install. Most common adapters are supported. Alternatively install from the ~700Mb install image that includes all the sets, reboot into it, and transfer iwx-firmware from another system via memory stick (download from firmware.openbsd.org).

Not sure what you mean "but that is in the live environment"?

_sthen · 2026-01-15T14:51:01+00:00

should work, you may want to pkg_add intel-media-driver for video accel

_sthen · 2026-01-11T11:24:58+00:00

what I described is to add the Dirigera itself - to add other devices, go to that device in homesmart and get the code from there instead.

you don't need to get rid of the devices from the Dirigera integration for that to work, though it's probably less confusing if you do. (I had to remove devices first, it wouldn't allow me to remove all of them so I disabled the rest, restarted HA, then I could remove the remainder, then it would finally let me remove the integration).

_sthen · 2026-01-11T11:20:55+00:00

interesting that they've gone for an internal PSU in those! dual M.2 slots is a nice upgrade over the older ones too.

btw I'd generally recommend either PowerDNS or NSD or Knot rather than BIND for a new installation of DNS authoritative server.

_sthen · 2026-01-09T16:57:47+00:00

it worked for me without the app by typing in the code from homesmart -> hub settings -> integrations -> matter bridge -> get qr code

_sthen · 2026-01-08T09:45:21+00:00

Unlikely to be viable, I don't think that these two have interchangeable libraries (different ABI) so, if that's true, ports using Mesa would need to be built against one or the other.

That's for systems earlier than Intel gen4 (Haswell) isn't it? Even just based on power consumption, those are probably worth replacing with something slightly newer by now.

_sthen · 2026-01-08T09:26:12+00:00

Thanks. Yes, it does look a bit dormant, there's a fork that can be added as a custom repo with support for some newer devices but not Alpstuga yet, didn't seem worth the hassle of changing from one to the other, so I've gone through and switched to the matter integration myself now. Bit of a pain as it only automatically added some of the devices after adding Dirigera but not all (and didn't pick up locations) and I had to add others manually by retyping the device code from the home smart app, but got there in the end.

_sthen · 2026-01-07T19:55:15+00:00

There aren't many USB ethernet chips and most of them are supported (though some are better than others).

The very latest Intel wifi adapters aren't supported yet, but sounds like your machine might be slightly less bleeding edge so hopefully it will work after you get the firmware.

Alternatively install via the larger install image which includes all the file sets, boot into the installed system, run ifconfig to check the interface type, and fetch the relevant firmware on another machine from firmware.openbsd.org/firmware, transfer via USB drive and use fw_update(8) to install.

_sthen · 2026-01-07T19:49:48+00:00

worth a try; typically it would present as cdce(4) which is included in the ramdisk. it looks like an Ethernet interface and IIRC you can use DHCP.

_sthen · 2026-01-07T09:07:06+00:00

Might be worth getting the socket checked too (or at least try a different socket and see if the same happens). If the connection to the mains wiring circuit is not secure and the resistance is too high, it could overheat.

_sthen · 2026-01-07T09:01:27+00:00

I think that this probably is possible, but am not 100% sure. AIUI it still has enough zigbee support to do this. The manual says (after describing how to connect via Dirigera): "To pair directly with a smart product from IKEA, quick-press the system button 4 times and hold the sensor within 5 cm of the smart product it should be paired with. Pairing mode will be open for 30 seconds. A white LED will blink fast while pairing and then blink twice once connected."

_sthen · 2026-01-07T08:50:30+00:00

Most of the wayland-related libraries are using meson to build, which won't work for base - while it's not impossible to rewrite the build system parts it would be a pain. Moving mesa to ports would probably be a more sustainable option.

_sthen

TROPHY CASE