Automate Opto22 groov View Public
HumDay reads Opto22 groov View Public’s own published API description and derives 10 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Opto22 groov View Public is
#### Revised: 2019-11-21 ### Overview groov View Public API revision 1.
What HumDay can do in Opto22 groov View Public
2 documented operations change something in Opto22 groov View Public.
- POSTWrites a new value to the given tag.
/v1/data-store/write/{id} - POSTRead selected tags from the data store.
/v1/data-store/read
What HumDay can read from Opto22 groov View Public
These are the operations a schedule or a trigger can watch.
- GETGet information about the user you are authenticated as.
/whoami - GETList all data store tags defined in the project.
/v1/data-store/tags - GETList devices available in the data store.
/v1/data-store/devices - GETGet information about groov View.
/info - GETList tags of the given device.
/v1/data-store/devices/{id}/tags - GETDownloads the complete groov View log.
/v1/logging/groovLogs.txt - GETDownloads the complete groov View log in JSON format.
/v1/logging/groovLogs.json - GETRead the current value of a single tag.
/v1/data-store/read/{id}
How automating Opto22 groov View Public works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Opto22 groov View Public account.
- Grant access, then go live. You approve the specific Opto22 groov View Public operations it may use — and only those.
Automate Opto22 groov View Public with these
- Opto22 PAC Control55 operations
- Gambitcomm MIMIC356 operations
- Meraki Dashboard263 operations
- ClearBlade220 operations
- Influxdata Influx OSS197 operations
- Intellifi Brain77 operations
- Adafruit IO71 operations
- Ijenko IoE² IoT to create end user applications67 operations
- smart me64 operations
- KeyServ24 operations
- Hardware Sentry TrueSight Presentation Server23 operations
- Netatmo19 operations
Categories
Questions about Opto22 groov View Public automation
- Can HumDay connect to Opto22 groov View Public?
- Yes. HumDay reads Opto22 groov View Public's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 10 operations are documented.
- Do I need to write code to automate Opto22 groov View Public?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Opto22 groov View Public account.
- What can HumDay do in Opto22 groov View Public?
- 2 of the 10 documented operations change something in Opto22 groov View Public, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Opto22 groov View Public account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Opto22 groov View Public is held behind that approval.
Where this came from
The operations above are read from a published API description for Opto22 groov View Public at developer.opto22.com/static/generated/groov-rest-api/swagger.yaml. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.