As you can see the git action format did a format on lib/injection.config.dart https://github.com/CyBear-Jinni/cbj_hub/pull/181/commits/b66e3c137c19a185ffec6c4f320371369169a7ec

injection.config.dart is autogenerated file and thus should not get formatted.

Please change git action dart format so that it will ignore lib/injection.config.dart

https://github.com/CyBear-Jinni/cbj_hub/blob/4e84ecab6be5570a05d0520200c348956187950d/.github/workflows/format.yml#L29

Should become

find . -name "*.dart" ! -path '*/gen/*' ! -name 'injection.config.dart' | tr '\n' ' ' | xargs dart format

Tuya devices are popular option when its come to smart devices. It is one of the most used smart devices in Home Assistant with 14.4% of its users using it. So adding support for that takes priority.

Please change the social media icons to be the same as the one in the bottom of this readme

https://github.com/CyBear-Jinni/cbj_app/blob/dev/README.md

ESPHome is a system to control your ESP8266/ESP32 by simple yet powerful configuration files and control them remotely through Home Automation systems. I think ESPHome is owned by Home Assistant. Percent of users in Home Assistant is 17.5

#175 I've updated the dependencies to the latest version without any dependencies issues constraints. There is some dependency that I've not updated because another dependency depends on their lower versions. So it'll create a major problem in version solving.

In the readme file we are missing NodeRed installation instructions + link.

Please add node-red instructions under the MQTT with the following link

NodeRed link: https://snapcraft.io/node-red

MQTT broker link: https://snapcraft.io/mosquitto

The end result should look like this (with links)

To run the hub you will also need MQTT broker as well as NodeRed.

Currently we scan all the time each vendor that we support.

This is not so efficient as it is a lot of unnecessary scans as most homes do not contain all the vendors that we support. And our vendor's support will only grow larger and with it the inefficiency of scanning all of them.

There are a number of smart devices that support mDNS protocols. My suggestion is to scan all the mDNS devices in the network and activate specific devices vendor scan for serviceType that corresponds to this vendor.

This way we will activate only vendors that exist in the user local network.

The Hub got built around the concept of MQTT in order to use tools like Node-RED to its advantage.

Node-RED is a programming tool for wiring together hardware devices, APIs and online services in new and interesting ways.

It provides a browser-based editor that makes it easy to wire together flows using the wide range of nodes in the palette that can be deployed to its runtime in a single-click.

Node-RED is full of features and has a pretty good graphical user interface.

Let's create an integration layer with Node-RED to control and change nodes inside of it.

1. The Hub will be able to use it to control and manage nods for scenes, control devices, routines, bindings.
   #18
2. Will grant the user option to see visually his scenes, routines, bindings.
3. Will grant the user the option to create complicated scenes, routines, bindings by using the Node-RED GUI interface.
4. You can download nodes in Node-RED that will grant us more functionality like interacting with alexa skills or nodes to "communicate with Sonoff Smart Switch devices on LAN" which will add support for more devices automatically for us.

Currently smart plugs and touch switches are the same for the hub.

Tuya API response includes both devType and haType but they are both switch types which I think is a bug in their API. The only differentiate that I have found in the response of the device is the attached image URL of the device but this is not a good way to distinguish between the devices.

After 10m the connection to the remote pipes time out with the error

⛔ Client stream error: gRPC Error (code: 2, codeName: UNKNOWN, message: HTTP/2 error: Connection error: Connection is being forcefully terminated. (errorCode: 10), details: null, rawResponse: null, trailers: {})

Shelly is a big player in the smart home system. In Home Assistant 12.7% of its users use it. Shelly suppose to have cloud API so it does not need to be so hard to add support for it, but local control is preferred if exists any.

When trying to run the same code that works but this time on my arm device it looks like the python packages are not installed.

My hypothesis is that Dart python_shell package have a timeout for installing a python packages and so when running inside the virtual environment after initialization the python package is not installed even though we have added it in needed dependencies.

Tested outside of snap with the original example from python_shell Dart package and it is not working.

Matter i a new IOT standart developed with corporation of big companies like Google Amazon Apple and more.

It just got support under Home Assistant using the python package python-matter-server and have 1095 active users.

Formerly Project named CHIP, worked on by a group named Connectivity Standards Alliance.

GitHub link

After running the hub for several hours on my arm device I got this exception.

Unhandled exception:
SocketException: Failed to create datagram socket (OS Error: Too many open files, errno = 24), address = , port = 5353
#0      _NativeSocket.bindDatagram (dart:io-patch/socket_patch.dart:1015:7)
<asynchronous suspension>
#1      MDnsClient.start (package:multicast_dns/multicast_dns.dart:135:40)
<asynchronous suspension>
#2      MdnsScanner._findingMdnsWithAddress (package:network_tools/src/mdns_scanner/mdns_scanner.dart:72:5)

I think increasing the delay between mdns searches will fix that.

We are currently moving back from Isar to hive as it currently does not support Linux arm architecture.

Let's keep track of this and make the move to Isar whenever it is resolved as it is better than hive.

Linking the issue to add Linux arm architecture support for Isar: https://github.com/isar/isar/issues/848