| 26 Feb 2023 |
|  slamslask joined the room. | 22:19:19 |
| 27 Feb 2023 |
|  justlistening joined the room. | 01:32:35 |
| 28 Feb 2023 |
|  dobstopper joined the room. | 21:00:07 |
| 1 Mar 2023 |
|  takov751 left the room. | 09:31:58 |
| 2 Mar 2023 |
|  iurab6 joined the room. | 14:40:09 |
| 3 Mar 2023 |
|  xor_alchemist joined the room. | 22:33:26 |
| 4 Mar 2023 |
|  EricD joined the room. | 15:53:19 |
| 6 Mar 2023 |
|  great-white-bark joined the room. | 11:27:35 |
| 8 Mar 2023 |
|  DivideByZero joined the room. | 01:53:15 |
| 9 Mar 2023 |
| justlistening left the room. | 23:56:18 |
| 10 Mar 2023 |
|  Adrián changed their display name from Erao to Adrián. | 23:09:14 |
| Adrián changed their profile picture. | 23:10:55 |
| 11 Mar 2023 |
|  js3z | 04:06:47 |
|  Kinetic Pizza joined the room. | 12:19:22 |
| Kinetic Pizza changed their display name from kineticpizza to Kinetic Pizza. | 12:35:04 |
| 12 Mar 2023 |
|  whitenight12 joined the room. | 12:31:20 |
 jwillikers | ironicbadger: Why not run Home Assistant on the Yellow and ESPHome on a separate x86_64 machine? | 13:30:20 |
| jwillikers | chrislas: I recently switched over from Ubiquiti to TP-Link. After several years of my UniFi AP losing connection to the UniFi Controller, I finally had it when my AP failed to adopt after a couple of days when I was transitioning my home network over to a different subnet. It literally got stuck during the adoption process and just hung there. From what I was able to tell, shelled into the AP, it was somehow failing to do a freaking HTTP request to the controller... I couldn't fix it even with a manual firmware upgrade on the AP. I switched to TP-Link and the Omada Controller and have been incredibly happy. It just works. The AP stays connected and my countless IoT devices work out of the box. I struggled to get them to work with the UniFi AP. Just this week I connected my first Matter device, a TP-Link Tapo P125M WlFi smart plug, and that worked great. Just heed the warning about attempting to put the device on a separate VLAN, that didn't work for me. | 13:42:36 |
 chrislas | In reply to @jwillikers:matrix.org
chrislas: I recently switched over from Ubiquiti to TP-Link. After several years of my UniFi AP losing connection to the UniFi Controller, I finally had it when my AP failed to adopt after a couple of days when I was transitioning my home network over to a different subnet. It literally got stuck during the adoption process and just hung there. From what I was able to tell, shelled into the AP, it was somehow failing to do a freaking HTTP request to the controller... I couldn't fix it even with a manual firmware upgrade on the AP. I switched to TP-Link and the Omada Controller and have been incredibly happy. It just works. The AP stays connected and my countless IoT devices work out of the box. I struggled to get them to work with the UniFi AP. Just this week I connected my first Matter device, a TP-Link Tapo P125M WlFi smart plug, and that worked great. Just heed the warning about attempting to put the device on a separate VLAN, that didn't work for me. Good to know.
I never did narrow down why it was dropping devices on my network. Part of me wonders if it's because my cameras are just blasting the Wi-Fi network with a ton of data | 15:26:45 |
| jwillikers | In reply to @chrislas:jupiterbroadcasting.com
Good to know.
I never did narrow down why it was dropping devices on my network. Part of me wonders if it's because my cameras are just blasting the Wi-Fi network with a ton of data I traced most of my IoT device issues to be related to very specific options, most of which I probably enabled at some point, in the UniFi controller specifically regarding the wireless options. I remember 802.11r being one of the culprits. I probably shot myself in the foot with rate control at one point, too. It's funny, looking at the Omada settings page for my wireless networks, there's only two or three of all of the options checked. | 19:23:55 |
| jwillikers | In reply to @chrislas:jupiterbroadcasting.com
Good to know.
I never did narrow down why it was dropping devices on my network. Part of me wonders if it's because my cameras are just blasting the Wi-Fi network with a ton of data * I traced most of my IoT device issues to be related to very specific options, most of which I probably enabled at some point, in the UniFi controller specifically regarding the wireless options. I remember 802.11r being one of the culprits. I probably shot myself in the foot with rate control at one point, too. It's funny, looking at the Omada settings page for my wireless networks, there's only two or three of all of the options checked. Fyi, I did contact TP-Link through their "Business" email contact form about some SNMP MIBs for their AP, and was very pleased with their support. I'm not sure if you've tried contacting them, but it might be worth a shot. Anything to avoid having to open up Wireshark and analyze packets, right? | 19:26:08 |
| 13 Mar 2023 |
|  MasterDev joined the room. | 04:07:07 |
|  evanwithhoovers joined the room. | 14:27:14 |
 ⚡️ ⚔️ su || cd ⚔️ ⚡️ | Redacted or Malformed Event | 23:02:31 |
| 14 Mar 2023 |
| DivideByZero changed their display name from durendal_ii to DivideByZero. | 00:44:37 |
|  nibblerrick joined the room. | 07:58:35 |
| 15 Mar 2023 |
|  Dahjah joined the room. | 02:18:13 |
| 16 Mar 2023 |
|  Mardsnova joined the room. | 11:02:30 |
| Mardsnova changed their display name from sulley2049 to Mardsnova. | 11:39:56 |
| 17 Mar 2023 |
|  Bun joined the room. | 19:25:13 |
