You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ookSwitch function sometimes returns a non-zero value when there were messages in the Rx buffer when called. This is not documented very well. For example mqtt-energenie-ener314rt (before v0.5) checked for non-zero return code, and logs an error if non-zero. This is believed to be the dodgy code:
/*
** flush Rx buffer if required
*/
ret = empty_radio_Rx_buffer(DT_CONTROL);
The text was updated successfully, but these errors were encountered:
Achronite
added a commit
to Achronite/mqtt-energenie-ener314rt
that referenced
this issue
Aug 11, 2023
Extensive rewrite of logging in application which is now configurable.
Fixed a bug where the target switch state sometimes fails to be updated in MQTT for OOK devices due to a bug in dependency [energenie-ener314rt#32](Achronite/energenie-ener314rt#32)
Fixed a bug where a stack trace was sometimes output for MQTT connection when exiting application
The record count is used in openthings_scan() to return messages before timeout reached. So the solution should be to change ookSwitch to ignore record count
The ookSwitch function sometimes returns a non-zero value when there were messages in the Rx buffer when called. This is not documented very well. For example mqtt-energenie-ener314rt (before v0.5) checked for non-zero return code, and logs an error if non-zero. This is believed to be the dodgy code:
The text was updated successfully, but these errors were encountered: