Repository navigation
feat: SSDP auto-discovery, sensor catalog, tidier Add Device page - #166
Merged
Merged
Conversation
…rted (smoke, water, gas, door, motion, climate); sirens stay unsupported Models map to code paths that already exist (shellySensorKind, HA_SENSOR_CLASSES/HA_BINARY_CLASSES). Not verified with real hardware.
M-SEARCH per UPnP DA 1.1; only private-address replies; candidates are still identified by the protocol probes. Parsing covered by tests; the multicast send was checked once against a real router (it replied), no smart device verified.
This was referenced Oct 30, 2026
…y, template prompts create, bare help only) 'yardım istiyorum' inside any sentence used to return the generic command list; create-requests were swallowed by DND/status/help matches.
…n narrow screens)
…, Messages, Settings) and no emoji Icons are lucide line icons rendered to 32px PNGs in desktop/resources/tray. Native menu not checked visually in a built app.
…devices; scenario creation redone - New quick-scenes.js: lists NX.SCENES that actually affect paired devices, per-device preview, run and save helpers. - Tap-to-run tab: ready scenes from real devices, honest empty state without devices, LAN failures reported after run. - Scenario creation page rewritten: scene choice with preview, quick suggestions with real time triggers, time/device/sensor/weather triggers, validation. - Home tap-to-run cards with a sceneId now run the scene. - Not verified with real hardware; location/security-mode triggers do not exist yet.
…e prefills its suggested time
…estions); other scenario pages restored
… automation page unchanged
…dy scenes, scene previews)
…rds, no 'see more' button
…odes above the input (horizontal scroll)
…ocks when idle, stacks above it, avoids bottom bars
…ons; status and support replies only for explicit requests
…w visible - quick-scenes: scene description is built from the paired devices' real actions (generic text only when no device matches); saved items use it too - nexus-skills: selecting a scene scrolls the "what happens" preview fully into view - nexus-ui.css: no square focus ring on the chat input inside its rounded bar (dark mode)
…of keeping 'devices set'
nexus-select.js turns every native <select> into a styled button + listbox (light/dark, keyboard, opens upward when short of room); the native select stays in the DOM so values and change events keep working. Covers feedback topic, household role, energy plan, tuya version, device pickers, and selects added later.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Combines #164 and #165 plus SSDP discovery (desktop): candidates from SSDP are identified first, then the subnet sweep continues. Multicast send checked against a real router; no smart device verified. Close #164/#165 in favour of this one.