Issues

• Device cannot choose to support different alarm limits on Analogue Points and Extension Points

  LucidProtocol/Lucid-Specification#113 · Filter by author GCoxCasey opened on Aug 10, 2026
  1

• Connection Schedule Repeat Interval conflict between protocol spec and Device Profile.

  LucidProtocol/Lucid-Specification#112 · Filter by author GCoxCasey opened on Aug 6, 2026

• Should device profiles use $schema to reference the version of Lucid schema they validate against?

  LucidProtocol/Lucid-Specification#109 · Filter by author GCoxCasey opened on Jun 19, 2026

• deviceLinks.name should not be empty

  LucidProtocol/Lucid-Specification#107 · Filter by author GCoxCasey opened on Jun 8, 2026
  3

• FD must always upload full configuration

  LucidProtocol/Lucid-Specification#105 · Filter by author GCoxCasey opened on May 18, 2026

• Field Device Configuration .json sample missing Point objects for extension points

  LucidProtocol/Lucid-Specification#103 · Filter by author GCoxCasey opened on Apr 22, 2026
  1

• Off Scan clarifications

  LucidProtocol/Lucid-Specification#102 · Filter by author GCoxCasey opened on Mar 26, 2026

• SA Profile should be able to specify limits on number of objects attached to points

  Change Agreeddocumentation
  LucidProtocol/Lucid-Specification#101 · Filter by author GCoxCasey opened on Mar 4, 2026
  1

• Documentation of Override behaviour

  Change Agreeddocumentation
  LucidProtocol/Lucid-Specification#99 · Filter by author GCoxCasey opened on Feb 23, 2026
  1

• Initialisation of counter points

  Change Agreeddocumentation
  LucidProtocol/Lucid-Specification#98 · Filter by author GCoxCasey opened on Dec 16, 2025
  2

• reportEventsDirectly and respondCurrentDataDirectly clarifications

  LucidProtocol/Lucid-Specification#93 · Filter by author GCoxCasey opened on Sep 18, 2025
  1

• Lucid UP/data resilience when SA uses multiple servers

  LucidProtocol/Lucid-Specification#92 · Filter by author GCoxCasey opened on Sep 16, 2025

• Security level 3 - is this even possible

  bugdocumentation
  Bug

  LucidProtocol/Lucid-Specification#91 · Filter by author davisonm opened on Mar 13, 2025

• A means of identifying a service state would be helpful if multiple devices are published by a single service

  documentationenhancement
  Feature

  LucidProtocol/Lucid-Specification#89 · Filter by author SteveBeadle opened on Feb 27, 2025

• Current LWT mechanism doesn't quite give us a definitive state

  bugdocumentationhelp wanted
  LucidProtocol/Lucid-Specification#88 · Filter by author vtgav opened on Nov 29, 2024
  6

• Two addressing schemes for data reporting

  LucidProtocol/Lucid-Specification#84 · Filter by author pauljnew opened on Nov 29, 2024
  3

• Table 16 (RONC) configuration issues

  LucidProtocol/Lucid-Specification#82 · Filter by author VicKrawciw opened on Nov 26, 2024

• Word document editing issues

  LucidProtocol/Lucid-Specification#80 · Filter by author davisonm opened on Oct 23, 2024

• Update JSON Schema version from Draft 6 to latest version

  LucidProtocol/Lucid-Specification#75 · Filter by author davisonm opened on Oct 15, 2024

• Update JSON Schema to reflect mandatory or not

  LucidProtocol/Lucid-Specification#56 · Filter by author SteveBeadle opened on Jul 12, 2024
  1

• The documentation ought to be in a more appropriate format for collaboration

  documentation
  LucidProtocol/Lucid-Specification#49 · Filter by author devslashwill opened on Jul 11, 2024
  1

• Use of the word "optional" in tables

  Change Agreeddocumentation
  LucidProtocol/Lucid-Specification#38 · Filter by author davisonm opened on Jun 30, 2024
  1