Troubleshooting and Support
While T4HE has proven to be a robust and reliable platform during Beta testing there will undoubtedly be some problems. Before requesting assistance please be sure that you have followed these basic troubleshooting steps. This will shorten the time it takes to resolve your problem.
When a new Tasmota device is created it is the job of the Universal Parent Driver to query the Tasmota hardware to determine its nature and install the most appropriate child driver. All Tasmota devices in T4HE will have a parent driver and at least one child driver. In the example below you can see that no child driver has been created.
The first step to correct this problem is to open the parent driver and click on the Configure command. This causes the parent driver to query the Tasmota hardware, determine the most appropriate driver and create the child device. If all is successful it should look something like this after you do a refresh of your browser.
If a device fails to configure correctly or does not work as expected it will be necessary to gather some information to provide to the community for support. T4HE has been made available to the public but carries no guarantees for compatibility or support. That said, the Hubitat community is an active one and the developer intends to continue to improve and expand the capabilities of T4HE. The first step is to enable logging on the device in question.
-
Go to the Parent Driver
-
Locate the preferences section and make sure Enable Debug Logging is enabled.
-
Open another browser window and select Logs within HE.
-
Now repeat the device command that caused the initial problem.
-
To limit the display of information to just the device in question click the specific device among those listed at the top of the screen or on the device's ID on the left (dev:173 in the screenshot below).
In the above example the error was caused by some mal-formed JSON caused by an invalid MQTT grouptopic of the items within the quotation marks (“”). Changing Grouptopic to any valid string solved the problem.
-
Now submit this information along with a description of the problem to the Hubitat Community forum at https://community.hubitat.com/c/support. Don’t forget to turn logging back off when you are done.
This concludes the first documentation release of Tasmota for Hubitat Elevation.