From 082bd9694e23f891eddbb2516cee7e5fe0269400 Mon Sep 17 00:00:00 2001 From: Scott Murray Date: Mon, 5 Oct 2020 17:03:30 -0400 Subject: Fix frequency verb invalid frequency behavior The frequency verb was not checking if a frequency corresponds to the frequency band step the binding provides to users, add logic to do so and return an error if the frequency is invalid. While this is a change in behavior, it is believe it should not impact users, as the binding is intended to reflect user facing radio application usage. Additional tweaks: - fix error invalid frequency error message in reply JSON. - add the same band limit checks to the null implementation's frequency setting function that the other implementations do. - fix a couple of issues in README.md; the "rds" verb was missing, and the value key name for the "frequency" event was incorrect. Bug-AGL: SPEC-3620 Signed-off-by: Scott Murray Change-Id: I2adfc10448546264110f6d854f02d677087f1e47 (cherry picked from commit 8958a8a3e98085c60c9cd803395be157e78e3565) --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 2155649..90184b7 100644 --- a/README.md +++ b/README.md @@ -21,12 +21,13 @@ respective audio stream. | scan_start | start scanning for station | *Request:* {"direction": "forward" or "backward"} | | scan_stop | stop scanning for station | | | stereo_mode | get/set stereo or mono mode | *Request:* {"value": "stereo" or "mono"} | +| rds | get current RDS data | | ## Events ### frequency Event JSON Response -JSON response has a single field **frequency** which is the currently tuned frequency. +JSON response has a single field **value** which is the currently tuned frequency. ### station_found Event JSON Response -- cgit 1.2.3-korg