diff options
author | minix1234 <48591487+minix1234@users.noreply.github.com> | 2020-06-12 09:03:30 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-06-12 09:03:30 -0400 |
commit | 70f60fcd8a20c1f0046fae0c83f1ce50d78c951a (patch) | |
tree | 514512d74e7c970badcd528882a426bfab388f7a | |
parent | 19a7bd496975a61fdc43003bc35ac1e65f7ed1d6 (diff) |
Updated activity_monitor.c - metadata publishing wrong codes
Found that MQTT activity_start: abeg and activity_end: aend topics where never being published. instead immediately after a play session started a play_end: pend topic was sent. Also after the activity_timout a duplicate play_end was received.
This commit fixes those bugs.
-rw-r--r-- | activity_monitor.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/activity_monitor.c b/activity_monitor.c index ce7edc5..735fd03 100644 --- a/activity_monitor.c +++ b/activity_monitor.c @@ -62,7 +62,7 @@ void going_active(int block) { command_execute(config.cmd_active_start, "", block); #ifdef CONFIG_METADATA debug(2, "abeg"); // active mode begin - send_ssnc_metadata('pend', NULL, 0, 1); // contains cancellation points + send_ssnc_metadata('abeg', NULL, 0, 1); // contains cancellation points #endif #ifdef CONFIG_DBUS_INTERFACE @@ -89,7 +89,7 @@ void going_inactive(int block) { command_execute(config.cmd_active_stop, "", block); #ifdef CONFIG_METADATA debug(2, "aend"); // active mode end - send_ssnc_metadata('pend', NULL, 0, 1); // contains cancellation points + send_ssnc_metadata('aend', NULL, 0, 1); // contains cancellation points #endif #ifdef CONFIG_DBUS_INTERFACE |