- Remove Telegram source filter and references
- Add device name mapping for username field (10→Joachim Pixel, 11→Huawei Smartphone)
- Implement color-coded markers and polylines per device
- Update time filter: default to 1h, add 3h/12h options, remove 7d/30d
- Add battery and speed info to location popups
- Improve marker design with custom droplet-shaped icons
- Filter only MQTT data (user_id = 0)
- Group locations by device with separate polylines
- Keep map layer selection (OSM, Satellite, Terrain, Dark)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Document all three workflows (tracker.json, tracker-db.json, tracker-mqtt.json)
- Add detailed descriptions of both web interfaces (index.html, index_owntrack.html)
- Include comprehensive installation guide with all credential types
- Add complete data schema documentation (Telegram vs MQTT differentiation)
- Expand workflow architecture diagrams for all three variants
- Add 7 customization options with code examples
- Include security warnings (GDPR, CORS, API authentication)
- Add extensive troubleshooting section (6 common issues)
- Document MQTT/OwnTracks integration details
- Add repository contents table and roadmap
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Added four comprehensive dropdown filters:
- Map layer switcher (standard, satellite, terrain, dark mode)
- Data source filter (Telegram/MQTT/all)
- Dynamic user/device filter (auto-populated from data)
- Time range filter (1h to 30d, plus all time)
Enhanced visualization:
- Latest location marked in red, historical in blue
- Proper layer management for markers and polylines
- Status shows filtered count vs total count
- All filters work in combination
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Log latitude/longitude values and types before parsing
- Add null checks for marker_label and display_time
- Improve history polyline filtering for invalid coords
- Show "Keine aktuelle Position" when no current location
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add console.log statements at each step
- Show error message in status widget
- Add coordinate validation
- Remove incorrect success/failure logic
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Convert string latitude/longitude to float before using in Leaflet
- NocoDB returns coordinates as strings, causing Leaflet errors
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add HTTP status check before parsing JSON
- Clear old markers and polylines on refresh to prevent stacking
- Improve error logging for better debugging
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add battery and speed fields to Location processing node
- Add battery and speed fields to NocoDB storage
- Update API URL to home64.de domain
- Add new index_owntrack.html with battery/speed display
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add validation for required fields (lat, lon, tst)
- Add timestamp validation to prevent "Invalid time value" error
- Skip entries with missing or invalid data
- Use fallback to current time if timestamp is invalid
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add tracker-mqtt.json: New n8n workflow for MQTT-based location data
- MQTT workflow subscribes to owntracks/# topic
- Transforms OwnTracks data format to NocoDB schema
- Stores locations in same database as Telegram workflow
- Update CLAUDE.md with MQTT workflow documentation
- Add OwnTracks integration guide and data mapping details
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Change sort option from object to array format to match n8n's
expected parameter structure for NocoDB nodes. This should resolve
import errors when loading the workflow.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add sorting to the "Lade Daten aus NocoDB" node to return locations
in descending chronological order (newest first). This ensures the
web interface displays all location entries correctly, not just the
first unsorted entry.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add tracker-db.json: NocoDB version of location tracker workflow
- Replaces file-based storage with NocoDB database
- Unlimited storage instead of 100-entry limit
- Includes CREATE and READ operations for locations table
- Add locations-example.csv: Sample location data for NocoDB import
- 8 example entries with Munich coordinates
- Demonstrates expected data structure
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
