MQTT Light/Templating Help

Configuration
4

Not for command_on_template it’s not. You have to supply the entity or attribute that holds the value in the template so it can be published. “brightness” as a value here means nothing. Hence your error

 Error parsing value: ‘value_json’ is undefined (value: on, template: {{ value_json.brightness }})

Try this in the developer tools template editor:

    command_on_template: >-
      {"state": "on"
        , "brightness": "{{ state_attr('light.office_level', 'brightness') | int }}"
        , "transition": "{{ state_attr('light.office_level', 'transition') | int }}"
      }

Also you have no else case for your if statements so leave them out or supply a default value in an else statement (128 or something).

      {%- if state_attr('light.office_level', 'brightness') is defined -%}
        , "brightness": "{{ state_attr('light.office_level', 'brightness') }}"
      {% else %]
        , "brightness":"128"
      {%- endif -%}
5

I see what you’re saying but that literally is what is here: MQTT Light - Home Assistant, and the docs says brightness and transition are allowed variables: MQTT Light - Home Assistant. Your example isn’t going to work because it’s a chicken and egg problem.

Again, pulling straight from the docs for this. I thought about an else statement but for brightness, in order for a light to be turned off brightness can’t be defined. For transition i wouldn’t mind a default value, but brightness was the issue.

6

Yeah ok I did not realise it had this:

Available variables: state, brightness, red, green, blue, white_value, flash, transition and effect.

7

I think I see what i need to do, i just am not quite sure how to do it. I need to set state_template and brightness_template based on an MQTT topic. IE this is what is in MQTT:

homeassistant/light/office_level/brightness 255
homeassistant/light/office_level/state on

Not sure how I use a template to extract that.

8

I’m having trouble understanding why this MQTT Light requires automations. I thought the purpose of the template schema is to provide complete flexibility to process received and transmitted payloads (without relying on automations).

Can you post a sample of the payload that is received (and, if not the same, the payload that is transmitted back to the light).

1 Like
9

I’m running two instances of HASS. One runs my Zwave network and the other is my “main” instance. (I’ve looked at zwave2mqtt but it won’t work for what i need). I’m basing my work off this thread: Automating the sharing of sensors and switches between HA's using MQTT Discovery and Statestream

And here is a copy/paste from MQTT-Explorer that shows all the values in MQTT. Includes the payload (what I want it to be).

last_updated = 2019-07-16T11:29:24.263374+00:00
brightness = 255
node_id = 50
value_index = 0
value_instance = 1
value_id = "72057594881605633"
friendly_name = "Office"
supported_features = 33
last_changed = 2019-07-16T11:29:24.263374+00:00
state = on
set = {"state": "on", "brightness": "255", "transition": "2"}

Edit: Maybe the issue is this. I’m trying to set the light based on the MQTT topics, which don’t have JSON values, and the light doesn’t pass the MQTT value in JSON (ie it uses the state and brightness topics, not what is in the set topic. So maybe I need to be using the json schema for lights instead? I just couldn’t get that working.

10

Thanks for the clarification. So those automations are based on RobDYI’s strategy to make entities discoverable (via MQTT Discovery) by another instance of Home Assistant.

In lieu of RobDYI’s strategy, you may wish to consider the following custom component:

Full disclosure: I have not tried it. However, others have and reported their success in this thread.

11

Sort of, i gave up trying to make them auto-discoverable (at least for lights, everything else I got working). I manually defined the lights to try and get them working.

Says it requires api_password which is going to be deprecated soon, right?

12

He added support for access tokens.

13

Ooo. Well I’m gonna hate throwing out literally tens of hours of work on the MQTT part (and I feel like I’m frustratingly close but not at the same time) but I just don’t know what else to do. I’ll maybe give it a try.

14

@123 I actually made some progress based on your posts here: Mqtt value template

This is now working:

state_template: "{{ 'on' if value == 'on' else 'off' }}"

Now just to get brightness_template working and i THINK i’m set. Could use some help. is it possible to template something like “if brightness is between 1 and 100 use {{brightness}} otherwise nothing?” Below is my stab at what I was thinking.

brightness_template: "{{ '{{brightness}}' if (value <=1 OR >= 100) else '' }}"

15

Not sure I understand the purpose of your state_template. It’s saying this:

If the received value is on then the state is on, otherwise it’s off.

If the received payload can be either on or off then there’s no need for the state_template.

You can create a template like that but that doesn’t mean it will work the way you expect. The purpose of the brightness_template is to supply a valid brightness level. An empty string ('') isn’t a valid brightness level.

The larger question is: If the payload doesn’t contain a value between 1 and 100, what does it contain? Zero? A number greater than 100 or less than zero?

16

I’m not 100% sure either. I may be able to remove it and test again, just not at the moment.

EDIT: Nope, it’s necessary. I get this error when i remove:

Exception in state_received when handling msg on 'homeassistant/light/office_level/state': 'off'
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/mqtt/light/schema_template.py", line 186, in state_received
    state = self._templates[CONF_STATE_TEMPLATE].\
AttributeError: 'NoneType' object has no attribute 'async_render_with_possible_json_value'

I think what I need to do is create an automation on the zwave HASS side that pushes a single payload with the information I need (particularly state and brightness). Right now i have 3 topics (set, state, and brightness) and it looks like i need 2 (set and state/brightness). I think i’ve figured out a way to push a change to MQTT when the brightness is changed so I’ll give that a shot.

I’ll keep messing around, but i appreciate your help. I’ll post an update if I figure out a work around

17

According to the documentation for MQTT Light using the JSON schema, state_template is optional. That means Home Assistant won’t complain if the state_template option is omitted. It will complain if you defined a blank state_template.

18

I think maybe it’s because of the way I defined my on/off commands. Idk, my solution seems to work so I’m not seeing a reason to stop using it unless there’s a bigger issue i’m not seeing.

19

I can’t comment because I haven’t seen what you’re working on. The only MQTT Light configuration you’ve shared is in the first post and that version uses a different state_template. In fact, that version appears to be handling a JSON-formatted payload whereas your most recent state_template isn’t.

:man_shrugging:

20

What i’m working on is exactly what I posted initially other than the recent change to state_template and removing brightness_template. And yea, only thing I can think of is the on/off command creates a json value to parse.

21

Ok, i’m really close but I feel like i’m taking one step forward and two steps back.

Here is the current config:

  - platform: mqtt
    schema: template
    name: Office Level
    command_topic: "homeassistant/light/office_level/set"
    state_topic: "homeassistant/light/office_level/state"
    command_on_template: >
      {"state": "on"
      {%- if brightness is defined -%}
      , "brightness": "{{ brightness }}"
      {%- endif -%}
      {%- if transition is defined -%}
      , "transition": "{{ transition }}"
      {%- endif -%}
      }
    command_off_template: >
      {"state": "off"
      {%- if transition is defined -%}
      , "transition": "{{ transition }}"
      {%- endif -%}
      }
    state_template: "{{ value }}"
    brightness_template:  "{{ value }}"

i KNOW that brightness part is wrong but here’s what’s messed up. I can control the light just fine. Switch it on/off, dim it, everything. It just throws an error of “Invalid brightness value received”. Which is annoying and i want to fix. The state part works 100% fine.

EDIT: I think i see the problem, and I don’t know the solution. The problem is for “brightness_template” it’s trying to find the value in /homeassistant/light/office/state. But the issue is, it’s not there. The value is in /homeassistant/light/office/brightness. But I can’t define brightness_command_topic like I can with the other variants of MQTT Light. So I think i’m stuck either 1) not having transitions and using the “default” light or 2) having transitions/brightness/what I want using the “template” light but getting spammed with errors all the time about how the brightness value isn’t correct. Sigh, damned if I do damned if I don’t.

22

What is the appearance and content of the data that is published to this topic? For example, does it contain sufficient information to determine the light’s state?

For example, let’s assume the payload is 0 when the light is turned off and an integer value greater than 0 when on. With this information we can create an appropriate state_template that would allow us to use this topic:

homeassistant/light/office_level/brightness

for the state_topic, instead of this one:

homeassistant/light/office_level/state

Therefore the brightness_template would be processing payloads from the brightness-related topic instead of the state-related topic … thereby eliminating the error messages.

23

Not going to work. The brightness does not get updated when the light gets turned off. IE this is the current output (notice the state is OFF but the brightness value is still 255)

office_level
state = on
last_updated = 2019-07-17T01:15:55.394507+00:00
last_changed = 2019-07-17T01:15:55.394507+00:00
node_id = 50
value_index = 0
value_instance = 1
value_id = "72057594881605633"
friendly_name = "Office"
supported_features = 33
brightness = 255

I think I’m going to take a different path. I realized only a few automations call things involving transitions, and I can move those to scenes. Move the scenes to the zwave instance and invoke them with an MQTT topic/payload. Reverted the MQTT lights to the “default” config and i can turn on/off and control brightness with no errors. I sincerely appreciate all your help though!