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
DeviceFactory is very limited, as it is based exclusively on the message attribute keys (TEMP, WIND, HUM, SWITCH, CMD...)
It can NOT handle complex algorithm, or even take advantage of the message protocol.
Therefore, input RTS messages from the bridge can NOT be mapped to a RTS device, as the discriminant is not a message attribute key, but the attribute protocol.
Moreother, the current implementation is buggy (HUMIDITY & TEMP Devices are never created, OregonTempHygro is instantiated instead).
DeviceFactory should be improved to use the whole Message.
The text was updated successfully, but these errors were encountered:
DeviceFactory is very limited, as it is based exclusively on the message attribute keys (TEMP, WIND, HUM, SWITCH, CMD...)
It can NOT handle complex algorithm, or even take advantage of the message protocol.
Therefore, input RTS messages from the bridge can NOT be mapped to a RTS device, as the discriminant is not a message attribute key, but the attribute protocol.
Moreother, the current implementation is buggy (HUMIDITY & TEMP Devices are never created, OregonTempHygro is instantiated instead).
DeviceFactory should be improved to use the whole Message.
The text was updated successfully, but these errors were encountered: