You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.
I guess we will have a similar discussion as we had with the SerialPort, but I would suggest to remove the serialisation from the main library and put it in the gateway server as an example for others.
The problem is it has a very large dependancy and IMHO this serialisation should be left to the main software and not covered in the library. In my project, the framework already provides libraries for serialising this sort of data, and for embedded systems adding dependancies like this isn't so nice...
What do you think? Is there a better way to handle this? Some sort of callback, or just let the framework populate the devices itself...
I guess we will have a similar discussion as we had with the SerialPort, but I would suggest to remove the serialisation from the main library and put it in the gateway server as an example for others.
The problem is it has a very large dependancy and IMHO this serialisation should be left to the main software and not covered in the library. In my project, the framework already provides libraries for serialising this sort of data, and for embedded systems adding dependancies like this isn't so nice...
What do you think? Is there a better way to handle this? Some sort of callback, or just let the framework populate the devices itself...
Edit: Migrated to https://github.com/zsmartsystems/com.zsmartsystems.zigbee
The text was updated successfully, but these errors were encountered: