Use T4 template for generating zpi and zcl code about zigbeenet HOT 4 CLOSED

As we implement it by hand I suggest we could close this Issue.

from zigbeenet.

Please use same names in types as the API has. This makes it easier to follow.

from zigbeenet.

I tought about the whole concept of commands and now i am at the point I would say that the current solution is not very well. Also T4 templates. Instead of using JSON definitions we should use own classes for each request and response. And these classes should be inherited from an base class (e.g. SerialPacket)

So I' thinking about removing ZpiObject, ZpiSREQ, ZpiMeta and the json files.

The sending and reading methods are already a good solution and should be further used

@nicolaiw
What do you think?

from zigbeenet.

I created a new branch rework with commit 8c31c81

I removed all ZpiObject classes and created Packet Directory in which classes with correct names are contained. This commit was the first step and just nine classes are implemented to start the Hardware and starts PermitJoin. On my machine the Example it is running:

[07:44:07 DBG] Opening interface...
[07:44:08 DBG] Interface opened...
[07:44:08 INF] Application started
[07:44:08 DBG] Transmitted: SubSystem: SAPI, Type: SREQ, Length: 0, Cmd: 0
[07:44:10 DBG] Paket read: SubSystem: SAPI, Type: SRSP, Length: 0, Cmd: ZB_START_REQUEST_RSP
[07:44:10 DBG] Paket read: SubSystem: ZDO, Type: AREQ, Length: 1, Cmd: ZDO_STATE_CHANGE_IND
[07:44:10 INF] State changed: Started_as_ZigBee_Coordinator
[07:44:10 DBG] Transmitted: SubSystem: ZDO, Type: SREQ, Length: 0, Cmd: 0
[07:44:10 DBG] Paket read: SubSystem: ZDO, Type: SRSP, Length: 1, Cmd: ZDO_MGMT_PERMIT_JOIN_REQ_SRSP
[07:44:10 DBG] Paket read: SubSystem: ZDO, Type: AREQ, Length: 3, Cmd: ZDO_MGMT_PERMIT_JOIN_RSP

Code is not yet perfect, but i need to have some sleep. More will come soon

from zigbeenet.