Differences

This shows you the differences between two versions of the page.

--- infra:hosts:chucktheplant [2026/07/21 16:54] – Document unknown chucktheplant Raspberry Pi state atluxity_idp.hackeriet.no
+++ infra:hosts:chucktheplant [2026/07/21 17:50] (current) – Document disconnected TellStick status atluxity_idp.hackeriet.no
@@ Line 2: / Line 2: @@
 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 believed to be a Raspberry Pi at Hackeriet.
+  * The host is a physical Raspberry Pi at Hackeriet.
-  * It has a TellStick attached.
+  * It has a blue USB TellStick attached, currently disconnected.
-  * The TellStick controls at least one Nexa power plug.
+  * The TellStick controls at least one Nexa power plug when connected.
-  * The useful thing to change for the Nexa plug is probably the TellStick/Nexa channel or learned code, not the RF carrier frequency.
+  * 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 record.
+  * 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.
-===== Known checks =====
+===== Physical observation =====
-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.
+Observed in photos on 2026-07-21:
-No direct Hackerpass entry name was found for:
+  * 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.
-  * ''chuck''
+===== Network and inventory state =====
-  * ''plant''
-  * ''tellstick''
-  * ''telldus''
-  * ''nexa''
-The device is known not to be ''infrastructure/pi@dongd''.
+Checks performed on 2026-07-21:
-NetBox could not be confirmed during the initial investigation because the NetBox backend database was recovering at the time.
+  * 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.
-===== Next investigation steps =====
+The device is known not to be ''infrastructure/pi@dongd'' in Hackerpass.
-When connected to the Hackeriet network, try mDNS first:
+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.
-<code>
+===== TellStick / Nexa notes =====
-avahi-resolve-host-name chucktheplant.local
-ping chucktheplant.local
-ssh pi@chucktheplant.local
-ssh atluxity@chucktheplant.local
-</code>
-If mDNS does not find it, look for Raspberry Pi devices and SSH listeners on the local network:
+The TellStick is currently disconnected. This was done on 2026-07-21 to avoid disturbing another tenant in the building.
-<code>
+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.
-sudo nmap -sn 10.10.50.0/24
-nmap -p 22 --open 10.10.50.0/24
-</code>
-Useful Raspberry Pi MAC prefixes to look for in ARP/DHCP data:
+===== Access recovery =====
-<code>
+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.
-b8:27:eb
-dc:a6:32
-e4:5f:01
-d8:3a:dd
-</code>
-If DHCP lease data is available, search for:
+Useful facts to recover from the SD card or from the running system:
-<code>
+  * configured hostname
-chucktheplant
+  * configured users and SSH access method
-raspberrypi
+  * network configuration
-tellstick
+  * TellStick configuration in ''/etc/tellstick.conf''
-telldus
+  * systemd services related to ''telldusd'', TellStick, Nexa, or local automation
-</code>
+  * whether the breadboard/wiring is used by this service
-===== After login =====
-Once access is found, collect the operational facts without changing configuration first:
-<code>
-hostnamectl
-ip addr
-lsusb | grep -i -E 'tell|telldus'
-tdtool --list
-sudo sed -n '1,220p' /etc/tellstick.conf
-systemctl status telldusd
-</code>
-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 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?