bird Max Plus S5 (IoT Connectivity) settings-parse fix: devices sending the documented 6-field S5 response no longer disconnect. New setting fields exposed - S6 upload interval when unlocked and when turned on - and the S6 upload switch is now the full 1-4 mode enum.
bird Bugfix in U5 (Start Update) setting for emoped_c: check_code field is now required for Vehicle Firmware and Audio File updates
bird segway-ninebot Fixed Q0 sign-in packet parsing: a repeated Q0 on an open connection dropped the connection instead of being parsed. Q0 now also reports gsm.operator.code, gsm.mcc, gsm.mnc and software.version on that path. Bugfix: the Q0 signal field was reported as gsm.signal.quality (bit error rate) on that path; it is a signal strength value and is now reported as gsm.signal.level, matching the rest of the protocol.
bird New setting option added for segway_3rd_gen: Voice package (type1=3) with audio index selection in U5 Start upgrade setting.
bird segway-ninebot Bugfix: total.driving.time now reports total ride time in seconds, as documented. Previously the value was divided by 60, reporting minutes - readings from S6 status packets will be 60x larger from now on.
namo Segway-ninebot protocol is updated: changed processing of U2 Firmware upgrade result packet: firmware_upgrade command is finished only if FW Upgrade Device Type of the command matches that in the U2 report channel message of type U2 is stored
bird Fixed C0 battery lock reply handling for segway_3rd_gen, max_plus_x and a200: failed replies no longer update battery.lock.status, and C0 replies no longer complete unrelated pending commands.
bird Bugfix: commands and settings now complete only on the device reply to the instruction they sent. Unsolicited replies (e.g. M0/I0 after login, local L0/L1 lock reports, P2, M1) no longer complete unrelated pending commands.
bird Fixed max_plus M1 serial replies: device.serial.number now holds only the vehicle SN and the BMS SN is stored in bms.serial.number (previously both were combined in device.serial.number). M3 replies now store device.serial.number and bms.serial.number.1-.3.
