chucktheplant

Raspberry Pi labelled chucktheplant.hackeriet.no.

Current status, as of 2026-07-21:

• The TellStick has been disconnected to avoid disturbing another tenant in the building.
• Nexa plug control from this host should be considered disabled while the TellStick is disconnected.
• The Raspberry Pi itself may still be powered and running.

Current understanding, as of 2026-07-21:

• The host is a physical Raspberry Pi at Hackeriet.
• It has a blue USB TellStick attached, currently disconnected.
• The TellStick controls at least one Nexa power plug when connected.
• The useful thing to change for the Nexa plug is 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 device record.
• Current SSH credentials and management path are unknown.
• Physical access is possible. The SD card can be removed and inspected or changed offline if network or login access cannot be recovered normally.

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.

Checks performed on 2026-07-21:

• DNS lookups for chucktheplant.hackeriet.no returned NXDOMAIN from public DNS, Hackeriet authoritative DNS on blade, and the likely internal resolver.
• mDNS did not advertise chucktheplant.local.
• mDNS discovery found other Raspberry Pi-like hosts on the local network, but none named chucktheplant.
• NetBox device/IPAM searches for chucktheplant, chucktheplan, plant, tellstick, and nexa returned no matching device or IP address records.
• NetBox tag searches for plant and tellstick returned no matches.
• The NetBox DNS plugin is installed, but the current API token cannot read DNS records or zones. DNS plugin data is therefore not confirmed either way from the API.

The device is known not to be infrastructure/pi@dongd in Hackerpass.

A local network scan found 10.10.3.154/24 as an active Raspberry Pi-like host with SSH open and MAC address b8:27:eb:60:34:09. NetBox already has that IP documented as pi inside vending machine, so it should not be assumed to be chucktheplant.

The TellStick is currently disconnected. This was done on 2026-07-21 to avoid disturbing another tenant in the building.

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.

Physical access to the Raspberry Pi is available. If normal network access cannot be recovered, the SD card can be removed and mounted on another machine to inspect or change the installed system directly.

Useful facts to recover from the SD card or from the running system:

• configured hostname
• configured users and SSH access method
• network configuration
• TellStick configuration in /etc/tellstick.conf
• systemd services related to telldusd, TellStick, Nexa, or local automation
• whether the breadboard/wiring is used by this service

• 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?