shifu
shifu copied to clipboard
Edgenesis
Kubernetes-native IoT gateway
**What this PR does / why we need it**: Remove redundant code and Imeplement socket end by char **Will this PR make the community happier**? yes **Which issue this PR...
**Describe the bug** A clear and concise description of what the bug is. deviceshifu crash when using socket for it's telemtrySettings is omit **To Reproduce** Steps to reproduce the behavior:...
**Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. ... 2. ... 3. ... 4. ... **Expected behavior**...
**What this PR does / why we need it**: This PR contains design for constomized deviceShifu. Customed deviceShifu will enable deviceShifu to handle customized logic such as parsing data from...
**What this PR does / why we need it**: Improve README to make it more intuitive. Before this PR, README is a little bit confusing. This PR should give readers...
Some of the device return not only a single message, but multiple messages for a single command e.g. > Calibrate Calibrate started (10 seconds later) Calibrate finished
Currently after issuing a reboot request and socket is closed from device end, the socket does not get reopened, and subsequent requests has error.
When sending command using /cmd route, we need to add configuration that the device uses non-default \n separator for a message
OPC UA's deviceshifu will always reconnect to the device many times when device is reboot, until delete the deviceshifu