This is an old revision of the document!
Table of Contents
chucktheplant
Raspberry Pi labelled chucktheplant.hackeriet.no.
Current understanding, as of 2026-07-21:
- The host is believed to be a Raspberry Pi at Hackeriet.
- It has a TellStick attached.
- The TellStick controls at least one Nexa power plug.
- The useful thing to change for the Nexa plug is probably the TellStick/Nexa channel or learned code, not the RF carrier frequency.
- The hostname
chucktheplant.hackeriet.nois not currently present in DNS. - The host has not yet been matched to a NetBox record.
- Current SSH credentials and management path are unknown.
Known checks
DNS checks on 2026-07-21 returned NXDOMAIN for chucktheplant.hackeriet.no from public DNS, Hackeriet authoritative DNS on blade, and the likely internal resolver.
No direct Hackerpass entry name was found for:
chuckplanttellsticktelldusnexa
The device is known not to be infrastructure/pi@dongd.
NetBox could not be confirmed during the initial investigation because the NetBox backend database was recovering at the time.
Next investigation steps
When connected to the Hackeriet network, try mDNS first:
avahi-resolve-host-name chucktheplant.local ping chucktheplant.local ssh pi@chucktheplant.local ssh atluxity@chucktheplant.local
If mDNS does not find it, look for Raspberry Pi devices and SSH listeners on the local network:
sudo nmap -sn 10.10.50.0/24 nmap -p 22 --open 10.10.50.0/24
Useful Raspberry Pi MAC prefixes to look for in ARP/DHCP data:
b8:27:eb dc:a6:32 e4:5f:01 d8:3a:dd
If DHCP lease data is available, search for:
chucktheplant raspberrypi tellstick telldus
After login
Once access is found, collect the operational facts without changing configuration first:
hostnamectl ip addr lsusb | grep -i -E 'tell|telldus' tdtool --list sudo sed -n '1,220p' /etc/tellstick.conf systemctl status telldusd
For TellStick plus self-learning Nexa plugs, the relevant configuration is usually in /etc/tellstick.conf using the arctech protocol. The channel/code-like values are normally house and unit parameters. Changing those requires re-learning the receiver.
Open questions
- Where is the Raspberry Pi physically located?
- What IP address does it currently have?
- Which account should be used for SSH?
- Is the hostname actually configured on the Pi, DHCP, DNS, or just a physical label?
- Which Nexa plug does it control?
- Which Hula/Home Assistant/light/automation workflow depends on it?
- Should it be registered in NetBox and DNS once found?