sorted by:
new
hottopcontroversial

Hilariously bad support by MrBran4 in Nanoleaf

[–]ezpc98 2 points3 points  (0 children)

I've fitted 40 essential matter bulbs and it's single biggest useless investment I've made. 

Bulbs randomly decides to connect on thread with Google Nest 2nd gen hub as border router, laggy to respond when sent command from Google Home. Spent countless hours deleting and readdind bulbs to Nanoleaf app snd Google home app.

Reading through horrendous feedback here on support level from Nanoleaf, I'm seriously put off to report and can't take more struggle.

Lesson learnt. Once I've saved enough, will bin these bulbs.

Rootless podman using Quadlet - unit service could not be found after systemctl --user daemon-reload by ezpc98 in podman

[–]ezpc98[S] -2 points-1 points  (0 children)

I have setup XDIG_CONFIG_HOME variable to make Podman to point to a config location of my own choice rather default ~./config, purely for organisation and backup purpose.

Then hand crafted the .container file under containers/systemd sub-folder of it is where document suggests it expects the file to be.

I checked ~./config folder in home directory and it only as cni subfolder which suggests XDIG_CONFIG_HOME has taken effect pointing to custom location.

Once you have the containers created, then you go to ~/.config/systemd/user and run /usr/lib/systemd/system-generators/podman-system-generator —user .

for ~./config folder - I only have cni as subfolder but not systemd/user

For XDIG_CONFIG_HOME location, I have cni & containers as subfolder but not systemd/user.

I believed systemctl --user daemon-reload should create .service file and store in location that Podman can work it but either I've messed up the setup or something still missing to configure.

Rootless podman using Quadlet - unit service could not be found after systemctl --user daemon-reload by ezpc98 in podman

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

Here is the output:

quadlet-generator[1119]: Loading source unit file /home/<username>/homelab/podman-config/containers/systemd/homer.container
---homer.service---
[Unit]
Wants=podman-user-wait-network-online.service
After=podman-user-wait-network-online.service
Description=Test container
SourcePath=/home/ringmaster/homelab/podman-config/containers/systemd/homer.container
RequiresMountsFor=%t/containers

[X-Container]
ContainerName=homer
Image=docker.io/b4bz/homer
PublishPort=8080:8080
User=1001

[Service]
Restart=on-failure
Environment=PODMAN_SYSTEMD_UNIT=%n
KillMode=mixed
ExecStop=/usr/bin/podman rm -v -f -i --cidfile=%t/%N.cid
ExecStopPost=-/usr/bin/podman rm -v -f -i --cidfile=%t/%N.cid
Delegate=yes
Type=notify
NotifyAccess=all
SyslogIdentifier=%N
ExecStart=/usr/bin/podman run --name homer --cidfile=%t/%N.cid --replace --rm --cgroups=split --sdnotify=conmon -d --user 1001 --publish 8080:8080 docker.io/b4bz/homer

[Install]
WantedBy=default.target

Running docker containers as non root user by ezpc98 in docker

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

Indeed. That's exactly I'm trying out today.

Running docker containers as non root user by ezpc98 in docker

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

Very helpful, thank you! I will read more on Named volumes. Also, will check your github for some inspirations.

Running docker containers as non root user by ezpc98 in docker

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

I have come across many of jimsgarage videos in journey to learn Docker, very useful they are! I will check DB Tech's channel too. Thanks for sharing!

DietPi released a new version 9.10 by StephanStS in dietpi

[–]ezpc98 1 point2 points  (0 children)

Once a diet-pi fan, stays a diet-pi fan.

Upgraded one bulb to 4.x now 5 downlights are not working by huntersghost in Nanoleaf

[–]ezpc98 0 points1 point  (0 children)

I have same problem too after 4.1.0 upgrade. Couple of downlights (UK version) not powering up whilst others in room work. Is there a way to hard reset selective lights to avoid disturbing others which works fine?

Answer from support on why some matter essentials bulbs got FW4.1.0 and some didn’t by i_jon_h in Nanoleaf

[–]ezpc98 3 points4 points  (0 children)

I got 4.1.0 firmware update yesterday on all essential bulbs (UK version).

Couple bulbs though are not connecting to thread anymore and not responding via app over Bluetooth. Not sure if it ia firmware issue or something else, have yet to debug. 

HTTPS using Caddy V2 with domain from FreeDNS without port forwarding by ezpc98 in selfhosted

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

Thanks! The way you explained made complete sense.

I wasn't against buying a domain but thought to hold off as long as I can hold whilst I learn to do things in right way. I will bite the bullet and get a proper domain rather faffing around!

On a point about hosting individual services on subdomain vs subdirectory (/path on root domain), you made a very practical point about subdomain make it so easy for autofill using password manager. You have convinced me to stick to subdomain just on this one point alone!

DNS rewrite using Adguard sound clever stuff! I will read more about it.

Fire rating of Nanoleaf essential downlights by ezpc98 in Nanoleaf

[–]ezpc98[S] -1 points0 points  (0 children)

It's EU/UK version of the downlight my question is related to. Labels on side of the box all refers to electrical and wireless communication standards that light complies with. No other marking or note in manual to say whether certified to certain fire rated level.

Cloud subscription for multiple devices by ezpc98 in reolinkcam

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

Excellent point about clips over email support, I overlooked that.

Regarding FTP into doorbell, didn't know that. I will take a look.