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.no is not currently present in DNS.
• The host has not yet been matched to a NetBox record.
• Current SSH credentials and management path are unknown.

Observed in photos on 2026-07-21:

• White plastic Raspberry Pi-style enclosure/container with a physical label reading chucktheplant.hackeriet.no.
• The container is placed by a window together with network gear, power strips, and cabling.
• Inside the container is an open Raspberry Pi board.
• A blue USB TellStick device is attached.
• At least one external antenna/coax setup is present.
• There is a breadboard and loose wiring inside the container, so the device may do more than just TellStick/Nexa control.
• Exact room/location name and switch/router port are still to be identified.

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:

• chuck
• plant
• tellstick
• telldus
• nexa

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.

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

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.

• What exact room/location name should be used for the Raspberry Pi?
• 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?
• What is the breadboard/wiring used for?
• Which Hula/Home Assistant/light/automation workflow depends on it?
• Should it be registered in NetBox and DNS once found?