We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the case if (command === 'diagnostics' || command === 'enginerpm') { in file onstar2mqtt-bigthundersr-vehicle1/src/index.js there is no
if (command === 'diagnostics' || command === 'enginerpm') {
onstar2mqtt-bigthundersr-vehicle1/src/index.js
client.publish( commandStatusTopic, JSON.stringify({ "command": { "error": { "message": "Completed Successfully", "response": { "status": 0, "statusText": "Completed Successfully" } } }, "completionTimestamp": completionTimestamp }), { retain: true } );
like there is for other commands. This leaves the status topic stuck at 'sent'
The text was updated successfully, but these errors were encountered:
@metheos, thanks for catching this!
Sorry, something went wrong.
Fix for #208
f0f8c3f
Merge pull request #215 from BigThunderSR/208-when-sending-diagnostic…
1bde11f
…s-command-there-is-no-completed-sucessfully-published-to-the-command-status-topic Fix for #208
BigThunderSR
Successfully merging a pull request may close this issue.
In the case
if (command === 'diagnostics' || command === 'enginerpm') {
in fileonstar2mqtt-bigthundersr-vehicle1/src/index.js
there is nolike there is for other commands. This leaves the status topic stuck at 'sent'
The text was updated successfully, but these errors were encountered: