Trim protocol PR to explicit RESP_CODE_ERR handling only

chore/offband-rebrand
Specter242 5 months ago
parent 8a804a3706
commit dc193be8ed

@ -208,8 +208,6 @@ class MeshCoreConnector extends ChangeNotifier {
int? get batteryMillivolts => _batteryMillivolts; int? get batteryMillivolts => _batteryMillivolts;
int get maxContacts => _maxContacts; int get maxContacts => _maxContacts;
int get maxChannels => _maxChannels; int get maxChannels => _maxChannels;
int? get deviceProtocolVersion => _firmwareVerCode;
bool get supportsFloodScope => (_firmwareVerCode ?? 0) >= 8;
bool get isSyncingQueuedMessages => _isSyncingQueuedMessages; bool get isSyncingQueuedMessages => _isSyncingQueuedMessages;
bool get isSyncingChannels => _isSyncingChannels; bool get isSyncingChannels => _isSyncingChannels;
int get channelSyncProgress => int get channelSyncProgress =>
@ -1756,6 +1754,7 @@ class MeshCoreConnector extends ChangeNotifier {
case respCodeCustomVars: case respCodeCustomVars:
_handleCustomVars(frame); _handleCustomVars(frame);
break; break;
// RESP_CODE_ERR is a defined firmware response (code 1), not an unknown frame.
case respCodeErr: case respCodeErr:
_handleErrorFrame(frame); _handleErrorFrame(frame);
break; break;

Loading…
Cancel
Save

Powered by TurnKey Linux.