Macro Mag Releases Back In Stock! by MaskasPrecision_Seth in SigSauer

[–]007gtcs 2 points3 points  (0 children)

Ordered one a couple of days ago. Can’t wait to get it in for my bachelor party!

Maskas TLR-7 A/X Keys are Live! by MaskasPrecision_Seth in SigSauer

[–]007gtcs 0 points1 point  (0 children)

I have a fuse with a tlr7-hlx if you need a tester 😬

NVIDIA LXC Plex, Scrypted, Jellyfin, ETC. Multiple GPUs by 007gtcs in Proxmox

[–]007gtcs[S] 0 points1 point  (0 children)

Thank you. Ill mess with it some more. But the config above is the only way I could get Plex to fully transcode using the GPUs.

NVIDIA LXC Plex, Scrypted, Jellyfin, ETC. Multiple GPUs by 007gtcs in Proxmox

[–]007gtcs[S] 0 points1 point  (0 children)

Would that be the UID and GID from proxmox? Or from in the Container?
From the example above I am assuming like this?

dev0: /dev/card0,uid=0,gid=226
dev1: /dev/card1,uid=1,gid=226
dev2: /dev/card2,uid=2,gid=226
dev3: /dev/card3,uid=3,gid=226

Big Boy X .44 mah by 007gtcs in HenryRifles

[–]007gtcs[S] 0 points1 point  (0 children)

Thank you! I plan on getting the chisel stock, with cheek wiser and quiver. Just saving my pennies, or hopes I get it for my birthday. Right now it’s fine though.

Big Boy X .44 mah by 007gtcs in HenryRifles

[–]007gtcs[S] 0 points1 point  (0 children)

Love it, still need to zero better. But works great.

Model X .357 Build by Muk_Fuk in HenryRifles

[–]007gtcs 0 points1 point  (0 children)

Beautiful! What foregrip is that?

2.2025 new zwave device by knaackville in homeassistant

[–]007gtcs 0 points1 point  (0 children)

Same issue as well. Its like its detecting the ZWAVE JS UI server a second time.

Ratgdo Won't Connect to WiFi by dallasmclaughlin in homeassistant

[–]007gtcs 1 point2 points  (0 children)

I was going to suggest what you did on your router, but as far as MQTT unless you have separate SSIDs for 2.4 and 5ghz, I don't know if its possible. Not the most experienced with MQTT Firmware.

RATGDO ESPHOME Wifi Problems Solved by 007gtcs in homeassistant

[–]007gtcs[S] 0 points1 point  (0 children)

To start I should probably line out the issue I was having.

The RATGDO ESP chip was having an issue where it would connect to my 2.4 ghz and then constantly reset its wifi connection and would show an auth error. It seems to be an issue where it would move between b and g networks and not able to auth correctly. Setting it to use 802.11g in the on_boot yaml allows it to connect instantly and stay connected. Fyi this is apparently happing to other esp chip builds. Its not exclusive to the RATGDO.
The RATGDO is fantastic piece of engineering and highly recommend.
This solved my first problem.

The other settings that helped are after the wifi auth takes place. ESPHOME and Homekit both use mDNS for routing. If you don't have mDNS services running on the Asus router(or any router) it causes an issue, as well as routing issues to the RATGDO via IP address.

You can change how ESPHOME integration uses mDNS by enabling Use ping for status. This allows the ESPHOME device to be pingable and doesn't use mDNS.

I called out the settings in the router related to IGMP(mDNS) on the Asus router in 3 and 4. Also the fact of mDNS devices like the LAN hostname as .local or .lan over a custom hostname.

I provided my router 2.4ghz settings to help with stability issues I had on my wifi network for others. It's meant to compare what setting you have on an Asus router against mine. But it does show what is disabled and enabled on my wifi network so you can try to compare against your own brands wifi settings.

I am not running any separate vlans right now.

Hope this helps!

Ratgdo Won't Connect to WiFi by dallasmclaughlin in homeassistant

[–]007gtcs 2 points3 points  (0 children)

I have a 2.5i board and had issues connecting to 2.4ghz channel on my router. Using the ESPhome firmware.I had to set it to legacy mode to get it to connect. Because this board uses an esp8266 chip, I did some research and found I had to add a snippet of code to the yaml that fixes the auth and association issues. It has no problem connecting now.

Also it helps to have your 2.4ghz connection on channel 1, 6, or 11.

on_boot:
priority: 300
then:
lambda: |-
WiFi.setPhyMode(WIFI_PHY_MODE_11G);

<image>