Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

location MQTT entity can make a difference for avoiding "Property value_template is not allowed" #2987

Closed
WJ4IoT opened this issue Dec 21, 2023 · 1 comment
Labels

Comments

@WJ4IoT
Copy link

WJ4IoT commented Dec 21, 2023

Hi,

When I recently started with my first package in HA I noticed the following error which is not a real error because HA is working for this entity as expected. Clueless what I should do to update this in the src/language-service/src/schemas/ folder. Sorry for this.

Copy of the MQTT-entity

  number:
  - unique_id: uno_dwl_interval
    name: "DWL Interval"
    icon: mdi:camera-timer
    command_topic: "UNO/DWL/cmnd/interval"
    state_topic: "UNO/DWL/sensor"
    value_template: "{{ value_json.interval }}" # ignore error on value_template
    max: 12
    step: 1
    availability:
    - topic: "UNO/DWL/LWT"
      payload_available: "Online" # watch out case sensitive
      payload_not_available: "Offline"

Tested three locations for this entity:

  • part of configuration yaml -> error
  • part of a package inside the package folder -> error
  • part of the mqtt.yaml -> NO error (configuration.yaml includes line: "mqtt: !include mqtt.yaml"

The error pictured in Visual Code Studio:
image

Working with:

  • Homeassistant (2023.12.3) installed in a Docker
  • Visual Studio Code v1.85.1 installed on Window 11
  • Homeassistant Config Helper V1.39.0

Hope this information is sufficient.

@WJ4IoT WJ4IoT added the yaml label Dec 21, 2023
@frenck
Copy link
Collaborator

frenck commented Oct 1, 2024

This was fixed by #3156

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants