-
This came up during planning. When reading all devices, the GUID is in the reading, but not info / context / type.
We should have enough information in the reading so that when we curl read to read…
-
PR coming. Saves round trips versus the HVAC.
-
The connectivity to the Edens UPS is very poor right now. Even snmpwalk gives up with a timeout.
Problems:
The SNMP plugin cannot read data and cannot initialize correctly.
The plugin does not fa…
-
Something is odd with the modbus plugin. We're not reading values where we should be.
Synse read:
```
ubuntu@w1:~$ export SYNSE_IP=10.42.4.226
ubuntu@w1:~$ curl http://${SYNSE_IP}:5000/v3/read/0…
-
when using this image as part of the test setup for the synse snmp plugin (where this emulator was originally defined), the emulator failed to work, causing test failures.
i'll need to circle back …
-
the test stage in CI has been disabled temporarily, as the CI pipeline in the v3 branch was updated to use the newer jenkins setup where agents are run in k8s. That change doesn't allow the same docke…
-
We saw this at Wrigley yesterday. Prod repro is consistent.
if one EGauge (modbus TCP device) is not configured correctly (or does not respond), they all bomb since the plugin falls over.
I was …
-
After doing some quick comparisons of throughput/latency tests between synse v2 and synse v3, it appears that v3 has a bit higher latency. this could be due to a number of things, one of which being…
-
Its unclear whats happening. Parsing through the logs, it finds 9 plugins including egauge via service endpoints discovery. Then, it only ends up registering a total of 8. For some reason, the egauge…
-
The current approach to plugin refresh is fairly naive. Synse notes that a plugin failed a request and marks it inactive. Later (either on a timer or when forced by user), it will attempt to reconnect…