Functions that still cant work:

• active button
• attribute loading
• Tooltip for the panel view, show the complete notification endpoint
• re.compile('.') is showing for pattern rather than the actual content "."
• use description as header in panel, and show id bellow, maybe also with tooltips when it is too long
• (optional) dynamically collapsable list for showing all entities

@sbanoeon I saw that the templates of the subscriptions module are using a lot of HTMX. I personally don't have much experience with that and the other modules are not using it. What is your opinion? Should we keep it here?

@djs0109 I think HTMX was a good way of implementing some dynamic functionalities in the subscriptions module. I would suggest to keep it. We can further use it in new features in future too.

The entity_set gives an error of missing managementForm, which makes the validation fail.

I would rewrite a parser that gets the data of entity_id/parttern/type from the request data.

@sbanoeon could you also have a look at the issue of the attributes?

reminder: we need to pull from development

@djs0109 Could you please have a look at the changes?

@sbanoeon, you can test with the following cases:

Normal HTTP

{
    "notification": {
        "http": {
            "url": "http://localhost:1234"
        },
        "attrs": ["temperature", "humidity"],
        "onlyChangedAttrs": true
    }
}

Normal MQTT

{
    "notification": {
        "mqtt": {
            "url": "mqtt://mosquitto:1883",
            "topic": "a/test/topic"
        },
        "attrs": []
    }
}

Custom MQTT with Plain Text Payload

{
    "notification": {
        "mqttCustom": {
            "url": "mqtt://mosquitto:1883",
            "topic": "a/test/topic",
            "payload":
                "The value of the %22temperature%22 attribute %28of the device ${id}, ${type}%29 is ${temperature}. Humidity is ${humidity} and CO2 is ${co2}."
        },
        "attrs": ["temperature", "humidity", "co2"],
        "onlyChangedAttrs": false
    }
}

Custom MQTT with JSON Payload

{
    "notification": {
         "mqttCustom": {
              "url": "mqtt://mosquitto:1883",
              "topic": "a/test/topic",
              "json": {
                  "t": "${temperature}",
                  "h": "${humidity}",
                  "c": "${co2}"
              }
          },
          "attrs": ["temperature", "humidity", "co2"],
          "onlyChangedAttrs": false 
      } 
}

Custom MQTT with NGSI Payload

{
    "notification": {
         "mqttCustom": {
              "url": "mqtt://mosquitto:1883",
              "topic": "a/test/topic",
              "ngsi": {
                  "id": "prefix:${id}",
                  "type": "newType",
                  "temperature": {"value": 123, "type": "Number"},
                  "co2_new": {"value": "${co2}", "type": "Number"}
              }
          },
          "onlyChangedAttrs": false 
      } 
}

@djs0109 review reminder

@sbanoeon All test cases seem to work. But do you have an idea why payload has no default value, but json and ngsi have the initial value "null"?

@djs0109 Since payload is of type string (CharField) and the default value for it is None, the crispy form initializes it with an empty text box. As for json and ngsi, they are of type JsonField and they are initialized with null as in the screenshot. Apparently this is how the crispy form handles it.

@sbanoeon thanks! I made a little adjustment. The rest looks good to me :) we can merge and close this PR