Share your feedback...
API and its Documentation
Some additional info and updates to the api and api docs would be great. changing "organisationId" to "orgid" would avoid the spelling issue as well as capitalization mistakes. via ( https://blog.dreamfactory.com/best-practices-for-naming-rest-api-endpoints/ ) Use Lowercase Letters: Whenever possible, use lowercase letters in your API URLs. This is mainly because the RFC 3986 Specification For URI Standards denotes that URIs are case-sensitive (except for the scheme and host components of the URL). Lowercase letters for URIs are in widespread use, and also help avoid confusion about inconsistent capitalization. If you add capital letters, you should be aware that this will cause confusion and result in user error more often than not.
Control Log Reporting
This feature would allow you as grower to see summarised reports of your control actions. I would also be possible to overlay automation actions on measurement graphs which would show pH for example responding to a dose. Also for example you could get total pump run times or total doses delivered over a period of time. Let us know if this is important to you and what else would be useful in this space?
Add full task management functionality to Edenic. This would include: -Journal and tasks calendar view -Ability to create journal and task templates -Schedule your people to certain tasks -Task reminders -Daily tasks lists -Record details for completed tasks. -Task reporting Tell us about how you would use this feature. Is this important to you?
Automated pH up or down (Pro controller)
Add ability to control pH to a range and automatically change from pH up to pH down (or vice versa) as required. This would only work from Edenic (not configurable on the device). This would also only be for Pro Controller as this requires multiple pumps. The pH range would also need to be wide enough to avoid pH up and down solutions 'fighting' each other. Is this important to you?
See calibration status, date of last calibration, points of calibration and the mV & temperature at calibration.
Crop cycle scheduling
This feature would allow you as grower to schedule changes to your system as you crop progresses. You will be able to choose a start and end date for the schedule and break this schedule up into multiple periods with different settings. Settings that could be changed would include (set points, on and off times, alarm settings and pump ratios) Tell us what you think about this feature and how important this is to you
Add MQTT publishing for BGPGuardian
MQTT is a standard for IoT devices to publish their data in an open and simple method. Adding this to the BGPGuardian device would allow external third-party software to utilise data from the BGPGuardian device.
SMS / Email Alerts
Currently alerts and alarms are delivered as push notifications to your mobile device. How else would you like to receive notifications. Would SMS or email be interesting to you? Let us know.
Interfacing with 3rd party hardware
Would you like to have devices from other supplier data showing in Edenic. This could be a climate monitoring device or any other device that generates data in your growing environment. Is this something you want? If so what would you like to integrate?
As a grower you will be able to define crop batches that are currently growing. Or perhaps future batches. You would then be able to record all data against a particular batch to track the conditions for the batch through the life cycle. Is important for you? Would you like to be able to do this in Edenic? What details are important for you?