Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Change variable name accross layers.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

This commit still keeps the internal DISTRO variable name as-is and only
changes the longer free form version.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

While the WiFi SSID can be long enough the OpenThreads network name is
length limited so we stay with the Oniro short version.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

More changes to come, image, lvgl app and session service

Relate-to: https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/226


Signed-off-by: Philippe Coval <philippe.coval@huawei.com>

The wpantund package is only needed for scenarios where the OpenThread
device is operating in network co-processor (NCP) mode. We are not using
NCP, but radio co-processor (RCP instead). The later one works with
ot-br-posix out of the box and we have no need for wpantund, as of now.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

To enable more use cases and testing we provide MQTT and CoAP
implementations on the Linux gateway side.

Fixes: https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/182



Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

This is a first step to a working NAT64 setup on our gateway.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Andrei Gherzan authored 3 years ago and Stefan Schmidt committed 3 years ago

allscenarios-zephyr-blueprint-dashboard.conf: Define Zephyr-specific DISTRO for Smart Panel Blueprint

This has two advantages:
1. it fixes the build by removing the BBMASK configuration done in the
   main distro configuration files
2. it also provides default MAC addresses in sync with the Linux
   counterparts

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

A simple configuration script to set the Thread border router up.
Wrapped into a systemd service to handle execution and service
dependencies.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Thread connectivity is a feature that can come as a full border router
or simple client flavour. They both drag in different dependencies
through the matching packagegroup. Demonstrate the use in our gateway
blueprint.

Fixes: https://git.ostc-eu.org/OSTC/planning/blueprints/-/issues/7



Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Basic distribution for the Gateway Blueprint as well as a gateway  image
that pulls in all networking packages we are using for this first
iteration.

Two blueprint specific overrides are added as well. We make sure hostapd
service gets started by default for a good ootb experience. Secondly we
enable the iptables package config flag for systemd-netword to have the
basic NAT functionality enabled.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Ensure we enable packet forwarding for IPv6 and IPv4. This is needed
for a serving OpenThread network as well as WiFi AP services .

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Together with hostapd this will give us all we need to run a very basic
WiFi hotspot setup. DHCP, DNS and NAT for the clients to serve.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Basic WiFi AP configuration for nl80211 driver with WPA-PSK to avoid
opening up your networking accidentally to everyone.

The appended systemd service file fixes an issue with the upstream one
on the command-line argument ordering. The conf file has to be last or
the service does not start for me.

Fixes: https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/83



Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Only use the extra recipes and bbappends we add in meta-ohos-blueprint
in the blueprint distributions. This will avoid blueprint specific
configurations being pulled into the main development distribution.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

* Use HOMEASSISTANT_TRUSTED_NETWORK (defaults to 192.168.0.0/24)
  variable to define trusted networks in the HomeAssisstant
  configuration.
* Default configuration to autologin when client from
  HOMEASSISTANT_TRUSTED_NETWORK and only one user is available (better
  experience with touchscreen modules).
* Predefine automations setup to include LED control based on human
  presence sensor.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

With the current configuration, the root filesystem can easily get into
an out of space state due to Epiphany downloading Google Safe Browsing
database. This can be more than 200MiB. This change bumps to 500MiB root
free space.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

HomeAssistant depends on this version through its met component. The old
0.5.X version is don't working with the new v2 API.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The old API was deprecated and the met component fails. Update the
component to use the new API. This also has a dependency on
python3-pymetno 0.7.0 and that is brought in by meta-python-dunfellplus
layer.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Update revision to include commits from merge request
OSTC/OHOS/components/smart_home_blueprint_zephyr!14,
that changes BT DIS model name string by changing
the word Sensor to Devie.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>

The -led suffix is inconsistent with every other naming in the
project (i.e. env variable with MAC address, device class in
Home Assistant), so change it to -switch.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>

Update revision to include commits from merge request
OSTC/OHOS/components/smart_home_blueprint_zephyr!13,
that fixes a buffer overflow in BT DIS model name string.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>

Andrei Gherzan authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

The new version includes commit(s) that rename various parts accordingly
to the change to All Scenarios OS.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Wojciech Zmuda authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Zbigniew Bodek authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Use homeassistant-config-blueprint-dashboard
package to install configuration files in the dashboard
blueprint image.

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Andrei Gherzan authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Add recipe for creating HomeAssistant's configuration
for dashboard blueprint.
- Install default configuration files. Currently
  it's only configuration.yaml
- Apply changes in run-time based on build variables

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Zbigniew Bodek authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

The plugin is used by Home Assistant in the Smart Home blueprint scenario
to communicate with IoT sensors and light switchd devices.

Instead of adding smart-home-homeassistant-plugin to installation
packages list, include it via RRECOMMENDS for HomeAssistant.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Wojciech Zmuda authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

The recipe installs Home Assistant custom component for communication
with IoT sensors and light switch devices running All ScenariOS firmware
for the Smart Home blueprint.

The recipe adds entries to HA configuration.yaml file. The entries are
generated with MAC addresses of the expected devices, that are part of
the blueprint setup. They are defined in the relevant blueprint config
file and can be overriden in local.conf.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Wojciech Zmuda authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

This recipe installs a Python library that can be used for
communication over BLE with IoT devices using AllScenariOS
Smart Home firmware.

It is used by Smart Panel Home Assistant plugin.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Andrei Gherzan authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

This inc file is useful so multiple recipes can synchronise on the same
path for the main Home Assistant configuration. For example, a recipe
bringing a custom Home Assistant configuration would use this as the
source of truth for the directory where this configuration needs to
reside. Home Assistant will use the same configuration path at
runtime.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Andrei Gherzan authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

This inc file is useful so multiple recipes can synchronise on the same
user configuration. For example, a recipe bringing a custom Home
Assistant configuration would use this to set the proper user ownership
of the configuration file.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Wojciech Zmuda authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Multiple IoT devices in the Smart Home blueprint are to be
programmed with firmware built from the same sources. That
sources specify MAC address of the BLE interface of the device.
Multiple devices cannot work at once with the same MAC, so in
that case user should have possibility to specify the address
in build time.

Variable SMART_HOME_SWITCH_MAC can be provided to Bitbake.
If detected, its value is used as MAC address for devices
using zephyr-blueprint-smarthome-led image.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Wojciech Zmuda authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Multiple IoT devices in the Smart Home blueprint are to be
programmed with firmware built from the same sources. That
sources specify MAC address of the BLE interface of the device.
Multiple devices cannot work at once with the same MAC, so in
that case user should have possibility to specify the address
in build time.

Variable SMART_HOME_SENSORS_MAC can be provided to Bitbake.
If detected, its value is used as MAC address for devices
using zephyr-blueprint-smarthome-sensors image.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Wojciech Zmuda authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Multiple IoT devices in the Smart Home blueprint are to be
programmed with firmware built from the same sources. That
sources specify MAC address of the BLE interface of the device.
Multiple devices cannot work at once with the same MAC, so in
that case user should have possibility to specify the address
in build time.

Look for `MAC` variable - if set, use its value as MAC address,
substituting the default value in the source code of the firmware.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Wojciech Zmuda authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Smart Panel blueprint sensor and switch devices MAC addrsses have to be:
 - configured on devices so they communicate over BLE from known addresses
   that do not collide,
 - configured in Home Assistant so it knows where to connect to.

Addresses can be overriden in local.conf of Linux build or in command line.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This bundles a rather large rename of all the recipes, descriptions and
comments, with the exception of repositories referenced from gitee or
other third party system (e.g. launchpad PPAs or COPR repositories).

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

To address the "demo" to "blueprint" rename, zephyr-demo-smarthome-base
repository was also renamed accordingly. Reflect this change in the
build recipe.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>