Changes
- Removed debug code used in the last beta to test a specific problem #526
- Add version number in manifest.json (Change in HA) #525
- Fix MQTT problem with devices like roller, rgbw2, bulb, and dimmers. #534
- Add services.YAML (specification of implemented services) #530
- Add support for Shelly Motion #523
- Accept Shelly Button 1 that identifies it with SHBTN-2
- Add MQTT support client/broker modes (see more below)
- Add support for external sensors using an extender to Shelly 1/1PM
- Add support for Shelly Plug 1L
- Fixed a bug causing TCP connections to stay in the TIME_WAIT state
- Change unit from lux to lx
MQTT Support
MQTT support is added to two different modes that can run in parallel.
You can run CoAP and MQTT at the same time and add Shelly devices using CoAP, REST and/or MQTT.
The benefit of MQTT is that it working with VLANs and network equipment that not support CoAP/IGMP. The backside is that MQTT can't be enabled at the same time as the device is connected to Shelly Cloud, except for Shelly H&T.
Connect to an MQTT broker like mosquito etc
Specifying the address and login to your MQTT broker to make ShellyForHass automatically detect your devices and create entities for them in HA. You must also configure your Shelly devices also to connect to this MQTT broker.
shelly:
mqtt_server_host: "192.168.1.100"
mqtt_server_port: "1883" #Default 1883
mqtt_server_username: "user"
mqtt_server_password: "password"
Build-in MQTT server
By configuring the mqtt_port the plugin starts listening for clients (Shelly devices) to connect to that port. It can be configured in the integration GUI or in config.yaml depending on how it is installed in your system. Please do not use port 1883 for this to avoid collision with other MQTT brokers.
shelly:
mqtt_port: 1888
In the Shelly config, you only have to enter the server address to point to the IP of HA and the port specified above in the config. This is just a simple MQTT server without authentication. So do not publish it on public networks etc.
