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