diff --git a/meshtastic/admin.proto b/meshtastic/admin.proto
index 6bf7d06..e629a87 100644
--- a/meshtastic/admin.proto
+++ b/meshtastic/admin.proto
@@ -114,6 +114,11 @@ message AdminMessage {
      * TODO: REPLACE
      */
     NEIGHBORINFO_CONFIG = 9;
+
+    /*
+     * TODO: REPLACE
+     */
+    AMBIENTLIGHTING_CONFIG = 10;
   }
 
   /*
diff --git a/meshtastic/mesh.proto b/meshtastic/mesh.proto
index 0e11d86..85ba046 100644
--- a/meshtastic/mesh.proto
+++ b/meshtastic/mesh.proto
@@ -305,6 +305,11 @@ enum HardwareModel {
    */
   NANO_G1_EXPLORER = 17;
 
+  /*
+   * B&Q Consulting Nano G2 Ultra: https://wiki.uniteng.com/en/meshtastic/nano-g2-ultra
+   */
+  NANO_G2_ULTRA = 18;
+
   /*
    * B&Q Consulting Station Edition G1: https://uniteng.com/wiki/doku.php?id=meshtastic:station
    */
@@ -745,9 +750,9 @@ message MeshPacket {
    * to make sure that critical packets are sent ASAP.
    * In the case of meshtastic that means we want to send protocol acks as soon as possible
    * (to prevent unneeded retransmissions), we want routing messages to be sent next,
-   * then messages marked as reliable and finally ‘background’ packets like periodic position updates.
+   * then messages marked as reliable and finally 'background' packets like periodic position updates.
    * So I bit the bullet and implemented a new (internal - not sent over the air)
-   * field in MeshPacket called ‘priority’.
+   * field in MeshPacket called 'priority'.
    * And the transmission queue in the router object is now a priority queue.
    */
   enum Priority {
@@ -1457,4 +1462,4 @@ message DeviceMetadata {
    * Has Remote Hardware enabled
    */
   bool hasRemoteHardware = 10;
-}
\ No newline at end of file
+}