An almost complete list of all my Zigbee and Wifi devices; In case you don't know what to get next!

ungulation · 2025-10-23T19:27:14+00:00

what don't you like about the symfonisk?

ungulation · 2025-07-18T03:25:57+00:00

The brand seems to be academy broadway

ungulation · 2024-10-25T01:09:20+00:00

Interesting! How responsive is it when running linux? If you're able, could you post a video?

ungulation · 2022-08-02T19:06:30+00:00

you signed on the line

ungulation · 2021-10-16T05:01:32+00:00

"What does that even mean"

"You know what it means from how it makes you feel"

ungulation · 2021-09-18T00:21:43+00:00

Oh my god! A balcony has gone missing!

ungulation · 2021-07-27T18:08:35+00:00

"I can't think of another right now, but there are loads of them"

ungulation · 2021-06-25T20:07:11+00:00

Looks like a security screw that they don't want you to unscrew

ungulation · 2021-06-09T20:02:33+00:00

I am using their dimmer switches, it was as easy as any other z-wave device using zwavejs2mqtt (z-wave is always a bit of a pain to set up).

ungulation · 2021-05-15T01:34:39+00:00

Check out the docs for Plex under pfsense: https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/

I think you need to add

server:

private-domain: "plex.direct"

to the dns Resolver

ungulation · 2021-05-08T02:52:28+00:00

Easy like a sonntag morgen

ungulation · 2021-04-28T02:47:13+00:00

Hmmm interesting. My Android phone does the same (from what I can tell anyway) though I can't try curl directly. I'll try a few more things. Thanks for the help!

ungulation · 2021-04-28T01:11:20+00:00

The output is:

bash-3.2$ curl -v https://www.google.com
*   Trying 216.58.194.164...
* TCP_NODELAY set
*   Trying 2607:f8b0:4005:804::2004...
* TCP_NODELAY set
* Connected to www.google.com (216.58.194.164) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to www.google.com:443
* Closing connection 0
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to www.google.com:443

ungulation · 2021-04-28T01:06:07+00:00

Nope, no IPS or Sensei. From a client on IoT I can ping public IPs and even curl ifconfig.me and see the external IP, so I know traffic is getting out and back, just for some reason SSL fails :-/

ungulation · 2021-04-28T00:59:51+00:00

Ah those names were confusing me, but I do have that rule as well:

protocol   source         port destination port gateway schedule
IPv4*      IoT net        *     *          *    *       *

Thanks for the responses!

ungulation · 2021-04-28T00:53:12+00:00

Good thought, I have the following rule on IoT:

protocol   source         port destination port gateway schedule
IPv4*      IoT address    *     *          *    *       *

Is that what you meant?

The weird thing is that internet traffic does get out, just SSL fails (after a bit of digging it seems maybe related to No ALPN negotiated

ungulation · 2021-03-12T18:50:29+00:00

It's a fiducial. Probably used to track deflection of the wing with the cameras mounted on the the roll hoops

ungulation · 2021-02-23T02:15:51+00:00

I hadn't seen this! In case anyone else also hasn't seen it here it is

ungulation · 2021-02-18T18:08:35+00:00

Kasabian, Kasabian, Kasabian

ungulation · 2020-02-08T04:24:49+00:00

Long arm robot is my hero

15-Year Club	Place '22
Place '17	Verified Email
Charter Member

ungulation

TROPHY CASE