diff --git a/Talegent/Talegent__Vitality_1KS__blazer_ser__2.8.3.64__01.dev b/Talegent/Talegent__Vitality_1KS__blazer_ser__2.8.3.64__01.dev
new file mode 100644
index 0000000..7cdf009
--- /dev/null
+++ b/Talegent/Talegent__Vitality_1KS__blazer_ser__2.8.3.64__01.dev
@@ -0,0 +1,55 @@
+# DEVICE:URL:REPORT: https://github.com/networkupstools/nut/issues/2923
+
+# DEVICE:COMMENT
+# I tested both NUT2.7.4 and NUT2.8.3.64, 
+# and they can both read the UPS status normally and
+# control the UPS devices properly, such as shutting down.
+#
+# MAINTAINER NOTE: Initial contribution had broken markup; it is
+# possible that fixing attempts lost some data near output.voltage
+# and/or that some data points were not even posted originally.
+# DEVICE:EOC
+
+# DEVICE:COMMENT-BLOCK: Driver configuration
+# :; cat /etc/nut/ups.conf
+#
+# [myups]
+#      driver = blazer_ser
+#      port = /dev/ttyCH341USB0
+#      desc = "My UPS"
+# DEVICE:EOC
+
+battery.charge: 100
+battery.voltage: 45.00
+battery.voltage.high: 39.00
+battery.voltage.low: 31.20
+battery.voltage.nominal: 36.0
+device.mfr: 222222222222222
+device.model: 2222222222
+device.type: ups
+driver.debug: 6
+driver.flag.allow_killpower: 0
+driver.name: blazer_ser
+driver.parameter.pollinterval: 2
+driver.parameter.port: /dev/ttyCH341USB0
+driver.parameter.synchronous: auto
+driver.state: dumping
+driver.version: 2.8.3.64-64+g72fbc5801
+driver.version.internal: 1.63
+input.current.nominal: 4.0
+input.frequency: 49.9
+input.frequency.nominal: 50
+input.voltage: 235.7
+input.voltage.fault: 0.0
+input.voltage.nominal: 230
+output.voltage: 230.4
+ups.beeper.status: enabled
+ups.delay.shutdown: 30
+ups.delay.start: 180
+ups.firmware: R1.00.48
+ups.load: 13
+ups.mfr: 222222222222222
+ups.model: 2222222222
+ups.status: OL
+ups.temperature: 55.0
+ups.type: online