Configure your Hardware as a Tasmota Node
This tutorial configures the Node to connect to the RDDL Testnet.
Last updated
This tutorial configures the Node to connect to the RDDL Testnet.
Last updated
The nodes come with firmware from and are compatible with .
Initially, you have to
Search for the Tasmota nodes' wifi hotspot
Connect to it
Configure your wifi (the node IP on your local network should be displayed so that the last step can be ignored)
Reconnect on your local wifi so you can use the node with internet connectivity.
Identify the local IP of your Tasmota node and connect to it (e.g. using Nmap to search for IP addresses or look it up on your router/switch)
Having that, you can connect to the node by browsing the IP address with HTTP.
Follow the menu to Consoles→Console.
Enter the command Mnemonic and store the mnemonic to recover your funds and chain interaction identities later.
Enter the command PublicKeys to get to know your addresses and keys.
Ensure that you also define the denomination, notarization periodicity, and the ChainID:
PlanetmintDenom plmnt Declares the token denomination used on the chain (Testnet).
PlanetmintChainID planetmint-testnet-1 or PlanetmintChainID planetmint-mainnet-1 Declares the ChainID of the Testnet/Mainnet.
NotarizationPeriodicity 3600 Defines the notarization frequency in seconds. 3600 = 60*60 seconds and lets the device notarize once an hour.
Next, you need to create the machine account's chain. This is necessary so the machine attests to the chain, which uses 1 PLMNT. After your machine is attested and activated, it will receive 8800 PLMNTs, enough to notarize data for a year if the notarization periodicity is set to 1 hour.
You can achieve this in the following ways:
Testnet only: Fund the machine address by sending PLMNT tokens to the address (e.g., plmnt10addjzn66e0u9kfy4ku307zjd0z3dyqd45gjh7)
Issue the following command on Tasmota (or https://testnet-ta.rddl.io on testnet)
CreateAccount https://ta.rddl.io
Send a request create-account to the Trust Anchor Registration Service like :
The Balance of the account can be inspected via the Balance command.
The Testnet Explorer can also be used to inspect the funds of the account
Restart your node once.
The Tasmota can now create, sign and broadcast transactions to the Planetmint Testnet. Please attest your machine now with the following command:
AttestMachine <machine type like fridge> <machine manufacturer like DIY Inc> <CID with additional information>
After a successful attestation, the device will start notarizing consumption/production data. It does so every 60 minutes (3600 seconds) or if you execute the Notarize command. Machine attestation is performed automatically and can be witnessed by looking at the explorer.
For Client and Topic set your machine's address.
Unable to connect to the MQTT service - connection error 62
The Tasmota version rddl-v0.43.0 and below do not recognize the newest Let's Encrypt root certificates and drop the TLS connection because of an untrusted CA. Executing the following command on the command line
setoption132 1
will enable certificate verification but disable the AWS IoT and Let's Encrypt certificate check. This will solve the issue as the certificates are valid, and the connection will again work as expected.
Enter the command PlanetmintAPI to set the URL to connect to the planetmint blockchain API. is set as the default value. If you want you node to interact with the mainnet set it to
Testnet only: Alternatively, if you are on the testnet, you can go to the Testnet Faucet and fund your address (e.g. plmnt1xjfmfeuu533h40sz0jcjkc5727ph3cy8r0d4ma)
The resulting transaction can be inspected on your account page on the .
Go to Configuration -> Configure MQTT and set the credentials provided .
Depending on the network you are using set the following host and port found and tick the checkbox for MQTT TLS.
If you cannot fund your account (i.e.: via ta(-testnet).rddl.io/create-account Or funding your account manually). Check if your machine address exists on the correct network under the following link:
or
If not, you probably downloaded firmware for the wrong network, as your firmware will be attested for either the testnet or mainnet. Check the links posted .
