-
Notifications
You must be signed in to change notification settings - Fork 114
mqtt_json platform depreciated in Homeassistant 0.84 #321
Comments
So it seems like there is still some work ahead for #322, right? |
@thubot No, it doesn't break any lights - they might have been renamed to The I won't change this to the new "schema" format until something like esphomelib v1.11.0 or even 1.12. The reason is that many users don't immediately update their HA installations and if I upgrade to the newer format it would break it for everybody with older versions of HA. If I don't change it just yet, it is only a minor annoyance as a warning message gets logged, but lights still work. |
Ah, you're right about the renaming. I missed that, sorry. Seems like I have some UI and group editing to do. |
Operating environment/Installation (Hass.io/Docker/pip/etc.):
All
ESP (ESP32/ESP8266/Board/Sonoff):
All
Affected component:
All components that use the mqtt_json platform as output
Description of problem:
Changes to mqtt lights in homeassistant made
mqtt_json
platform depreciated, this is now incorporated in to one platform,light.mqtt
, with the type of mqtt light configured via a schema.This should only affect devices set up via mqtt discovery using the old type of config, and users who manually setup their lights in configuration.yaml
Pull that implemented this and describes the change is here: home-assistant/core#18227
Problem-relevant YAML-configuration entries:
Old configuration entry
New entry
Traceback (if applicable):
Additional information:
Due to the depreciation above, in HA 0.84.1 devices set up as light produce a warning as still using the old setup via Mqtt discovery
The text was updated successfully, but these errors were encountered: