Tuya WiFi Smart Plug - Revision history

Leo: /* Usage with stock Tuya firmware */

2020-06-15T23:22:21Z

Usage with stock Tuya firmware

← Older revision		Revision as of 23:22, 15 June 2020
Line 1:		Line 1:
	Tuya ~~has some~~ cheap ~~WiFi capable~~ smart plugs ~~which you can~~ control ~~remotely using your~~ phone. ~~These smart plugs will need~~ to talk ~~with Tuya~~'s ~~servers in order~~ to ~~work~~. There are ~~alternative firmware~~ that can be loaded ~~over the air (OTA)~~ on ~~the device~~.		Tuya is a Chinese IOT company that creates many cheap smart devices including plugs, light bulbs, and switches. These smart devices connect to the cloud out of the box and lets the user easily control the device with their phone or a smart speaker. Some of these smart devices are sold under other brands from 3rd party resellers but uses the same underlying cloud infrastructure. The IoT device interacts with the cloud via HTTP and MQTT.

			As these devices are always connected to the cloud, there are a few reasons to be wary of these IoT devices. As described by the 35c3 talk, risks include: the data that's collected by the company on your usage, the security of the data that's collected, and the ability for a malicious party to upload a trojaned firmware which can tunnel into your private network or access the internet via your device. The talk can be found at [https://media.ccc.de/v/35c3-9723-smart_home_-_smart_hack#l=eng&t=2093 https://media.ccc.de/v/35c3-9723-smart_home_-_smart_hack]

			There are alternate opensource firmwares that can be loaded on these smart devices which will be discussed below.

	==Usage with stock Tuya firmware==		==Usage with stock Tuya firmware==
	The stock firmware requires setup with the Tuya app or with TuyAPI in combination with the Tuya Cloud. There is no way to set up the device without having it connect to Tuya's servers. If this is a concern, skip to the ~~Tuya-Convert~~ section ~~below~~ to change the stock firmware.		The stock firmware requires setup with the Tuya app or with TuyAPI in combination with the Tuya Cloud. There is no way to set up the device without having it connect to Tuya's servers. If this is a concern, skip to the next section to learn how to change the stock firmware.

	As part of the initial set up, a randomized AES key ~~is generated~~ and is ~~shared with Tuya's servers. Your phone's SmartLife app also obtains~~ this key ~~when you log in~~.		As part of the initial set up, after the WiFi credentials are shared with the smart device, the device will communicate with the Tuya Cloud to register itself via HTTP/HTTPS. Once registered, Tuya will send a randomized AES key to both the device and your phone. From this point on, communication to the device is done via MQTT or HTTP using this AES key.

	The following three pieces of information is required to control a device using the Tuya firmware.:		The following three pieces of information is required to control a device using the Tuya firmware.:
Line 13:		Line 17:

	[[File:Tuya Cloud Development.png\|thumb\|right\|Tuya Cloud Development API Key]]		[[File:Tuya Cloud Development.png\|thumb\|right\|Tuya Cloud Development API Key]]
	Retrieving this AES key after the initial set up has been difficult (as of 2020) because traffic between the plugs and Tuya are encrypted; traffic between Tuya and the SmartLife app is encrypted and SSL interception isn't possible; and the data stored by the SmartLife app is also encoded or encrypted. If you wish to obtain the AES key, the only method I had success with was to use the TuyAPI project.		Retrieving this AES key after the initial set up has been difficult (as of 2020) because traffic between the plugs and Tuya are encrypted; traffic between Tuya and the SmartLife app is encrypted and SSL interception isn't possible; and the data stored by the SmartLife app is also encoded or encrypted. If you wish to obtain the AES key, the only method I had success with was to use the TuyAPI project. Alternatively, you could use the <code>esptool.py</code> utility to dump the flash and recover the localKey.

	The TuyAPI project has instructions on obtaining the AES key at https://github.com/codetheweb/tuyapi/blob/master/docs/SETUP.md. After obtaining the tuya-cli tool, you will need to obtain a Cloud Development Project API key from Tuya which is required to register the device and obtain the AES key when the device is set up.		The TuyAPI project has instructions on obtaining the AES key at https://github.com/codetheweb/tuyapi/blob/master/docs/SETUP.md. After obtaining the tuya-cli tool, you will need to obtain a Cloud Development Project API key from Tuya which is required to register the device and obtain the AES key when the device is set up.
Line 39:		Line 43:
	#The JSON message is then encrypted using AES ECB using the 128bit AES localKey.		#The JSON message is then encrypted using AES ECB using the 128bit AES localKey.
	#A MD5 hash of {{code\|1=data=$Cyphertext{{!}}{{!}}pv=2.1{{!}}{{!}}$LocalKey}} is computed.		#A MD5 hash of {{code\|1=data=$Cyphertext{{!}}{{!}}pv=2.1{{!}}{{!}}$LocalKey}} is computed.
	#The final message ~~concats~~ {{code\|"2.1" + MD5[8, 24] + $CypherText}}		#The final message concatenates {{code\|"2.1" + MD5[8, 24] + $CypherText}}

	A message payload sent to the Tuya plug looks something like the following		A message payload sent to the Tuya plug looks something like the following
Line 55:		Line 59:
	}		}
	<nowiki>}</nowiki>		<nowiki>}</nowiki>
	}		<nowiki>}</nowiki>
	}}		}}

Line 132:		Line 136:

	==Flashing Tasmota with Tuya-Convert==		==Flashing Tasmota with Tuya-Convert==
	~~See~~ the project website at https://github.com/ct-Open-Source/tuya-convert.		Read more from the project website at https://github.com/ct-Open-Source/tuya-convert. I suggest watching the talk [https://media.ccc.de/v/35c3-9723-smart_home_-_smart_hack#l=eng&t=2093 https://media.ccc.de/v/35c3-9723-smart_home_-_smart_hack] on for more information on how the Tuya-Convert script works.

	The Tuya-Convert project simplifies the flashing of the Tuya smart plugs. It turns a Linux computer with a wireless adapter into an access point along with all the necessary services (DNS, HTTP, MQTT) to fake an update server. ~~Once running,~~ a Tuya device ~~in setup~~ mode will ~~automatically be found and flashed~~. Tuya-Convert ~~supports flashing~~ either Espurna or Tasmota~~, both~~ are custom open source firmware with excellent sets of features. Tasmota appears to be more popular and active and is what I am using.		The Tuya-Convert project simplifies the flashing of the Tuya smart plugs. It turns a Linux computer with a wireless adapter into an access point along with all the necessary services (DNS, HTTP, MQTT) to fake an update server. When a Tuya device enters Smart Config mode, it will listen for WiFi credentials by a UDP broadcast. The Tuya-Convert script will broadcast the WiFi credentials and initiate a firmware update to an intermediate firmware. Once the device comes online using this intermediate firmware, you can flash the device firmware with either Espurna or Tasmota. Both are custom open source firmware with excellent sets of features, though Tasmota appears to be more popular and active and is what I am using.

	To get Tuya-Convert running as a container in Docker, you will need a computer running Linux with Docker and Docker Compose installed. Clone the Tuya-Convert project and build the docker image with the provided Dockerfile. Create a new directory to work from and copy the example {{code\|docker/docker-compose.yml}} file there. The only thing that you need to edit is the wireless adapter device. Leave the vtrust-flash AP alone. The container will run in privileged mode and will have direct access to the wireless adapter. Depending on the system you're using, you may need to disable NetworkManager because it may try to reconnect you to a known network when the container attempts to create an access point. Disabling the firewall might be necessary to ensure the services spun up within the container are visible.		To get Tuya-Convert running as a container in Docker, you will need a computer running Linux with Docker and Docker Compose installed. Clone the Tuya-Convert project and build the docker image with the provided Dockerfile. Create a new directory to work from and copy the example {{code\|docker/docker-compose.yml}} file there. The only thing that you need to edit is the wireless adapter device. Leave the vtrust-flash AP alone. The container will run in privileged mode and will have direct access to the wireless adapter. Depending on the system you're using, you may need to disable NetworkManager because it may try to reconnect you to a known network when the container attempts to create an access point. Disabling the firewall might be necessary to ensure the services spun up within the container are visible.
Line 221:		Line 225:
	{"NAME":"Teckin SP25","GPIO":[56,255,255,255,255,255,0,0,22,17,255,21,255],"FLAG":1,"BASE":18<nowiki>}</nowiki>		{"NAME":"Teckin SP25","GPIO":[56,255,255,255,255,255,0,0,22,17,255,21,255],"FLAG":1,"BASE":18<nowiki>}</nowiki>
	}}		}}

	* AWP04L: {{highlight\|lang=text\|code=		* AWP04L: {{highlight\|lang=text\|code=
	{"NAME":"AWP04L","GPIO":[57,255,255,131,255,134,0,0,21,17,132,56,255],"FLAG":0,"BASE":18<nowiki>}</nowiki>		{"NAME":"AWP04L","GPIO":[57,255,255,131,255,134,0,0,21,17,132,56,255],"FLAG":0,"BASE":18<nowiki>}</nowiki>
Line 227:		Line 232:
	The plugs I've set up also have WIfiManager disabled (so that it will not enter configuration mode when it fails to connect). MQTT is enabled with the topic set to the device name and the master topic set to {{code\|tasmota/device-name/}}. The web server is also disabled to save resources.		The plugs I've set up also have WIfiManager disabled (so that it will not enter configuration mode when it fails to connect). MQTT is enabled with the topic set to the device name and the master topic set to {{code\|tasmota/device-name/}}. The web server is also disabled to save resources.

	=== Troubleshooting ===		===Troubleshooting===
	==== Device did not appear with the intermediate firmware ====		====Device did not appear with the intermediate firmware====
	If your Tuya device is not being detected, you will see the following messages where the script retries. Ensure that you have another device connected to the vflash-trust AP.		If your Tuya device is not being detected, you will see the following messages where the script retries. Ensure that you have another device connected to the vflash-trust AP.

Line 245:		Line 250:
	Check the *.log files in the scripts folder}}		Check the *.log files in the scripts folder}}

	====Flashing Failed ====		====Flashing Failed====
	One of my attempts failed with this error:		One of my attempts failed with this error:
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
Line 384:		Line 389:


	{{Navbox Tinkering}}[[Category:Tinkering]]		{{Navbox Tinkering}}
			[[Category:Tinkering]]

Leo: Added category

2020-06-14T23:28:48Z

Added category

← Older revision		Revision as of 23:28, 14 June 2020
Line 382:		Line 382:
	*https://github.com/clach04/python-tuya		*https://github.com/clach04/python-tuya
	*https://github.com/clach04/python-tuya/wiki		*https://github.com/clach04/python-tuya/wiki


			{{Navbox Tinkering}}[[Category:Tinkering]]

Leo: /* MQTT Interaction */

2020-05-21T17:14:08Z

MQTT Interaction

← Older revision		Revision as of 17:14, 21 May 2020
Line 55:		Line 55:
	}		}
	<nowiki>}</nowiki>		<nowiki>}</nowiki>
	}}}		}
			}}

	Messages generated by the plug will be sent to the topic {{code\|smart/device/out/$DEVICE_ID}} and will be encrypted with the same algorithm outlined above. Plugs with additional capabilities such as power monitoring will also report these values to this topic multiple times per minute.		Messages generated by the plug will be sent to the topic {{code\|smart/device/out/$DEVICE_ID}} and will be encrypted with the same algorithm outlined above. Plugs with additional capabilities such as power monitoring will also report these values to this topic multiple times per minute.

Leo: /* MQTT Interaction */

2020-05-21T17:13:41Z

MQTT Interaction

← Older revision		Revision as of 17:13, 21 May 2020
Line 38:		Line 38:
	#JSON payload must be minimized with extra spaces removed		#JSON payload must be minimized with extra spaces removed
	#The JSON message is then encrypted using AES ECB using the 128bit AES localKey.		#The JSON message is then encrypted using AES ECB using the 128bit AES localKey.
	#A MD5 hash of {{code\|1=\|pv=2.1~~\|2=\|3=~~$LocalKey}} is computed.		#A MD5 hash of {{code\|1=data=$Cyphertext{{!}}{{!}}pv=2.1{{!}}{{!}}$LocalKey}} is computed.
	#The final message concats {{code\|"2.1" + MD5[8, 24] + $CypherText}}		#The final message concats {{code\|"2.1" + MD5[8, 24] + $CypherText}}

Leo: /* Flashing Tasmota with Tuya-Convert */

2020-05-21T17:10:39Z

Flashing Tasmota with Tuya-Convert

@@ Line 211: / Line 211: @@
 HAVE FUN!}}
-Once the devive has been flashed with Tasmota, it will come back up in configuration mode with an open access point named tasmota-xxxx. Connect to the network and configure the WiFi settings in a web browser. Once saved, it should connect to your WiFi network or if it fails, it will fallback into the configuration mode again where you can update the network settings again.
+Once the device has been flashed with Tasmota, it will come back up in configuration mode with an open access point named tasmota-xxxx. Connect to the network and configure the WiFi settings in a web browser. Once saved, it should connect to your WiFi network or if it fails, it will fallback into the configuration mode again where you can update the network settings again.
 The firmware loaded by tuya-convert is intended to be an intermediate firmware. Use the default update server URL to pull the latest OTA firmware. The device will reboot after it is done. Firmware upgrade takes a few minutes.
@@ Line 225: / Line 225: @@
 The plugs I've set up also have WIfiManager disabled (so that it will not enter configuration mode when it fails to connect). MQTT is enabled with the topic set to the device name and the master topic set to {{code|tasmota/device-name/}}. The web server is also disabled to save resources.
 ==Reverse Engineering==

Leo: /* Flashing a new firmware with Tuya-Convert */

2020-05-21T17:06:41Z

Flashing a new firmware with Tuya-Convert

@@ Line 130: / Line 130: @@
 <div class="res-img">[[File:NodeRED Tuya Plug.png|NodeRED Tuya Plug setup|center]]</div>
-==Flashing a new firmware with Tuya-Convert==
+==Flashing Tasmota with Tuya-Convert==
-The Tuya-Convert project simplifies the flashing of the Tuya smart plugs. It turns a Linux computer with a wireless adapter into an access point and bundles all the necessary services (DNS, HTTP, MQTT) such that a smart plug in setup mode will automatically be found and flashed. During the flashing procedure, you can choose to use either Espurna or Tasmota. Both custom firmware has their own set of features but Tasmota appears to be more popular and active.
+See the project website at https://github.com/ct-Open-Source/tuya-convert.
-TODO: docker run notes. also, you must connect to vtrust-flash with a phone or other device for the plug to get flashed.
+HAVE FUN!}}
-After choosing Tasmota, the device will reboot and come back up in configuration mode with an open access point named tasmota-xxxx. Connect to the network and configure the WiFi settings in a web browser. Once saved, it should connect to your WiFi network or if it fails, it will fallback into the configuration mode again.
+Once the devive has been flashed with Tasmota, it will come back up in configuration mode with an open access point named tasmota-xxxx. Connect to the network and configure the WiFi settings in a web browser. Once saved, it should connect to your WiFi network or if it fails, it will fallback into the configuration mode again where you can update the network settings again.
 The firmware loaded by tuya-convert is intended to be an intermediate firmware. Use the default update server URL to pull the latest OTA firmware. The device will reboot after it is done. Firmware upgrade takes a few minutes.
-See the project website at https://github.com/ct-Open-Source/tuya-convert.
+With the latest version firmware installed, set the device up to your specific model. Look up your model at https://templates.blakadder.com/ and copy the configuration template. Apply this template on the Tuya device under 'Configuration' -> 'Configure other'. The templates of the two models I own are:
-Teckin SP25:
+* Teckin SP25: {{highlight|lang=text|code=
 {"NAME":"Teckin SP25","GPIO":[56,255,255,255,255,255,0,0,22,17,255,21,255],"FLAG":1,"BASE":18<nowiki>}</nowiki>
 }}
+* AWP04L: {{highlight|lang=text|code=
 {"NAME":"AWP04L","GPIO":[57,255,255,131,255,134,0,0,21,17,132,56,255],"FLAG":0,"BASE":18<nowiki>}</nowiki>
 }}
 ==Reverse Engineering==

Leo: /* Flashing a new firmware with Tuya-Convert */

2020-05-21T06:18:05Z

Flashing a new firmware with Tuya-Convert

← Older revision		Revision as of 06:18, 21 May 2020
Line 132:		Line 132:
	==Flashing a new firmware with Tuya-Convert==		==Flashing a new firmware with Tuya-Convert==
	The Tuya-Convert project simplifies the flashing of the Tuya smart plugs. It turns a Linux computer with a wireless adapter into an access point and bundles all the necessary services (DNS, HTTP, MQTT) such that a smart plug in setup mode will automatically be found and flashed. During the flashing procedure, you can choose to use either Espurna or Tasmota. Both custom firmware has their own set of features but Tasmota appears to be more popular and active.		The Tuya-Convert project simplifies the flashing of the Tuya smart plugs. It turns a Linux computer with a wireless adapter into an access point and bundles all the necessary services (DNS, HTTP, MQTT) such that a smart plug in setup mode will automatically be found and flashed. During the flashing procedure, you can choose to use either Espurna or Tasmota. Both custom firmware has their own set of features but Tasmota appears to be more popular and active.

			TODO: docker run notes. also, you must connect to vtrust-flash with a phone or other device for the plug to get flashed.

	After choosing Tasmota, the device will reboot and come back up in configuration mode with an open access point named tasmota-xxxx. Connect to the network and configure the WiFi settings in a web browser. Once saved, it should connect to your WiFi network or if it fails, it will fallback into the configuration mode again.		After choosing Tasmota, the device will reboot and come back up in configuration mode with an open access point named tasmota-xxxx. Connect to the network and configure the WiFi settings in a web browser. Once saved, it should connect to your WiFi network or if it fails, it will fallback into the configuration mode again.

Leo: /* Node-RED integration with MQTT */

2020-05-20T16:51:02Z

Node-RED integration with MQTT

← Older revision		Revision as of 16:51, 20 May 2020
Line 35:		Line 35:

	All messages sent to and received from the plug must be JSON and encrypted using the AES key that was generated when the device was first set up also known as the {{code\|localKey}}. The steps to encrypt a message are:		All messages sent to and received from the plug must be JSON and encrypted using the AES key that was generated when the device was first set up also known as the {{code\|localKey}}. The steps to encrypt a message are:
	# JSON payload must be minimized with extra spaces removed
	# The JSON message is then encrypted using AES ECB using the 128bit AES localKey.		#JSON payload must be minimized with extra spaces removed
	# A MD5 hash of {{code\|1=~~data=$CypherText\|~~\|pv=2.1\|\|$LocalKey}} is computed.		#The JSON message is then encrypted using AES ECB using the 128bit AES localKey.
	# The final message concats {{code\|"2.1" + MD5[8, 24] + $CypherText}}		#A MD5 hash of {{code\|1=\|pv=2.1\|2=\|3=$LocalKey}} is computed.
			#The final message concats {{code\|"2.1" + MD5[8, 24] + $CypherText}}

	A message payload sent to the Tuya plug looks something like the following		A message payload sent to the Tuya plug looks something like the following
Line 53:		Line 54:
	"101": 0		"101": 0
	}		}
	}		<nowiki>}</nowiki>
	}}}		}}}

	Messages generated by the plug will be sent to the topic {{code\|smart/device/out/$DEVICE_ID}} and will be encrypted with the same algorithm outlined above. Plugs with additional capabilities such as power monitoring will also report these values to this topic multiple times per minute.		Messages generated by the plug will be sent to the topic {{code\|smart/device/out/$DEVICE_ID}} and will be encrypted with the same algorithm outlined above. Plugs with additional capabilities such as power monitoring will also report these values to this topic multiple times per minute.

	=== Node-RED integration with MQTT ===		===Node-RED integration with MQTT===
	You can use [[Node-RED]] and MQTT to control the Tuya smart plugs. I was able to get reliable triggering after changing the flows to use MQTT exclusively.		You can use [[Node-RED]] and MQTT to control the Tuya smart plugs. I was able to get reliable triggering after changing the flows to use MQTT exclusively.

Line 102:		Line 103:
	msg.payload = JSON.parse(CryptoJS.enc.Utf8.stringify(e).toString());		msg.payload = JSON.parse(CryptoJS.enc.Utf8.stringify(e).toString());

	return msg;}}		return msg;}}In an effort to make the flows more manageable, I inject the localKey from a single node. My flows ended up looking like this.
			[[File:Node-RED and MQTT Integration.png\|alt=Node-RED using MQTT to interact with Tuya Smart Plugs\|center\|thumb\|Node-RED using MQTT to interact with Tuya Smart Plugs]]
			<br />

	===Node-RED integration with TuyAPI===		===Node-RED integration with TuyAPI===
Line 128:		Line 131:

	==Flashing a new firmware with Tuya-Convert==		==Flashing a new firmware with Tuya-Convert==
	The Tuya-Convert project simplifies the flashing of the Tuya smart plugs. It turns a ~~linux~~ computer with a wireless adapter into an access point and bundles all the necessary services (~~dns~~, ~~http~~, ~~mqtt~~) such that a smart plug in setup mode will automatically be found and flashed. During the flashing procedure, you can choose to use either ~~espurna~~ or tasmota.		The Tuya-Convert project simplifies the flashing of the Tuya smart plugs. It turns a Linux computer with a wireless adapter into an access point and bundles all the necessary services (DNS, HTTP, MQTT) such that a smart plug in setup mode will automatically be found and flashed. During the flashing procedure, you can choose to use either Espurna or Tasmota. Both custom firmware has their own set of features but Tasmota appears to be more popular and active.

			After choosing Tasmota, the device will reboot and come back up in configuration mode with an open access point named tasmota-xxxx. Connect to the network and configure the WiFi settings in a web browser. Once saved, it should connect to your WiFi network or if it fails, it will fallback into the configuration mode again.

	~~After choosing Tasmota, the device should reboot and it should show up as~~ an ~~open access point. Connect to it and configure the WiFi settings. It will reboot once more and connect to your network. This step takes a few minutes. After it comes back up, you need to update its~~ firmware ~~to the latest version via the web interface~~. Use the default update server URL to pull the OTA firmware. The device will reboot after it is done~~, but this step~~ takes a few minutes.		The firmware loaded by tuya-convert is intended to be an intermediate firmware. Use the default update server URL to pull the latest OTA firmware. The device will reboot after it is done. Firmware upgrade takes a few minutes.

	See the project website at https://github.com/ct-Open-Source/tuya-convert.		See the project website at https://github.com/ct-Open-Source/tuya-convert.

Leo: /* Node-RED integration with MQTT */

2020-05-20T16:29:37Z

Node-RED integration with MQTT

@@ Line 60: / Line 60: @@
 === Node-RED integration with MQTT ===
 You can use [[Node-RED]] and MQTT to control the Tuya smart plugs. I was able to get reliable triggering after changing the flows to use MQTT exclusively.
 ===Node-RED integration with TuyAPI===
 If you don't want to use MQTT, you can still control a Tuya plug using the TuyAPI package which uses a HTTP API. I have found this to be more unreliable than MQTT and I do not recommend this method.   Issues I've encountered while using these libraries include unreliable triggering (where calls to turn on or off a plug are missed), or where triggering causes some undefined behavior (such as the plug resetting, disconnecting from WiFi, or toggling the switch rather than turn on or off).  For Node-RED integration, use the tuya-smart contrib package which provides nodes that interfaces with the TuyAPI library.

Leo: /* MQTT Interaction */

2020-05-20T16:25:39Z

MQTT Interaction

@@ Line 32: / Line 32: @@
 ===MQTT Interaction===
-The Tuya smart plugs will attempt to connect to a MQTT server at mq.gw.tuyaus.com on port 1883. You can either use this server or override the DNS entry within your network to point to a self-hosted MQTT server.
+The Tuya smart plugs will attempt to connect to a MQTT server at mq.gw.tuyaus.com on port 1883. You can either use this server or override the DNS entry within your network to point to a self-hosted MQTT server. The device subscribes to the topic {{code|smart/device/in/$DEVICE_ID}}; encrypted commands published will be processed by the device. Encrypted messages generated by the plug will be published to the topic {{code|smart/device/out/$DEVICE_ID}}.
-Commands should be sent to the topic {{code|smart/device/in/$DEVICE_ID}}. The message should conform to the typical Tuya format described below.
+All messages sent to and received from the plug must be JSON and encrypted using the AES key that was generated when the device was first set up also known as the {{code|localKey}}. The steps to encrypt a message are:
-The following function node will convert a JSON payload into the Tuya format that the plug will understand.
+A message payload sent to the Tuya plug looks something like the following
-{{highlight|lang=javascript|code=
+{{highlight|lang=json|code=
-var CryptoJS = global.get("CryptoJS");
-// mqtt topic
+Messages generated by the plug will be sent to the topic {{code|smart/device/out/$DEVICE_ID}} and will be encrypted with the same algorithm outlined above. Plugs with additional capabilities such as power monitoring will also report these values to this topic multiple times per minute.
 === Node-RED integration with MQTT ===