-
https://github.com/vapor-ware/synse-server/blob/6650dbcbc28150957106f04155b7f88e9c2f7e41/synse/plugin.py#L126-L127
the address it uses here is the same as is given to the client.. instead of requir…
-
The emulator seemingly takes these devices as shallow clones of the same device. Effecting change in state on a LED color or Lock state will alter every lock in the wedge/chamber in initial testing wi…
-
the SDK should be able to provide basic conversion capabilities, e.g. deg. C deg F.
See: https://github.com/vapor-ware/synse-modbus-ip-plugin/pull/16#issuecomment-431363145
TBD how this will b…
-
we currently have the `/test` endpoint to test whether synse server is reachable or not, but it seems like there are other measures of health that could be good to expose, e.g.
- are all configured…
-
We can id modbus devices by ip and port.
When we need to read registers that are sequentially addressed, we can perform those reads in one round trip and unpacking the results. This will help from ov…
-
auto_fan will need these, likely other components as well. (Turntable)
-
On a fresh deploy of synse-server, logs will fail with tracebacks due to Forbidden errors from API
```
[2018-11-01 08:52:32 +0000] - (synse)[DEBUG] scan:31: Re-registering plugins
[2018-11-01 08:…
-
## Description
We have a stub in place for the lock route in v2.0
Once I understand how the backend plugin looks and what data it requires from Synse Server, can update as needed and then create t…
-
there is a stub in place for the lock route that will need to be filled out. it should more or less follow the pattern of other alias routes. once that is done, we can address #72
-
## Description
We used to get all devices on a scan.
Now we get partial scan results as the containers come up.
At least for testing purposes it would be good to know when / if scan has found a…