| commit | 9661374ddc013e4101b5a0bdf80d76ce484fae18 | [log] [tgz] |
|---|---|---|
| author | hnnajh <72513572+hnnajh@users.noreply.github.com> | Wed Jan 06 08:05:28 2021 -0800 |
| committer | GitHub <noreply@github.com> | Wed Jan 06 08:05:28 2021 -0800 |
| tree | 5ccb0b2b878303f2ac61936825a4fa6a37761042 | |
| parent | a108646e6caf071ce0a9d26c01abdfab5727907d [diff] |
Adding Rotating Device Id to BLE & DNS-SD discovery (#4210)
* RotatingId: version0
* RotatingId: version1
* RotatingId: version0
* RotatingId: version1
* Fix Darwin host build (#3990)
#### Problem
Some conversions to use PacketBufferHandle (#3909) broke Darwin builds,
which aren't currently run in CI.
#### Summary of Changes
Fix src/platform/Darwin/BleConnectionDelegateImpl.mm to match the API
change in #3909.
* Add '-Wextra' to compiler flags (#3902)
* Implement Level Control Cluster (#3806)
* New seekbar in Android CHIPTool
* Sample usage in lighting-app/nrfconnect
Signed-off-by: Markus Becker <markus.becker@tridonic.com>
* Fix Rendezvous over BLE after recent changes (#4012)
PR #3704 introduced a change that the BLE transport in
RendezvousSession is only initialized when PeerAddress
in RendezvousParams is of type BLE. However, PeerAddress
isn't initialized anywhere. As a result Rendezvous over BLE
stopped working between Android CHIPTool and accessories.
Btw, remove an assert related to the storage delegate
as it seems an optional member of the device controller.
* [thread] fix invalid configuration of active dataset (#4008)
* Fix data loss or crash in TCPEndPoint with LwIP (#4022)
* Fix data loss or crash in TCPEndPoint with LwIP
#### Problem
Under the configuration CHIP_SYSTEM_CONFIG_USE_LWIP, in some cases where
the data size exceeds the TCP window size, TCPEndPoint can either die or
lose data when accounting of un-acked data falls out of sync.
#### Summary of Changes
Imported fix from Weave:
* This change removes separate accounting of the unsent
data position and replaces it with simple counting of
sent-but-not-acked data and a skip-loop at the start
of DriveSending().
Fixes #4013 - Data loss or crash in TCPEndPoint with LwIP
* Restyled by clang-format
Co-authored-by: Restyled.io <commits@restyled.io>
* Update lighting-app gen/ folder with ZAP generated content (#4010)
* Fix segmentation fault error in response echo message (#3984)
* Add back Android default build coverage & fix the build (#3966)
mDNS doesn't build with no device layer. Remove it from the build and
add back the coverage that would catch this that was lost in #3340.
* Update all-clusters-app gen/ folder with ZAP generated content (#3963)
* Move src/inet/tests to auto-test-driver generation (#3997)
* Rename TestUtils to UnitTestRegistration. (#4021)
Looking to remove usage of 'Utils' unless we have really no choice.
'UnitTestRegistration' seems clearer in what it does compared to
'TestUtils'.
* Update src/lib/core/tests to auto-test-driver generation (#3991)
* Cleanup zap chip-helper.js (#3973)
* Cleanup zap chip-helper.js
* Restyled by clang-format
Co-authored-by: Restyled.io <commits@restyled.io>
* Move src/transport/tests to auto-test-driver generation (#3999)
* Move src/transport/tests to auto-test-driver generation
* Add relevant libraries (and more test-capable libs) to nrf.
* Refactor inet test helpers (to not include actual inet tests), try to make qemu allow better linkage but still failed for transport tests so disabled for now
* Added more tests on esp32 qemu
* Restyle fixes
* Fix cast errors in InetCommon
* Disable raw tests from zephyr: somehow they fail running out of endpoints
* Disable DNS test on zephyr
* Remove inet endpoint test from zephyr
* Remove inet endpoint test from zephyr - fix again
* Modify gitignore
* Restyle fixes
* Use CHIPDeviceController instead of CHIPDeviceController_deprecated (#3979)
* Implement the missing part of Exchange Header in Transport layer (#4017)
* Implement the missing part of Exchange Header in Transport layer
* Revert comment 'if' back to 'iff'("if and only if")
* Remove duplicated send flag defines and put ExchangeMgr/ExchangeConte… (#3994)
* Remove duplicated send flag defines and put ExchangeMgr/ExchangeContext under the same namespace as CRMP
* Rename kSendFlag_Default to kSendFlag_None
* Move src/lib/asn1/tests and src/ble/tests to auto-test-driver generation (#3998)
* Move src/lib/asn1/tests and src/ble/tests to auto-test-driver generation
* Remove one more unused file
* Attempt to enable asn1 and ble tests in esp32 - see if they pass or not
* Fix merge error
* Update include header for ASN1 test
* Include ASN1 in libCHIP
* Some conversions to use PacketBufferHandle (#4011)
* Some conversions to use PacketBufferHandle
#### Problem
Code should use `PacketBufferHandle` rather than `PacketBuffer *`.
#### Summary of Changes
- Converts remaining receive path in //src/inet and //src/transport.
- Converts most of //src/ble.
- Introduces Handle versions of the `AddToEnd`/`DetachTail` pair.
Part of issue #2707 - Figure out a way to express PacketBuffer ownership in the type system
* Restyled by clang-format
* review
* revive BtpEngine::Clear[TR]xPacket()
* simplify conditional
* (void) message.DetachTail() → message.FreeHead()
* remove ExchangeContext::kSendFlag_RetainBuffer
* missed pBuf.IsNull()
* DetachHead() → PopTail()
* typos
Co-authored-by: Restyled.io <commits@restyled.io>
* Move src/system/tests to auto-test-driver generation (#4000)
* Move src/system/tests to auto-test-driver generation
* Remove a TCP/IP init call that was killing qemu
* Remove explicit "all" target from root build file (#3967)
The "all" target exists implicitly and contains everything. We don't
need to specify one, and it's misleading to do so specifying deps has no
effect.
* Make src/setup_payload compile with -Werror=conversion (#4032)
* Add SSID and password to chip-tool pairing (#4054)
* Get temperature-measurement and all-clusters-app to use examples/common/chip-app-server (#4039)
#### Problem
PR #3704 introduced a change where a `PeerAddress` is now required in order to start `RendezvousSession`.
Sadly the multiple code paths bootstrapping `RendezvousSession` has not been updated.
PR #4012 add a fix for some of the `examples/` but not for the `all-clusters-app` nor the `temperature-measurement-app`.
To avoid such situation, this PR merge `examples/common/chip-app-server` and the custom code from `all-clusters-app` and `temperature-measurement-app`.
One of the more discutable change of this PR (imo) is the code that moves the custom `Echo` mechanism from the `all-clusters-app` to `chip-app-server`. I was hoping to get rid of it before doing this change but the `all-clusters-app` and the `temperature-measurement-app` are broken since #3704 and this PR should fix that.
Also I have a PR (mostly) ready once #3979 lands to get rid of this `Echo` specific code and replace it by a manufacturer specific `ping` command.
#### Summary of Changes
* Remove `EchoServer.cpp`, `RendezvousDeviceDelegate.cpp` and `include/RendezvousDeviceDelegate.h` from `all-clusters-app`
* Remove `ResponseServer.cpp`, `RendezvousDeviceDelegate.cpp` and `include/RendezvousDeviceDelegate.h` from `temperature-measurement-app`
* Introduce `chip-app-server/include/AppDelegate.h` in order to keep the behavior the `all-clusters-app` that turns on/off leds on different events. Maybe it should be converted to some types of `ChipDeviceEvent` or `CHIPCallback` at some point.
* Fix `chip-app-server` to accomodate for the specifics of `all-clusters-app`
* Add all Thread ULA addresses to the lwip interface (#4053)
ULA prefixes will used for CHIP network so we need to add all these
addresses to the interface.
* Remove src/lib/message. (#4055)
* Remove src/lib/message.
Updated messaging implementation lives in src/messaging and the
src/lib/message is not currently compiled or linked in.
This saves us from looking at this code when some refactoring is needed
(e.g. the SystemPacketBuffer changes).
* Remove one more unused file
* [ChipTool] Add Payload Parse Command (#3696)
* [ChipTool] Add Payload Parse Command
* [ChipTool] Add Payload Parse Command
* [ChipTool] Restyle issues resolved
* Restyled by whitespace
* Resolve build errors caused by Command.h schema change
Co-authored-by: lijayaku <lijayaku@amazon.com>
Co-authored-by: Restyled.io <commits@restyled.io>
* rename ParseCommand to QRCodeParseCommand
* adding AdditionalDataParseCommand version 0
* Adding parsing logic + logging
* adding another parsing method
* Basic Parsing is DONE
* fixing memory issue
* removing some logs
* removing more logs
* minor update
* Add RotatingDeviceId to DNS-SD
* fix compilation problem
* fix minor diffs
* cleanup rotating id in ble
* fix dns
* nits
* fix compilation
* Revert "fix minor diffs"
This reverts commit 88fb69cfc9752343f352c569746177a07a0bb5b0.
* nits
* nit fixes
* update allocation
* update allocation
* refactoring
* revert settings.json
* fix styling
* Update README file
* adding a build flag to bypass advertising the additional data field
* fix styling
* fixing README style
* Fixing nits + added description about the additional data
* fixed minor comment
* remove ParseCommand
* removing unused headers + nits
* Fixing Additional data TLV Tags
* Fix Styling
* removed unnecessary logging tag
* fixing writing rotating id
* fixing minor styles
* adding check for rotating id tag
* restyling
* update AdditionalDataPayloadParser to work on vector of bytes
* restyling
* Nit fix
* Renaming QRCode command to SetupPayload command
* update parse command for additional data
* change compile flags
* update some comments
* fixing parsing/generating the additional data payload
* changing the additional parser APIs
* restyling
* reverting pigweed repo changes
* rename CHIP_ENABLE_ADDITIONAL_ADVERTISING
* removing logging tag
* adding extra validation in parser
* adding docs to the additional data payload parser
* Update ReadME.md
Co-authored-by: Kevin Schoedel <67607049+kpschoedel@users.noreply.github.com>
Co-authored-by: Vivien Nicolas <vnicolas@apple.com>
Co-authored-by: Markus Becker <Markus.Becker@tridonic.com>
Co-authored-by: Damian Królik <66667989+Damian-Nordic@users.noreply.github.com>
Co-authored-by: Łukasz Duda <lukasz.duda@nordicsemi.no>
Co-authored-by: Restyled.io <commits@restyled.io>
Co-authored-by: Yufeng Wang <44623591+yufengwangca@users.noreply.github.com>
Co-authored-by: Michael Spang <spang@google.com>
Co-authored-by: Andrei Litvin <andrei@andy314.com>
Co-authored-by: jepenven-silabs <67962328+jepenven-silabs@users.noreply.github.com>
Co-authored-by: Boris Zbarsky <bzbarsky@apple.com>
Co-authored-by: Jiacheng Guo <gjc@google.com>
Co-authored-by: Liju Jayakumar <26148162+lijujayakumar@users.noreply.github.com>
Co-authored-by: lijayaku <lijayaku@amazon.com>
Project Connected Home over IP is a new Working Group within the Zigbee Alliance. This Working Group plans to develop and promote the adoption of a new, royalty-free connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet.
The goal of the Connected Home over IP project is to simplify development for manufacturers and increase compatibility for consumers. The project is built around a shared belief that smart home devices should be secure, reliable, and seamless to use. By building upon Internet Protocol (IP), the project aims to enable communication across smart home devices, mobile apps, and cloud services and to define a specific set of IP-based networking technologies for device certification.
The Zigbee Alliance officially opened the Project Connected Home over IP (Project CHIP) Working Group on January 17, 2020 and is in the process of drafting the specification.
Visit connectedhomeip.com to learn more and read the latest news and updates about the project.
Project Connected Home over IP is developed with the following goals and principles in mind:
Unifying: Project CHIP will produce a new specification, building with and on top of market-tested, existing technologies.
Interoperable: The specification permits communication between any Project CHIP-certified device, subject to users’ permission.
Secure: The specification leverages modern security practices and protocols.
User Control: The end user is in control of authorization for interaction with devices.
Federated: No single entity serves as a throttle or a single-point-of-failure for root of trust.
Robust: The set of protocols specify a complete lifecycle of a device — starting with the seamless out-of-box experience, through operational protocols, to device and system management specifications required for proper function in the presence of change.
Low Overhead: The protocols are practically implementable on low compute-resource devices, such as MCUs.
Pervasive: The protocols are broadly deployable and accessible, thanks to leveraging IP and being implementable on low-capability devices.
Ecosystem-Flexible: The protocol must be flexible enough to accommodate deployment in ecosystems with differing policies.
Easy to Use: The protocol should aim to provide smooth, cohesive, integrated provisioning and out-of-box experience.
Open: The Project’s design and technical processes should be open and transparent to the general public, including to non-members wherever possible.
The Project, as illustrated above, defines the application layer that will be deployed on devices and controllers as well as the supported IPv6-based networks to help achieve our interoperability architectural goal. Project CHIP will initially support Wi-Fi and Thread for core, operational communications and Bluetooth Low Energy (BLE) to simplify device commissioning and setup.
The Application Layer can be further broken down seven main components:
Application: High order business logic of a device. For example, an application that is focused on lighting might contain logic to handle turning on/off the bulb as well its color characteristics.
Data Model: Data primitives that help describe the various functionalities of the devices. The Application operates on these data structures when there is intent to interact with the device.
Interaction Model: Represents a set of actions that can be performed on the devices to interact with it. For example, reading or writing attributes on a device would correspond to interactions with the devices. These actions operate on the structures defined by the data model.
Action Framing: Once an action is constructed using the Interaction Model, it is framed into a prescriptive packed binary format to enable being well represented on the “wire”.
Security: An encoded action frame is then sent down to the Security Layer to encrypt and sign the payload to ensure that data is secured and authenticated by both sender and receiver of a packet.
Message Framing & Routing: With an interaction encrypted and signed, the Message Layer constructs the payload format with required and optional header fields; which specify properties of the message as well some routing information.
IP Framing & Transport Management: After the final payload has been constructed, it is sent to the underlying transport protocol for IP management of the data.
The Project’s design and technical processes are intended to be open and transparent to the general public, including to Work Group non-members wherever possible. The availability of this GitHub repository and its source code under an Apache v2 license is an important and demonstrable step to achieving this commitment.
The Project endeavors to bring together the best aspects of market-tested technologies and to redeploy them as a unified and cohesive whole-system solution. The overall goal of this approach is to bring the benefits of the Project to consumers and manufacturers as quickly as possible. As a result, what you observe in this repository is an implementation-first approach to the technical specification, vetting integrations in practice.
The Project repository is growing and evolving to implement the overall architecture. The repository currently contains the security foundations, message framing and dispatch, an implementation of the interaction model and data model. The code examples show simple interactions, and are supported on multiple transports -- Wi-Fi and Thread -- starting with resource-constrained (i.e., memory, processing) silicon platforms to help ensure the Project’s scalability.
We welcome your contributions to Project Connected Home over IP. Read our contribution guidelines here.
Instructions about how to build Project Connected Home over IP can be found here.
The Connected Home over IP repository is structured as follows:
| File / Folder | Contents |
|---|---|
.default-version | Default Project CHIP version if none is available via source code control tags, .dist-version, or .local-version |
build/ | Build system support content and build output directories |
| BUILDING.md | More detailed information on configuring and building Project CHIP for different targets |
CODE_OF_CONDUCT.md | Code of Conduct for Project CHIP, and contributions to it |
| CONTRIBUTING.md | Guidelines for contributing to Project CHIP |
CONTRIBUTORS.md | Contributors to Project CHIP |
docs/ | Documentation |
examples/ | Example firmware applications that demonstrate use of Project CHIP technology |
integrations/ | Third party integrations related to this project |
integrations/docker/ | Docker scripts and Dockerfiles |
LICENSE | Project CHIP License file (Apache 2.0) |
Makefile-Android | Convenience makefile for building Project CHIP against Android |
Makefile-Standalone | Convenience makefile for building Project CHIP as a standalone package on desktop and server systems |
README.md | This file |
src/ | Implementation of Project CHIP |
third_party/ | Third-party code used by Project CHIP |
tools/ | Tools needed to work with the Project CHIP repo |
Project CHIP is released under the Apache 2.0 license.