What’s new.

Monday, September 21, 2026

1. this ship

   Ask to upgrade — UniFi stay on Cable Pro

   Free seats map their own building. Live UniFi/switch/AP pull is Cable Pro or MSP, not a cheap add-on, because that is the shop’s controller — wiring Enlighten’s keys would leak the house. Ask to upgrade emails Mike. Check or invoice later. No Stripe.

   • ●Keep public /signup. Free plant is empty and isolated — not Harborline, Cobus, or operator lastPull.
   • ●Account, Billing, Jobs, Switches, and Air have Ask to upgrade. Enlighten sees the list on /admin and /admin/health.
   • ●alacarte-addons stays held. no-stripe stays. UniFi 8-port and heatmap notes were not restamped.
   • billing
   • unifi
   • free

Sunday, September 20, 2026

1. this ship

   APs are not 8-port switches — NICGIGA 6-port is typed

   UniFi access points were landing under Switches because the controller JSON includes a virtual 8-port table on in-wall APs. Those are passthrough NICs. The two unmanaged NICGIGA 4×2.5G + 2 SFP boxes can be added as 6-port faceplates. Lantern cannot read their per-port state.

   • ●switch-ap-misclassify and unmanaged-switch-ports are checked off.
   • ●APs stay on Air. Physical ethernet (1–2, IW up to 5) can show as passthrough — not an 8-port chassis.
   • ●Add a switch includes NICGIGA NIC-AS2042. Unmanaged card says no SNMP / no scrape. If it hangs off the UniFi switch, that uplink is on the UniFi faceplate.
   • ●Instant On is never scraped from this site. Frozen OG, lockup, and rail untouched.
   • switch
   • unifi
   • plant

Saturday, September 19, 2026

1. this deploy

   Home Air counts this shop's last controller pull

   Signed-in / now uses the same AP list as Air: last UniFi pull for that company, plus APs already on the plant. A friend shop with an empty plant file still sees their APs after Test pull. Harborline stays the compiled demo and never inherits another company's snapshot.

   • ●Home, Air, and home studies share one helper. No per-shop recode after a tester pulls UniFi.
   • ●Empty until that shop pulls UniFi or adds an AP. Switches and cameras stay the plant file.
   • ●Password hashes untouched.
   • air
   • home
   • unifi

2. this deploy

   UniFi official API pull reads device detail, not list tags

   Test pull on Operator → Integrations now GETs each adopted device so switch ports, PoE state, and AP radios come from the official Network API device object. The list endpoint only returns capability tags. Classic Network 8.1.113 still uses the LAN PC Agent. Harborline stays compiled.

   • ●LIST interfaces: ["ports"] is not a port table. GET /devices/{id} expands interfaces.ports and interfaces.radios.
   • ●Guest clients stay off the File list. Default / WAN / console hosts stay off the plant.
   • ●unifi-controller-pull is checked off. Instant On never. PoE/L2 collector overlay stays on network-device-auto-add. Password hashes untouched.
   • unifi
   • integrations
   • plant

Friday, September 18, 2026

1. this deploy

   Set all files UniFi pull onto the plant lists

   Set all on Integrations now merge-adds the last UniFi pull onto Switches, Air, Cameras, and Computers using controller hostnames. WAN, Default, and public IPs stay off the plant. Unknown LAN-scan Others with the same MAC move out of Others.

   • ●One write. No invented SW-MDF. Private IPs only. Harborline stays the compiled demo.
   • ●PoE/L2 collector overlay is still open. Password hashes untouched.
   • unifi
   • integrations
   • plant

2. this deploy

   Air's switch card follows the amber rule too

   The switch on Air was painting every live port amber because a PoE switch reports PoE enabled on all of its copper ports. Amber now waits for watts, so the card shows the mix it should: powered ports amber, live ports with no draw green, empty ports black.

   • ●PoE enabled on a port is capability, not power. Only watts on a live port light the bolt.
   • ●Same fix on the switch page and the closet cabinet, since they share the plate.
   • switches
   • poe
   • unifi

3. this deploy

   The switch on the plant now matches the controller

   Switches and Air were reading two different copies of the same box — Air had the real 16-port PoE switch while the closet still showed the 24 ports someone typed before the controller was connected. There is one switch now, and it is the one the controller reports.

   • ●A switch the controller knows takes its real make and model, its port count, its PoE numbers, and its management address from the pull. 16 copper + 2 SFP instead of a typed 24.
   • ●The port list shows what is plugged into each port, from the controller: the AP, the PC, the camera, with its IP and MAC.
   • ●The closet, rack slot, and the name you gave the switch stay yours. So does any port you have already labelled or patched.
   • ●A shop with no controller is unchanged — your typed port count, your picked faceplate, and Unknown where nothing has reported.
   • ●Plant rows carry the private management address only. A public WAN address is dropped instead of filed on a switch.
   • switch
   • unifi
   • plant

4. this deploy

   A live SFP uplink is green, and amber now means PoE watts and nothing else

   SFP cages follow the same rule as copper: green when the link is up, plain black when it is not. Every other orange accent on the faceplate — the picked port ring, the hover card edge, the PoE chip when nothing is drawing — went neutral, so amber on a switch always means that port is pushing watts.

   • ●A live SFP uplink reads the same green as an active copper port. A dark cage is a cage with no link.
   • ●The PoE chip in the header only lights amber while the switch is actually handing out watts.
   • ●Clicking a port on the switch page rings it in white instead of orange. SFP still never shows a bolt or a watt figure.
   • switches
   • poe
   • unifi

5. this deploy

   Switch ports read amber, green, or black at a glance

   A port is only amber when it is actually pushing PoE watts. A live port with no power now reads green, and a port with nothing plugged into it is a plain black jack instead of a lit one.

   • ●Amber bolt = up and drawing watts. Green jack = up, no PoE draw. Plain black jack = down.
   • ●PoE-capable ports still carry the bolt, but it stays neutral until watts are flowing, so amber never means anything else.
   • ●A down port no longer claims 0 W. It reads PoE port · no link. A real 0 W still shows only when the controller reported zero on a live port.
   • ●Same three colors on the Air card, the switch page, and the MDF cabinet, and they hold up on a phone.
   • switches
   • poe
   • unifi

6. this deploy

   Switch page lists every port: device, PoE, VLAN, spare

   Open a switch and the faceplate now has a real port table under it — port and alias, up or down, link speed, PoE watts and mode, VLAN, the device on the jack, and whether it is an uplink, a downlink switch, or an access port. Click a row to light that jack on the faceplate; click a jack to jump to the row. The header counts used vs spare and the PoE headroom left in the budget.

   • ●Devices come from the last controller pull — the port MAC is matched to that client for its hostname and IP. On a typed plant the jack, room, and drop the shop keyed show instead, marked Typed.
   • ●Anything the controller did not report reads Unknown. Lantern does not invent a watt, a speed, or a VLAN.
   • ●A switch with no controller can still be walked: pick the faceplate model on the switch page and type a device per port. The picked faceplate now sticks — typing a camera onto port 7 no longer repaints the chassis as a generic plate.
   • ●PoE bolt, per-port hover, and the lit-port animation are unchanged. Password hashes untouched.
   • switches
   • poe
   • unifi

7. this deploy

   A lightning bolt on every PoE port

   The switch faceplate now marks each PoE port with its own bolt, so you can glance at the plate and see which jacks can power a camera or an AP. Hover or tap a port for that port's watts. The big total that sat on top of the ports moved up to the header.

   • ●Bolt lit = that port is drawing power right now. Bolt dim = PoE port with nothing on it. No bolt = not a PoE port, and SFP cages never get one.
   • ●Hover or tap a port for up/down, that port's watts, link speed, and the device. If the controller sent no watts for a port it says watts unknown on this pull — 0 W only when the controller really said zero.
   • ●Total draw and budget now ride in a chip next to 16 copper + 2 SFP. The budget is the switch's published spec (150 W on a a UniFi PoE switch); if the controller reports a different number, the chip says so instead of printing it as the spec.
   • ●Ports are focusable, so the same facts come up on a phone. Password hashes untouched.
   • switches
   • unifi
   • poe

8. this deploy

   Integrations is Connected and Available, not one long scroll

   Operator → Integrations now opens on one compact UniFi row — Connected, controller, last pull clock — with an Edit button for the key and the local controller login. The pulled device list moved behind its own Devices and clients disclosure, so 30-plus rows no longer bury the settings.

   • ●Set all still sits at the top of that list, and every row still has Set. Nothing was renamed.
   • ●Vendor cards are uniform now: what each one pulls, what Lantern needs pasted, where the rows land. Meraki saves a dashboard key today and says Key saved — not Connected. Omada, Aruba, Mist, MikroTik, and Protect read Later until Lantern really pulls them.
   • ●Secrets are still write-only and never shown again. A demo company still cannot see the operator snapshot. Password hashes untouched.
   • unifi
   • integrations
   • admin

9. this deploy

   Integrations uses Set all, not File all

   The UniFi devices list on Integrations now has Set all at the top. Each row is Set. Same plant write — just the control name.

   • ●Pending copy is Setting. Password hashes untouched.
   • unifi
   • integrations

10. this deploy

    Switch faceplates show PoE watts on a lightning bolt

    The a UniFi PoE switch (and other PoE catalog plates) now has a bolt in the middle of the copper ports for used / budget watts from the last pull. Hover a port for that drop’s watts, link speed, up or down, and the device name. The old “10 up / 18 / 150 W” line mixed port count with the budget — it now reads 10 up · 16 copper + 2 SFP.

    • ●Bolt sits on the 16-port copper bank. Hover it for the budget and which ports are drawing. Watts come from controller poe_power — nothing invented.
    • ●Click the card still opens /switches. Lit-port animation unchanged. Password hashes untouched.
    • switches
    • unifi
    • poe

11. this deploy

    Public changelog no longer lists the house LAN

    What’s new and the public launch board no longer print the operator UniFi controller address, in-wall AP model, or operator PC hostname. Harborline demo isolation is a separate tenant fix.

    • ●Public /changelog redacts those strings even when an older live log row still has them.
    • ●Public /launch no longer serializes launch-card notes (those held the controller fact). Password hashes untouched.
    • unifi
    • changelog
    • privacy

12. this deploy

    Harborline demo does not show another shop’s APs

    UniFi last pull stays on the company that owns Integrations and the PC agent token. Harborline demo seats keep the Tacoma sample plant — not Cobus UniFi APs, switch faceplates, or controller cards.

    • ●Air / Switches / File all read that company’s snapshot only. A demo tenant cannot inherit the operator last pull.
    • ●Enlighten / Cobus still sees the house UniFi pull. Password hashes untouched.
    • unifi
    • plant
    • harborline

13. this deploy

    Air AP pages plus UniFi 16-port PoE faceplates

    Air is a compact AP list that opens radios, clients, airtime, IP, and MAC. The switch draws like a a UniFi PoE switch: clip-art, live ports, PoE, and the device on each port from the controller. Port/PoE counts come from the switch, not the first AP.

    • ●Manual add browses UniFi PoE SKUs and generic 8/16/24/48. faceplateId persists. UniFi LAN ingest maps model + port_table.
    • ●Did not Test-pull cloud or port-forward. Password hashes untouched.
    • unifi
    • air
    • switches

14. this deploy

    Air shows every UniFi AP plus the switch ports

    The floor/Air page listed one AP and stuffed LAN-scan hostnames into SCAN LAN. The controller pull already had APs and a PoE switch. Air now cards each AP. Switch ports and PoE come from the switch, not an in-wall AP. Walk samples stay typed.

    • ●Ports 3 / PoE 0 was the first device in the JSON (an in-wall AP), not a PoE audit. Next LAN UniFi pull stores the switch port table.
    • ●SCAN LAN is a count plus Computers — not OTHER-* wrapping as jack labels. Password hashes untouched.
    • unifi
    • air
    • floors

15. this deploy

    UniFi LAN pull rides the PC Agent

    Classic Network 8.1.113 cannot list adopted switches from api.ui.com. Save the local UniFi user on Integrations. A house PC Agent pulls HTTPS-out to the house UniFi controller and posts the File list.

    • ●Do not Test pull the cloud key again until the snapshot has devices.
    • ●Tray Push inventory, or wait ~15 minutes. Secret is never shown again. Do not email the UniFi password.
    • ●File still uses controller names. Not a house collector container. Not Harborline.
    • unifi
    • admin
    • computers

Thursday, September 17, 2026

1. this deploy

   UniFi File uses controller names, not the console WAN

   Test pull skips the Site Manager console host (example-domain.ui.com / public WAN). Adopted switches and APs keep controller names. Air overlay is the same for other vendor APIs.

   • ●File a UniFi switch as its hostname, not SW-MDF. Manufacturer is Ubiquiti plus the model.
   • ●example-domain.ui.com + 108.x WAN is the console host, not a plant device.
   • ●Air overlay is shared: UniFi live; Meraki, Omada, Aruba, Mist, MikroTik next on the same page.
   • unifi
   • admin
   • plant

2. this deploy

   Vendor APIs on Account — UniFi first

   Anyone on UniFi, Meraki, or Juniper should connect with an API key. Operator → Integrations (above Tools) is the Enlighten UniFi paste. Account also takes shop vendor keys. UniFi is Doing, not done until a real pull. Meraki and Juniper are Need to do.

   • ●unifi-controller-pull — official Integration API, key in Operator → Integrations. Classic the house UniFi controller is a LAN fact. Windows HTTPS-out if the key is LAN-only.
   • ●meraki-controller-pull — shop Meraki key, HTTPS to api.meraki.com. Same snapshot. After UniFi or parallel notes.
   • ●juniper-controller-pull — Mist or Junos REST after UniFi/Meraki. Not a duplicate of l3-vendor-adapters. Omada/L2 later.
   • unifi
   • meraki
   • juniper
   • launch
   • account

3. this deploy

   UniFi pull lists devices and clients you can file

   The shop Network site (ES), not hidden Default / super rows. File each row, or File all with the suggested category, onto this location.

   • ●Pull keeps Enlighten Studios. /v1/sites/{id}/devices plus console proxy. Guest / visitor SSIDs skipped.
   • ●Saved key Test pull does not ask you to paste again. Secret is never shown again.
   • ●UniFi is not done until those rows land on the plant. Not Harborline. Do not email the key.
   • unifi
   • admin
   • plant

4. this deploy

   Integrations is on the operator rail, above Tools

   Sign in as mike@ → Integrations (above Tools). Paste the UniFi Network Integration API key and Test pull. Self-hosted Network 8.1.113 has no local key screen — mint at unifi.ui.com/api. Meraki, Protect, and other vendors wait on that page.

   • ●Rail + admin tabs: Integrations, one word, above Tools. UniFi form is live. Secret is never shown again.
   • ●Coming next on the same page: Meraki, Omada, Juniper, Protect, other cameras. PC Agent / LAN scan stay HTTPS-out from Computers.
   • ●lantern.enlightenstudios.us cannot reach the house UniFi controller. Test pull uses api.ui.com. UniFi is not done until switches and APs land.
   • unifi
   • admin
   • launch

5. this deploy

   UniFi log rows rewritten: official Integration API

   Same ids as the older live rows. Official UniFi Integration API key on Account. Plesk is the Enlighten backend on ES-ss1 (Computers), not the house UniFi controller. LAN fact stays the house UniFi controller. UniFi is not done until switches and APs land.

   • ●Paste the Integration API key (X-API-KEY) from the console or Site Manager → Integrations.
   • ●lantern.enlightenstudios.us cannot reach RFC1918. Site Manager / api.ui.com, or a Windows HTTPS-out agent if the key is LAN-only.
   • ●Did not restyle frozen OG, rail, or plant lists. Password hashes untouched.
   • unifi
   • changelog
   • launch

6. this deploy

   Admin APIs — paste a UniFi Integration key

   Enlighten admin only: /admin/integrations. Official UniFi Network Integration API (X-API-KEY). Test pull hits api.ui.com. RFC1918 house controller is documented. Plesk is the Enlighten backend, not the house. Password hashes untouched.

   • ●Sign in as mike@ → Admin → Integrations (above Tools). Paste the Integration API key. Optional controller URL defaults to the house UniFi controller.
   • ●Test pull shows device / PoE / port counts. The secret is never logged or shown again.
   • ●Lantern’s server cannot reach RFC1918. Local-only keys need a Windows HTTPS-out agent. Not a Harborline controller.
   • unifi
   • admin
   • launch

7. this deploy

   UniFi is official Integration API — shops do not run a collector

   Official UniFi Integration API. House controller the house UniFi controller. Paste the key in Operator → Integrations (above Tools). The website cannot reach RFC1918.

   • ●unifi-controller-pull stays Doing. Not a local cookie username. Instant On never.
   • ●Paste the UniFi Integration API key in Operator → Integrations (X-API-KEY).
   • ●Do not email the UniFi password.
   • unifi
   • launch

8. this deploy

   UniFi controller is classic the house UniFi controller

   Mike’s UniFi is classic local API on the house LAN at the house UniFi controller — not UniFi OS on :443. Pull is the official Integration API key on Account. Plesk is the Enlighten backend, not the house. UniFi is not done.

   • ●unifi-controller-pull stays Doing. Done: HTTPS-out shape, no inbound, not fake-live, LAN IP, classic :8443.
   • ●Paste the official UniFi Integration API key (X-API-KEY). Not a ui.com cookie login. Instant On never.
   • ●lantern.enlightenstudios.us cannot reach RFC1918. Site Manager / api.ui.com, or a Windows HTTPS-out agent if the key is LAN-only. Do not email the UniFi password.
   • unifi
   • launch

9. this deploy

   UniFi: what Mike needs to send

   Account is the official UniFi Integration API key. Controller LAN fact: the house UniFi controller. Plesk is the Enlighten backend, not the house. No inbound scrape.

   • ●Paste the Integration API key in Operator → Integrations (console or Site Manager → Integrations, X-API-KEY).
   • ●If the key only talks to the LAN controller, Windows HTTPS-out agent — same family as LAN Scan EXE.
   • ●Do not port-forward UniFi. Do not paste the password in email.
   • unifi
   • launch

10. this deploy

    PC Agent 2026.09.17.8 — real LAN IP, SSD life, temps

    Host IP ignores multicast 224.0.0.22. SSD life reads Wear from each PhysicalDisk. CPU temp also asks Windows thermal-zone counters. GPU still nvidia-smi when NVIDIA is installed. Intel iGPU stays Unknown. Re-download the EXE.

    • ●IPv4 skips 224/239 multicast, 169.254, and loopback. Prefers 192.168 / 10 / 172.16.
    • ●Get-PhysicalDisk | Get-StorageReliabilityCounter plus MSFT_StorageReliabilityCounter for NVMe/SSD life.
    • ●Get-Counter Thermal Zone Information for CPU when ACPI is empty. No kernel temp driver.
    • ●Account UniFi connect is the official Integration API key. Plesk is the Enlighten backend, not a house bind.
    • computers
    • pc-agent
    • unifi

11. this deploy

    Wake-up ten — honest live vs blocked on Mike

    Typed Cobus add, PC Agent Bypass/Hidden SYSTEM, PoE on Add switch, smart devices, LAN-scan EXE, collapsed Checked cards are live. UniFi is the official Integration API key until switches and APs land. Home tier is a client flag, no Stripe. Harborline is not his house.

    • ●Live: camera / switch / AP merge-add, PoE used ports/watts, /computers/smart, Floor One video hold + plus floor, Launch collapse.
    • ●PC Agent EXE stays ExecutionPolicy Bypass + WindowStyle Hidden SYSTEM. LAN scan is a second EXE HTTPS-out (Get-NetNeighbor RFC1918).
    • ●UniFi: official Integration API. Controller fact the house UniFi controller. Shops do not run a collector on the house. Instant On never.
    • ●Home tier: Enlighten client checkbox only. No Stripe SKU. Mapping still Need to do.
    • plant
    • launch
    • computers
    • unifi

12. this deploy

    Board: typed plant, UniFi/Omada/Meraki, L2 consoles, PoE, smart devices

    Need-to-do cards for Brand under Tools, Switches above Air, manual cameras/switches, UniFi then Meraki and Omada HTTPS-out, other L2 consoles, unmanaged LAN scan, PoE watts, and Smart devices. Tick only refreshes percents — these cards boot from catalog + stamp. PC Agent EXE is a different binary.

    • ●brand-tools-nav / switches-nav-above-air — Need to do. Electric Pro stays uncluttered.
    • ●cameras-manual-add / switches-manual-add / plant-manual-add — typed inventory, no L3, no live LDAP bind.
    • ●unifi-controller-pull / meraki-controller-pull / omada-controller-pull — shop HTTPS-out. Not fake-live. The website cannot reach RFC1918.
    • ●l2-controller-integrations — Instant On, Insight, Cisco Business, MikroTik, other L2. Instant On is never a live scrape.
    • ●lan-scan-unmanaged — unmanaged / no controller only. switch-poe-ports — used PoE + watts + budget. smart-devices-tab — under Computers.
    • launch
    • plant
    • unifi
    • nav