ESP8266 Wi-Fi Scans Need a Result-Ownership State Machine
Separate driver-owned scan results from bounded application snapshots, and close the cleanup lifecycle when refreshes, cancellation or retrieval fail.
-
-
Zephyr UDP MSG_TRUNC: The Returned Datagram Length Can Exceed the Bytes Copied
Why does a UDP receive call return more bytes than fit in its buffer, and why does a zero-length MSG_PEEK size probe fail to report the queued datagram size?
-
Zephyr Socket Dispatcher: Bind the Interface Before a Helper Selects the Default Backend
Why can a socket intended for one network module use another provider when a library sets an option before SO_BINDTODEVICE?
-
Greengrass Platform Manifests: Put Specific Matches Before the Fallback
Why can a valid component recipe select a generic artifact or lifecycle on an industrial gateway even when a matching architecture-specific manifest exists?
-
Greengrass Thing-Group Removal: Verify When the Old Components Actually Leave a Gateway
Why can a gateway retain group-deployed components after it is removed from that AWS IoT thing group?
-
AWS IoT Basic Ingest: Explain Why a Telemetry Rule Works but MQTT Subscribers See Nothing
Why can an industrial gateway reach its AWS rule through a reserved Basic Ingest topic while an otherwise correct MQTT observer receives no publication?
-
Greengrass Component Versions: Resolve Conflicting Thing and Thing-Group Requirements
Why does a deployment to one gateway fail to upgrade a component when another thing-group deployment still requires its old version?
-
Greengrass Update Deferral: Reply Before the Component Notification Timeout
How can an industrial gateway component defer a cloud deployment while finishing a bounded task, and why do silence, local deployment and a missed notification fail to protect that task?
-
Greengrass Component Configuration: Remove Obsolete Gateway Keys with Reset Before Merge
Why does a redeployed industrial collector retain an omitted setting, and how should reset paths, default values and whole-list replacement be combined to produce its intended effective configuration?
-
Greengrass Shadow Synchronization: Decide Which Offline Changes Win on Reconnect
When an industrial gateway and AWS IoT Core change the same shadow during an outage, which desired and reported values survive synchronization, and how does direction change that decision?
