I genuinely don’t know how people get their license just completely plows into me as I’m driving regularly straight, it’s a total loss. Yes it’s just 328 but fuck man this thing was my absolute baby for years and is my first car did everything to it
:( absolutely heart broken and devastated
I've been struggling with this device for a while. Does anyone have an idea what's going on and how to get it to properly pair?
2026-06-30 15:36:40.356 DEBUG MdnsAdvertisement Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 578 next: 1m 30s
2026-06-30 15:36:57.771 INFO WebSocketC~erHandler [3] WebSocket connection established
2026-06-30 15:36:57.773 DEBUG WebSocketC~erHandler [3] Sending server info
2026-06-30 15:36:57.779 DEBUG WebSocketC~erHandler [3] WebSocket request {"message_id":"499065763","command":"start_listening","args":{}}
2026-06-30 15:36:57.782 INFO WebSocketC~erHandler WebSocket server start_listening
2026-06-30 15:36:57.782 INFO WebSocketC~erHandler WebSocket server start_listening. Returned 0 nodes
2026-06-30 15:36:57.782 DEBUG WebSocketC~erHandler [3] WebSocket response (start_listening) 499065763
2026-06-30 15:37:00.019 DEBUG WebSocketC~erHandler [3] WebSocket request {"message_id":"499065764","command":"get_loglevel","args":{}}
2026-06-30 15:37:00.042 DEBUG WebSocketC~erHandler [3] WebSocket response (get_loglevel) 499065764 { console_loglevel: "debug", file_loglevel: null }
2026-06-30 15:37:10.606 DEBUG WebSocketC~erHandler [3] WebSocket request {"message_id":"499065765","command":"set_wifi_credentials","args":{"ssid":"SSID_REDACTED","credentials":"WPA_KEY_REDACTED"}}
2026-06-30 15:37:10.606 INFO ConfigStorage Set config key wifiSsid to SSID_REDACTED
2026-06-30 15:37:10.616 INFO ConfigStorage Set config key wifiCredentials to <redacted>
2026-06-30 15:37:10.620 INFO WebSocketC~erHandler Broadcasting server_info_updated event { fabric_id: 2, compressed_fabric_id: 7828733150003217139, fabric_index: 1, schema_version: 11, min_supported_schema_version: 11, sdk_version: "matter-server/1.1.2 (matter.js/0.17.4-alpha.0-20260625-0f2168fd4)", wifi_credentials_set: true, wifi_ssid: "SSID_REDACTED", thread_credentials_set: false, bluetooth_enabled: false, ble_proxy_enabled: false, controller_node_id: 112233 }
2026-06-30 15:37:10.621 DEBUG WebSocketC~erHandler [3] WebSocket response (set_wifi_credentials) 499065765 {}
2026-06-30 15:37:18.110 DEBUG WebSocketC~erHandler [3] WebSocket request {"message_id":"499065766","command":"get_loglevel","args":{}}
2026-06-30 15:37:18.110 DEBUG WebSocketC~erHandler [3] WebSocket response (get_loglevel) 499065766 { console_loglevel: "debug", file_loglevel: null }
2026-06-30 15:37:24.103 INFO WebSocketC~erHandler [3] WebSocket connection closed
2026-06-30 15:38:10.358 DEBUG MdnsAdvertisement Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 579 next: 1m 30s
2026-06-30 15:39:24.789 DEBUG WebSocketC~erHandler [2] WebSocket request {
"message_id": "65967dbc3da241d696dd9deaa68f7a13",
"command": "commission_with_code",
"args": {
"code": "MT:KUAA0YBV01B68K4YI10",
"network_only": true
}
}
2026-06-30 15:39:24.793 INFO ConfigStorage Set config key nextNodeId to 15
2026-06-30 15:39:24.802 INFO Discovery Initiating discovery of node with discriminator 2425
2026-06-30 15:39:24.832 INFO CommissioningClient Operational address for undefined set to udp://[fe80::d60a:dcff:fe22:8d13%enp6s18]:5540
2026-06-30 15:39:24.833 INFO Endpoint server-2-134b.peer1 ready endpoint#: (unassigned) type: RootNode (0x16) behaviors: 💤parts ✓index ✓commissioning ✓network
2026-06-30 15:39:24.840 INFO Controller~missioner Establish PASE to device DT: 769 PH: 36 ICD: 0 VP: 5004+13825 PI:
2026-06-30 15:39:24.845 DEBUG MessageExchange New exchange » •unsecured#b33456a429f28624⇵b2c3 protocol: 0 peerSess: 0000 SAT: 4s SAI: 300ms SII: 500ms maxTrans: 5 MRP I
2026-06-30 15:39:24.852 DEBUG MessageChannel Message » for: SC/PbkdfParamRequest backOff: 636ms id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:25.491 DEBUG MessageChannel Message » for: SC/PbkdfParamRequest retrans#: 1 backoff: 617ms id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:26.109 DEBUG MessageChannel Message » for: SC/PbkdfParamRequest retrans#: 2 backoff: 1.05s id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:27.161 DEBUG MessageChannel Message » for: SC/PbkdfParamRequest retrans#: 3 backoff: 1.49s id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:28.648 DEBUG MessageChannel Message » for: SC/PbkdfParamRequest retrans#: 4 backoff: 2.79s id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:31.440 DEBUG MessageExchange Message •unsecured#b33456a429f28624⇵b2c3✉0ac36e95: Wait additional 8.44s for processing time and peer resubmissions after all our resubmissions
2026-06-30 15:39:39.885 INFO Session •unsecured#b33456a429f28624 Session ended
2026-06-30 15:39:39.886 WARN Commission~onnection Address udp://[fe80::d60a:dcff:fe22:8d13%enp6s18]:5540 unreachable for known-address-0-udp://[fe80::d60a:dcff:fe22:8d13%enp6s18]:5540
2026-06-30 15:39:39.888 DEBUG ParallelPa~Discovery Failed parallel commissioning attempt: [peer-communication] Could not connect to device
2026-06-30 15:39:40.360 DEBUG MdnsAdvertisement Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 580 next: 1m 30s
2026-06-30 15:41:10.364 DEBUG MdnsAdvertisement Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 581 next: 1m 30s
2026-06-30 15:42:24.833 ERROR WebSocketC~erHandler [2] WebSocket error response (commission_with_code) 65967dbc3da241d696dd9deaa68f7a13 Commission failed: discovery of node with discriminator 2425 failed: No device could be commissioned (1 of 1 started attempt(s) failed, 1 discovered)
at ServerError.nodeCommissionFailed (/app/node_modules/@matter-server/ws-controller/src/types/WebSocketMessageTypes.ts:100:16)
at ControllerCommandHandler.commissionNode (/app/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:969:31)
at async WebSocketControllerHandler.#commissionWithRetry (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:697:47)
at async WebSocketControllerHandler.#handleCommissionWithCode (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:741:24)
at async WebSocketControllerHandler.#handleWebSocketRequest (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:485:30)
Caused by: [discovery-aggregate] discovery of node with discriminator 2425 failed: No device could be commissioned (1 of 1 started attempt(s) failed, 1 discovered)
at CommissioningDiscovery.onComplete (/app/node_modules/@matter/node/src/behavior/system/controller/discovery/ParallelPaseDiscovery.ts:180:23)
Cause #0: [peer-communication] Could not connect to device
at ControllerCommissioner.#establishPaseFromCandidates (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:322:23)
at async ControllerCommissioner.commission (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:232:29)
at async CommissioningClient.commission (/app/node_modules/@matter/node/src/behavior/system/commissioning/CommissioningClient.ts:275:52)
at async Peers.runCommissioning (/app/node_modules/@matter/node/src/node/client/Peers.ts:365:20)
2026-06-30 15:42:40.366 DEBUG MdnsAdvertisement Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 582 next: 1m 30s
I had already 2x EAP245v3 working fine. I added 1x EAP775-Wall to an area with poor coverage and now my laptop wants to latch on to the weak signal from the EAP775 even when I am a few feet from the EAP245.
6ghz band for some reason doesn't want to work in the EAP775. When I try to upgrade firmware for any of the 3 AP on the controller it fails. It just shows UPGRADING for 5 minutes and then goes back like nothing ever happened, no sort of logs.
Connected on this far off EAP775 it took 5 minutes to try to upload the 30mb firmware file
I have a use case where we would like to lookup data from an external API, display the results, and then have an option to use that data to create a new lead/contact in Hubspot and guide the user to schedule a new meeting.
Is that something that can be accomplished with Hubspot?
In other words display a form, user enters a required data and hits submit, they see the result and are given the option to create new lead and if they were to select that it would pre-populate with some of the data from the API. Once that is submitted they are taken to the schedule meeting screen to complete that process.
Since someone is going to want to know why to spill the beans, I'll give you the long story.
I have a BGW320 in IP passthrough mode. About 2 months ago I stopped getting internet on an old ASUS router. I could remote into the ASUS router (when a PC was on a hotspot), configure a static WAN IP in the 192.168.1.x range and get back online.
I replaced the ASUS with an OpnSense router, configured IP passthrough and the same thing happened. I had to factory reset the BGW320 and re-configure passthrough to get back online without double NAT.
Now, 2 months later, the same thing his happening. I have not been on site to attempt a factory reset. Also during troubleshooting I could not get online with a spoofed WAN MAC address on the OpnSense router in an attempt to bypass IP Passthrough.
Therefore, what is the simplest way to get AT&T to send out a replacement BGW320? It seems to be the faulty piece in the equation.