Error rendering payload: 'None' has no attribute 'state'

[MrGibbage]

When I try to turn my family room KPL load on and off with Home Assistant, the light doesn't do anything and I get the following error in my log

2022-01-15 10:25:36.695 DEBUG Mqtt: Received PUBLISH (d0, q0, r0, m0), 'insteon/4c.f9.cb/set/1', ...  (2 bytes)
2022-01-15 10:25:36.696 INFO KeypadLincDimmer: KeypadLinc message insteon/4c.f9.cb/set/1 b'ON'
2022-01-15 10:25:36.701 ERROR MsgTemplate: Error rendering payload: 'None' has no attribute 'state'
2022-01-15 10:25:36.703 ERROR MsgTemplate: Template was: 
{ "cmd" : "{{json.state.lower()}}"
  {% if json.brightness is defined %}
      , "level" : {{json.brightness}}
  {% endif %}
  {% if json.transition is defined %}
      , "transition" : {{json.transition}}
  {% endif %} }
2022-01-15 10:25:36.704 ERROR MsgTemplate: Data passed was: {'value': 'ON', 'json': None}
2022-01-15 10:25:36.705 DEBUG MsgTemplate: Input template render: 'None'

And here's my KPL definition:

 keypad_linc:
    btn_state_topic: "insteon/{{address}}/state/{{button}}"
    btn_state_payload: '{ "state" : "{{on_str.upper()}}", "brightness" : {{level_255}}, "reason" : "{{reason}}" }'
    dimmer_state_topic: "insteon/{{address}}/state/1"
    dimmer_state_payload: >
      { "state" : "{{on_str.upper()}}", "brightness" : {{level_255}}, "reason" : "{{reason}}" }
    btn_on_off_topic: "insteon/{{address}}/set/{{button}}"
    btn_on_off_payload: '{ "cmd" : "{{value.lower()}}" }'
    dimmer_level_topic: "insteon/{{address}}/set/1"
    dimmer_level_payload: >
      { "cmd" : "{{json.state.lower()}}"
        {% if json.brightness is defined %}
            , "level" : {{json.brightness}}
        {% endif %}
        {% if json.transition is defined %}
            , "transition" : {{json.transition}}
        {% endif %} }
    btn_scene_topic: "insteon/{{address}}/scene/{{button}}"
    btn_scene_payload: '{ "cmd" : "{{json.cmd.lower()}}"
      {% if json.brightness is defined %}
      , "level" : {{json.brightness}}
      {% endif %}
      }'

Similarly, when I manually operate the switch, I don't get any feedback in Home Assistant. But there are no errors, so I have that going for me:

2022-01-15 10:45:19.512 INFO Protocol: Read 0x50: Std: 4c.f9.cb Type.ALL_LINK_BROADCAST mh:3 hl:2 grp: 01 cmd: 11 00
2022-01-15 10:45:19.513 DEBUG Protocol: Setting next write time: 10:45:19.685
2022-01-15 10:45:19.514 DEBUG MsgHistory: Received 1 hops, total 11 for 11 entries
2022-01-15 10:45:19.515 INFO Broadcast: Handling all link broadcast for 4c.f9.cb 'family room kpl'
2022-01-15 10:45:19.516 DEBUG Protocol: Setting next write time: 10:45:20.538
2022-01-15 10:45:19.516 INFO Base: Device 4c.f9.cb broadcast grp: 1 on: True mode: normal
2022-01-15 10:45:19.516 INFO Base: Setting device 4c.f9.cb (family room kpl) on True level 255 normal device
2022-01-15 10:45:19.519 UI KeypadLinc: KeypadLinc 4c.f9.cb LEDs changed to 11100001
2022-01-15 10:45:19.519 INFO StateTopic: MQTT received state 4c.f9.cb (family room kpl) on: {'is_on': True, 'level': 255, 'mode': <Mode.NORMAL: 'normal'>, 'button': 1, 'reason': 'device'}
2022-01-15 10:45:19.520 DEBUG Mqtt: Sending PUBLISH (d0, q1, r1, m132), 'b'insteon/4c.f9.cb/state/1'', ... (59 bytes)
2022-01-15 10:45:19.520 DEBUG Mqtt: MQTT publish insteon/4c.f9.cb/state/1 { "state" : "ON", "brightness" : 255, "reason" : "device" } qos=1 ret=1
2022-01-15 10:45:19.521 DEBUG Base: Found 1 responders in group 1
2022-01-15 10:45:19.521 DEBUG Base: Group 1 -> ['53.c1.0e']
2022-01-15 10:45:19.521 INFO Base: 4c.f9.cb (family room kpl) broadcast to 53.c1.0e for group 1
2022-01-15 10:45:19.521 DEBUG Mqtt: Received PUBACK (Mid: 132)
2022-01-15 10:45:19.522 DEBUG Mqtt: MQTT writing
2022-01-15 10:45:20.007 INFO Protocol: Read 0x50: Std: 4c.f9.cb Type.ALL_LINK_CLEANUP mh:2 hl:1 grp: 01 cmd: 11 01
2022-01-15 10:45:20.009 DEBUG MsgHistory: Received 1 hops, total 11 for 11 entries
2022-01-15 10:45:20.295 INFO Protocol: Read 0x50: Std: 4c.f9.cb Type.ALL_LINK_BROADCAST mh:3 hl:2 grp: 01 cmd: 06 00
2022-01-15 10:45:20.296 DEBUG MsgHistory: Received 1 hops, total 11 for 11 entries
2022-01-15 10:45:20.298 DEBUG Protocol: Setting next write time: 10:45:20.297
2022-01-15 10:45:20.298 DEBUG Protocol: Setting next write time: 10:45:20.469
2022-01-15 10:45:20.299 DEBUG Broadcast: Cleanup report for 4c.f9.cb, grp 1 success.
2022-01-15 10:45:27.156 INFO Protocol: Read 0x50: Std: 4c.f9.cb Type.ALL_LINK_BROADCAST mh:3 hl:0 grp: 01 cmd: 13 00
2022-01-15 10:45:27.158 DEBUG Protocol: Setting next write time: 10:45:27.156
2022-01-15 10:45:27.159 DEBUG MsgHistory: Received 3 hops, total 13 for 11 entries
2022-01-15 10:45:27.160 INFO Broadcast: Handling all link broadcast for 4c.f9.cb 'family room kpl'
2022-01-15 10:45:27.161 DEBUG Protocol: Setting next write time: 10:45:28.183
2022-01-15 10:45:27.162 INFO Base: Device 4c.f9.cb broadcast grp: 1 on: False mode: normal
2022-01-15 10:45:27.163 INFO Base: Setting device 4c.f9.cb (family room kpl) on False level 0 normal device
2022-01-15 10:45:27.171 UI KeypadLinc: KeypadLinc 4c.f9.cb LEDs changed to 11100000
2022-01-15 10:45:27.172 INFO StateTopic: MQTT received state 4c.f9.cb (family room kpl) on: {'is_on': False, 'level': 0, 'mode': <Mode.NORMAL: 'normal'>, 'button': 1, 'reason': 'device'}
2022-01-15 10:45:27.174 DEBUG Mqtt: Sending PUBLISH (d0, q1, r1, m133), 'b'insteon/4c.f9.cb/state/1'', ... (58 bytes)
2022-01-15 10:45:27.175 DEBUG Mqtt: MQTT publish insteon/4c.f9.cb/state/1 { "state" : "OFF", "brightness" : 0, "reason" : "device" } qos=1 ret=1
2022-01-15 10:45:27.176 DEBUG Base: Found 1 responders in group 1
2022-01-15 10:45:27.176 DEBUG Base: Group 1 -> ['53.c1.0e']
2022-01-15 10:45:27.177 INFO Base: 4c.f9.cb (family room kpl) broadcast to 53.c1.0e for group 1
2022-01-15 10:45:27.179 DEBUG Mqtt: Received PUBACK (Mid: 133)
2022-01-15 10:45:27.180 DEBUG Mqtt: MQTT writing
2022-01-15 10:45:27.300 INFO Protocol: Read 0x50: Std: 4c.f9.cb Type.ALL_LINK_CLEANUP mh:1 hl:0 grp: 01 cmd: 13 01
2022-01-15 10:45:27.302 DEBUG MsgHistory: Received 1 hops, total 13 for 11 entries
2022-01-15 10:45:27.524 INFO Protocol: Read 0x50: Std: 4c.f9.cb Type.ALL_LINK_BROADCAST mh:3 hl:2 grp: 01 cmd: 06 00
2022-01-15 10:45:27.526 DEBUG MsgHistory: Received 1 hops, total 13 for 11 entries
2022-01-15 10:45:27.527 DEBUG Protocol: Setting next write time: 10:45:27.527
2022-01-15 10:45:27.528 DEBUG Protocol: Setting next write time: 10:45:27.698
2022-01-15 10:45:27.528 DEBUG Broadcast: Cleanup report for 4c.f9.cb, grp 1 success.

Finally, here is how I have the light defined:

- platform: mqtt
  schema: template
  #brightness: true
  command_topic: 'insteon/4c.f9.cb/set/1'
  state_topic: 'insteon/4c.f9.cb/state/1'
  command_on_template: 'ON'
  command_off_template: 'OFF'
  unique_id: 'familyroomkpl'
  name: 'Family Room Fan Light'

Anyone see a way to fix this? Thanks in advance!

Skip

[MrGibbage]

@krkeegan , can you please take a look at this? I could sure use your help!

[krkeegan]

Using the discovery platform would be one way to avoid these issues. Otherwise you should review: https://github.com/TD22057/insteon-mqtt/blob/master/docs/Templating.md I put a lot of work into the instructions there. You can also review the 'discovery_entities" for keypadlincs here https://github.com/TD22057/insteon-mqtt/blob/master/insteon_mqtt/data/config-base.yaml to see how it is defined when using the discovery platform. Given what you have provided I would suspect that the following configuration in Home Assistant would work: ```yaml light: - platform: mqtt schema: json name: 'Family Room Fan Light' state_topic: 'insteon/4c.f9.cb/state/1' command_topic: 'insteon/4c.f9.cb/set/1' unique_id: 'familyroomkpl' brightness: false ```

…

On Wed, Jan 19, 2022 at 4:39 AM Skip Morrow ***@***.***> wrote: @krkeegan <https://github.com/krkeegan> , can you please take a look at this? I could sure use your help! — Reply to this email directly, view it on GitHub <#473 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXHXKZPZKN4LMIOWYXWUATUW2WH5ANCNFSM5MBEDRZQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[MrGibbage]

Thanks! I set these lights up a year ago, and I remember doing some work with that switch, but I don't remember the specifics. Anyway, your solution was perfect. I looked the those docs and they are very nice, and will help me with some other stuff I have planned.