03.01 – Basic Information
Core Node (Hardwired)
Even with the core node being direct-connected to the server, I used the same configuration for this as I do all my clients with some exceptions. My plan is to keep this inside, and put up a solar node outside (depending on more research, this may or may not be a CLIENT or ROUTER)
- USB-connected to server
- Wi-Fi disabled
- MQTT disabled
- Acts as RF gateway only
This prevents:
- Duplicate routing
- Security exposure
- App clients connecting directly
Client Nodes
Client devices may enable:
- Wi-Fi
- MQTT
- TLS
- Internet access
MQTT Settings
|
SETTING |
VALUE |
| Server | mqtt.example.net |
| Username | your-choice (set from MQTT install) |
| Password | your-choice (set from MQTT install) |
| Encryption | ✅ |
| JSON | ✅ |
| TLS | ✅ |
Naming Conventions
I decided to establish a standardized naming convention for my network that consists of some basic elements:
- Long name includes a designated emoji per entity at the start
- Each person or entity that is on my network has their own assigned (self-chosen) emoji to represent them and all their devices - no two people can use the same emoji
- Short name is the last 4 characters of the node's MAC
- I opted for this because some emojis are exactly 4 bytes, so if a person has more than one node, it prevents node SN identification. More complex emojis require more than 4 bytes and cant be used anyhow, so...