在线时间:8:00-16:00
迪恩网络APP
随时随地掌握行业动态
扫描二维码
关注迪恩网络微信公众号
开源软件名称:NorthernMan54/homebridge-tasmota开源软件地址:https://github.com/NorthernMan54/homebridge-tasmota开源编程语言:TypeScript 89.4%开源软件介绍:Homebridge Plugin for Tasmota Devices that leverage's the Home Assistant Auto Discovery Function to configure and add devices. And remove the need to manually configure Tasmota devices with Homebridge. So far this has been tested with Switches/Outlets, Dimmers/Light's and temperature sensors ymmv for other devices. Features
Tasmota Device's Tested YMMV for other devices
Sensor types supported
Tasmota Devices that do not work or have issuesFor autodiscovery to work and the proper device to be created in Homebridge the device needs to include its 'device_class' as part of the discovery message. Majority of the basic sensor types that use GPIO pins do not include this type of information, but other sensors that use I2C do. An easy way to quickly determine if the Tasmota knows what type of device it is, is if the Tasmota page knows the type of sensor information. Like temperature. Installation / ConfigurationFor installation and configuration of the plugin please use the homebridge UI/console. Tasmota Device Config
I found that some of my devices were not using a unique Topic for devices and I needed to update the configuration to Topic: tasmota_%06X This showed up when looking at MQTT messages and I was seeing them with this Topic.
Device Removal or Device Configuration ResetIf Home Assistant Auto Discovery for a device is disabled, the accessory will be removed from homekit. Useful for cleaning up devices that have wacky configurations accidentally created while configuring your device.
Usefull Tasmota Device Optionssetoption30 - Enforce Home Assistant auto-discovery relay as lightsetoption37 - Remapping the RGBWcWw channels for lightsDiscovery OverridesPlease seeDEVICES.md for examples. Technical DetailsUnder the covers this plugin leverages the Home Assistant Auto Discovery Function (setOption19) built into the Tasmota firmware and the MQTT Discovery feature built into Home Assistant. And uses the information provided by the Tasmota device to configure the HomeKit Accessory automatically without requiring within Homebridge. Known issuesRGB Lights and Tasmota Versions greater 9.5.0Identified that with Tasmota versions greater than 9.5.0 that ability to control RGB light colours is not working. Override settings removed from config.json by Homebridge UIIdentified that the Homebridge UI removes the config.json setting Accessory Names DoubledAccessory names are doubled with Tasmota version 8.1.3 to 8.4 - This is an issue with Tasmota firmware and is being tracked here. As a workaround downgrade to Tasmota version 8.1 i.e. "Scanner Scanner" Phantom Devices or ServicesAs device discovery is leveraging Home Assistant MQTT Auto Discovery, it is using these retained messages on your MQTT server, and will create and recreate them based on these retained messages. To eradicate these phantom devices the retained messages for the appropriate accessory / device need to removed from your MQTT server using a tool like MQTT Explorer. The Home Assistant MQTT Auto Discovery messages live under the topic 'homeassistant/' and a device can have multiple messages that need to be removed depending on the number and type of services. If you make a mistake and accidentally delete a message for an active device, rebooting the device or setting 'setoption19 1' will recreate messages. If you change the configuration in Tasmota of an existing device, and the old characteristics are still visible, you will need to clean up the 'Home Assistant MQTT Auto Discovery' messages for the device then disconnect the device for the cleanup period. You can temporarily change the cleanup period to 0.125 which is approx 10 minutes if your in a hurry. Frequency of sensor information updatesFrequency of data updates is controlled by the Tasmota device itself and not the plugin itself. The plugin does not poll the device for status, but processes telemetry updates as they are received. The plugin watches for telemetry updates on the tele/SENSOR topic ie 'tasmota-5042/tele/SENSOR'. During initialization of the plugin, it sets the teleperiod option to 300 seconds ( 5 minutes ). This is done to force the device to refresh status immediately after plugin startup. And then further updates are published every 5 minutes by the accessory. To drive realtime updates of sensor value changes a rule would need to be created on the device to publish the new data on the appropriate tele/SENSOR topic for the device whenever a sensor changes value, something like this from the Tasmota rule cookbook. https://tasmota.github.io/docs/Rules/#transmit-sensor-value-only-when-a-delta-is-reached This is discussed in detail in this Tasmota issue arendst/Tasmota#2567 This is a sample Tasmota rule for BH1750 Illuminance sensor to send updates with every value change.
As a side effect the rule resets the Some Sample Device ConfigurationsDiscord ServerA channel #tasmota has been created on the Homebridge Discord Server. Credits
|
2023-10-27
2022-08-15
2022-08-17
2022-09-23
2022-08-13
请发表评论