- fix bidirectional link queries to find links where device is source or target
- merge A→B and B→A edges into single link with combined confidence
- include interface speed in edge data for variable edge width
- infer discovered node roles from LLDP/CDP capabilities (router, switch, wireless, phone)
- store remote_capabilities in link metadata during evidence processing
- replace Cytoscape destroy-and-recreate with element diffing to preserve zoom/pan/positions
- add node detail slide-out panel with device info, connections, and confidence
- support ?node= URL param for deep-linking to selected nodes
- add site-based compound node grouping in Cytoscape
Start a named Finch pool with CAStore certificate path and configure
Req to use it by default. Fixes integration sync failures on Dokku
where the OS CA trust store is unavailable.
Tests for agents, alerts, integrations, organization, members, and
invitations controllers. Refactor alert filters to reduce complexity.
75 new tests, all passing.
REST endpoints for CRUD, scoped filtering (active/upcoming/past).
GraphQL queries and mutations for maintenance windows.
Fix agent edit test assertion message.
REST API v1 endpoints for schedules (14 endpoints) and escalation
policies (10 endpoints) with full CRUD for nested resources (layers,
members, overrides, rules, targets). GraphQL types, resolvers, and
schema mutations for both resource trees.
Bump desktop nav breakpoint from md (768px) to lg (1024px) so the
mobile hamburger menu is used on medium-width screens instead of
nav items overflowing outside the viewport.
Clear all 65 bad fuzzy translations in English .po files (e.g.
"Navigation" was incorrectly translated to "Pagination") and fix
49 fuzzy entries in Spanish .po files with correct translations.
- Add 2-week visual timeline with per-layer and final schedule views
- Color-coded user spans with today marker and prev/next navigation
- Inline user picker when adding new layers (auto-add on select)
- Auto-add members on select for existing layers (no Add button)
- Display user names (first last) instead of emails throughout
- Default handoff time to 8:00 AM and start date to today
Built-in PagerDuty-equivalent system for on-call scheduling and alert
escalation. Users can now manage schedules, rotation layers, overrides,
and escalation policies directly in the app alongside PagerDuty.
- On-call schedules with rotation layers (daily/weekly/custom), member
management, and temporary overrides
- Escalation policies with ordered rules, timeout-based escalation,
and user/schedule targets
- Automatic escalation via Oban worker with configurable repeat count
- Email notifications via Swoosh for on-call alerts
- Resolver computes who's on-call from layer stacking and overrides
- AlertNotificationWorker integration: starts escalation alongside
PagerDuty, acknowledges/resolves incidents on alert state changes
- Device and organization schemas support escalation_policy_id
- Escalation policy picker on device form
- Schedules nav item with tabbed index (schedules + escalation policies)
- Full CRUD UI for schedules, layers, members, overrides, rules, targets
- 62 LiveView tests, 56 context/schema/resolver/escalation tests
- 26 E2E Playwright tests for smoke and critical path coverage
Add castore as a direct dependency to provide CA certificates in
environments where the OS trust store is not available (Dokku staging).
Stop leaking raw system errors (like CA trust store details) to the
UI by logging the full error server-side and showing a generic
user-friendly message instead.
When a billing provider is active, all other billing providers are
hidden from the main list and collected into a compact <details>
disclosure element showing provider names and descriptions.
When a billing provider is active (enabled), the other billing providers
are dimmed and collapsed to a single row showing a lock icon and which
provider is active. This reinforces the mutually exclusive constraint.
Also fixes status emoji accumulating in page title (JS regex needed
unicode flag) and adds missing page_title to 8 LiveViews.
Fix JS regex in StatusTitle hook to use unicode flag so emoji are
properly matched and replaced instead of accumulating. Add page_title
to 8 LiveViews that were missing it, which caused "TowerOps | TowerOps"
duplication from the live_title suffix.
Add setup_help info boxes to each integration provider showing where
to create API keys, step-by-step instructions, required permissions,
and example URL patterns.
8 of 13 OIDs were pointing to wrong MIB columns:
- RSSI: was reading ubntWlStatSignal(.5), now ubntWlStatRssi(.6)
- Quality: was reading ubntWlStatSignal(.5), now ubntAirMaxQuality(.6.1.3)
- Tx Rate: was reading ubntWlStatSsid(.2), now ubntWlStatTxRate(.9)
- Rx Rate: was reading ubntWlStatHideSsid(.3), now ubntWlStatRxRate(.10)
- Capacity: was reading ubntWlStatTxRate(.9), now ubntAirMaxCapacity(.6.1.4)
- Distance: was reading ubntWlStatSecurity(.11), now ubntRadioDistance(.1.1.7)
- Utilization: was reading WDS/Repeater booleans(.12/.13), now ubntAirMaxAirtime(.6.1.7)
- Added Signal Level sensor from ubntWlStatSignal(.5)
All 7 OIDs were reading from wrong SNMP table/columns. Frequency and
power config values pointed at the status table instead of the config
table, and capacity/signal columns pointed at unrelated fields like
radio temperature and boolean flags.
Corrected OIDs to match UBNT-AirFIBER-MIB structure:
- Frequency/power: config table (.3.1) entries 5, 6, 9
- Signal: status table (.3.2) entries 11, 14
- Capacity: status table (.3.2) entries 5, 6 with 1M divisor
- Added guard clause to return nil for empty binary MAC addresses
- Filter rejects entries with nil IP or MAC addresses
- Prevents 'can't be blank' validation errors on upsert
- Root cause: some SNMP devices return incomplete ARP entries
Previously just logged a count without any details, making debugging
impossible. Now logs first 3 sample errors with IP, MAC, and validation
errors to help identify root cause.
Sample output:
290 ARP upsert failures for device X
sample_errors: [
%{ip: nil, mac: "00:11:22:33:44:55", errors: %{ip_address: ["can't be blank"]}},
%{ip: "10.0.0.1", mac: nil, errors: %{mac_address: ["can't be blank"]}},
...
]
Proactively add catch-all handlers to device index/show pages to
prevent FunctionClauseError when StatusTitleComponent broadcasts
alert changes. These are the most frequently open pages where users
would encounter the crash.
The StatusTitleComponent (rendered in authenticated layout) subscribes
to organization:*:alerts PubSub topic. Since LiveComponents run in the
parent process, both the component and parent LiveView receive these
messages.
Added catch-all handler to prevent FunctionClauseError when alert
changes broadcast. The component already handles the message properly.
- Check if community string is nil before slicing
- Display '(none)' instead of crashing with FunctionClauseError
- Fixes discovery crashes when community string is not set
Error was: String.slice(nil, 0..3) causing discovery tasks to fail
- API auth uses current_user, not current_scope
- Check membership role directly instead of using owner?/1 helper
- Allow superusers to update organization settings
- Fixes KeyError: key :current_scope not found
Previous code assumed LiveView context with current_scope, but API
requests only have current_user and current_organization_id assigned.
- Add authorization check in organization_controller.ex update action
- Only organization owners can modify organization settings via API
- Returns 403 Forbidden if user is not an owner
- Affects all organization settings including use_sites and name
- Organization name can now be updated via API (existing field)
This ensures critical organization settings are only changed by authorized users.
Device Type Fix:
- Add Topology.maybe_update_device_role() call after discovery completes
- Device types (AP, router, switch, etc.) now inferred immediately after discovery
- Previously devices showed 'unknown' until first polling cycle completed
- Role inference uses SNMP manufacturer, model, and system description
Billing Fix:
- Handle string values from Settings.get_setting() in default_price_per_device()
- Add case clause to convert string '2.00' to Decimal struct
- Fixes CaseClauseError crash on /orgs/:slug/settings page
All discovery tests passing.
- Made normalize_mac/1 public with comprehensive documentation
- Enhanced normalize_mac to handle:
- Binary MAC addresses (6 bytes) with proper hex conversion
- Short MAC addresses with zero-padding (e.g., 'A:B' -> '0a:0b')
- Colons, dashes, and no-separator formats
- Fixed refresh_links_for_device/1 to return :ok when device not found
(was returning nil, causing test failures)
- Fixed site fallback test to use assigned_network_site_gaiia_id
(string field) instead of network_site_id (FK)
- Simplified account lookup optimization test to remove
non-existent Repo.query_count/1 dependency
All 19 subscriber matching tests now passing:
- 7 normalize_mac/1 tests (binary, colons, dashes, padding, etc.)
- 12 refresh_device_links/1 tests (all match methods, prioritization,
cross-org isolation, etc.)
CRITICAL FINANCIAL BUGS FIXED:
1. Stripe price creation was sending dollars instead of cents
- create_price() now converts $2.00 -> 200 cents
- Was sending "2.00" to unit_amount_decimal (0.02 dollars!)
- Now correctly sends "200.00" (2 dollars in cents)
2. VISP sync was using floating point arithmetic for MRR
- calculate_total_mrr() was using 0.0 accumulator and float math
- Now uses Decimal.new("0") and Decimal.add() throughout
- Prevents precision loss when summing subscriber MRR
All money calculations now use Decimal library to avoid floating
point precision errors. Amounts are only converted to cents (integers)
at the boundary when sending to Stripe API.
- Add missing wireless_mac and wireless_ip to schema validation
(was causing highest-confidence matches to be rejected)
- Optimize account lookup to load once instead of 5x per refresh
(eliminates N+1 query performance issue)
- Preserve all matching phases with proper signature updates
When SNMP returns MAC addresses as strings (e.g., 'A:B:C:D:E:F'), they were
being converted to lowercase without padding hex digits with leading zeros.
This caused subscriber matching to fail because the normalize_mac function
expects properly padded MACs (e.g., '0a:0b:0c:0d:0e:0f').
Now properly normalizes string MACs by:
- Removing all separators
- Ensuring 12 hex characters
- Reformatting with colon separators and proper padding
This fixes subscriber matching for ePMP and some Ubiquiti devices that
return string-formatted MACs from SNMP.
Removed:
- Compact view toggle button from the header
- toggle_compact_mode event handler
- @compact_mode assign
The button was not connected to any actual functionality.
The discovered tab badge was showing length(@discovered_devices) which is
the paginated list (20 items per page), not the total count. Now shows
@pagination.total_count to display the actual total (e.g., 876 devices).
- Create wireless_client_readings hypertable with compression and retention
- Add WirelessClientReading schema and batch insert function
- Update DevicePollerWorker to save historical readings
- Add signal_badge and snr_badge components to CoreComponents
Security-hardened implementation that automatically grants superuser status
to graham@towerops.net and graham@mcintire.me during user registration.
Security measures:
- Only runs during NEW user creation (__meta__.state == :built check)
- Cannot be triggered via account updates (prevents privilege escalation)
- Case-insensitive comparison (prevents 'Graham@TOWEROPS.NET' bypass)
- Email must pass validation and uniqueness constraint first
- Explicit defense-in-depth with comprehensive security comments
Prevents scenarios where:
- Owner loses access to their own system
- Need to manually grant superuser via database manipulation
- Case variations could bypass the check
Test coverage includes:
- Both email addresses get superuser
- Case variations are handled correctly
- Similar/spoofed emails are rejected
- Other emails don't get superuser
