unknowing8343

So, what I want to do is basically to be able to publish some of my own IR remotes at home to some public database, very probably IRDB. Of course I'd also be using the device for automations and so on, which I know it works great at that. But my main goal is to make it possible for people to not have to buy a stupid remote for some old hardware they have.

From the docs, it seems like it is possible.

Do you have any experience on this?

I was using the Plasma Vaults feature for the first time on my Linux computer, and it worked nicely (GoCryptFS), but when I wanted to sync that folder on my Android... I just couldn't find the right tool on Android for the job.

How do you solve this problem yourself?

The use case is basically so that all my family members we can check that "John has an old laptop collecting dust" or "Mary has this specific tool that I'd love to use for my current project".

It would be awesome if you could also have a private inventory, aside from the "shared knowledge".

So, what do you guys use for this? Maybe it does not have to be self hosted, but I have a sense the best solutions for this use case are.

Go and check the link, but essentially:

• small
• 2023 release (Android 13)
• HEADPHONE JACK (I was almost sold here)
• NFC
• 8GB RAM (that is powerful)
• 256 GB internal storage
• Dual SIM or SIM+MicroSD
• IR BLASTER (whatttttttt)
• LED indicators (front AND BACK)
• fingerprint scanner
• face ID
• FM Radio
• PROGRAMMABLE BUTTON (ok I'm in love already STOPPP)

I mean... this list is mindblowing. So...

What's the downside?

Honestly, you can go and check all reviews... but this phone is virtually perfect for the size, the only issue I have is that the screen is a bit too tiny, 3 inches, and 480p, and I think this will make many people run away.

It should make me look elsewhere also... but where? Any other small phone with a bigger screen is pretty bad, old, etc... and I really needed a new phone, so I realised this was an opportunity to commit to the cause, and buy and hopefully push this form factor from Unihertz to mainstream brands.

Hopefully one day we can get one with a slightly bigger screen, I believe 4 inches and 1080p would be brutal. But for now... I think I've found my new phone. In fact, I bought it 3 hours after knowing its existance.

If you are not sold yet...

Go check reviews on YouTube (example). Honestly, you'll see every reviewer falls in love with the device, even non-small phone lovers. It looks like it performs pretty well, it's decently fast, battery is solid, screen is bright and colorful, the LEDs are really useful, even Face ID (which I'll probably disable) is quick, it does not heat up at all, and even photos are pretty decent...

And it's something like 200 $. Come on. What a deal.

Will report back.

So, what do you think?

I followed this video to make my Home Asssistant accessible from everywhere, and yeah, port 8123 is fully clear to me, I've done it, it works great.

But he also talks about port 443, and when he sets it up in the router instead of choosing 443 on both WAN and LAN he goes for 443 to 8123. Why? And which one is the WAN and the LAN one? His router config has completely different names to mine, and as you can tell I am quite a noob at this.

I am worried that there is not really a benefit of doing that, just more noise and energy consumption.

There does not seem to exist like a single, complete solution for this that everyone agrees is the way to go... or maybe I did not look hard enough.

How do you do it?

My priorities are:

Top priority

• Turn off

Amazing to have

• Volume controls
• Pause/play

Nice to have

• monitoring state (on/off)

I saw that System Bridge exists, and looks almost perfect aside from the fact that is not even in the AUR (outdated) and is not distributed under Chocolatey in Windows... this makes me think that the project is very much not widely used at all.

So, how do you deal with these things?

How can I kill this evil thing?

This is probably not the place to do it but I figured it would be where I could find someone who fixed it.

Essentially the title.

If only S2 (previous connection point from light switch to bulb) is truly required, then, wow, that makes things way easier to install.

I guess electrically it makes sense, I'm just weirded out it does not show in the instructions.

I just started my journey into Home Automation, and I think I am starting to understand better what Matter actually signifies...

So, Zigbee is just a communication protocol, and the definition of smart devices is actually done by ZHA, Zigbee2MQTT, etc... correct?

So Matter actually reduces all those Zigbee sub-protocols into one thing, so one Matter bulb will be always compatible, you don't need to pick like we do now with ZHA, Zigbee2MQTT... correct?

And then, the Zigbee communication is substituted either with Thread (basically Zigbee technology but for Matter) or Wi-Fi. But the smart device definition is still Matter, so a bulb will always behave like Matter specifies, in terms of variables and parameters.

Am I getting close?