Hubitat-TED5000.groovy This is an adaptation of the TED5000 Pro Hubitat device driver written by Daniel Terryn. TED stands for The Energy Monitor. The TED5000 can support up to four MTU’s. Each can be set for different roles, Load, Generation, Adjusted Load, Standalone, and Standalone (NET). This driver is customized for my TED5000 configuration with two MTU’s. MTU1 is on the line from the utility company and is set as “Adjusted Load”. MTU2 is on the lines from my 2 kWh solar array and is set as “Generation”. If your setup is different you may need to adjust the driver code as needed. On your TED5000 go to the http://TED5000/api/LiveData.xml file to see what values it returns. Use this as a guide to tweak the driver for your particular configuration. To install the driver in Hubitat: 1. Go to the Drivers code page select new driver and paste in the entire hubitat-ted5000.groovy file. Then click save. It should not report any errors. 2. Go to devices page and select “add Virtual Device”. On the Driver information page scroll down to the bottom of the “Type” drop down and select TED5000, in the “Device name” field give a name for your device. 3. Fill in the IP address and port for your TED5000 and select a refresh interval, and logging level. If you have authentication enabled then fill in the userid and password for your TED5000. At this point you should start to see current States values being populated. If not look at the log files for the TED5000 driver for a hint as to what is going wrong. You may need to increase the log level to a higher value such as debug. If everything is working you can select the following attributes for a dashboard item. Solar_power = Most recent power reading from MTU2 Solar_today = Cumulative power since midnight from MTU2 Solar_peak = The highest power reading since midnight from MTU2 Solar_saving_MTD = Cumulative cost since beginning of billing cycle from MTU2 Solar_saving_TDY = Cumulative cost since midnight from MTU2 Solar_power_average = Average daily power generate this billing cycle from MTU2 Solar_power_factor = Power Factor calculated from MTU2 Net_power = Net power usage MTU1 – MTU2 Adjusted_load = Total power used on MTU1 Voltage = Most recent voltage reading cost_today = Total Cumulative cost since midnight daily_max_power = Peak max power since midnight daily_min_power = Minimum power reading since midnight power_factor = power factor calculated on MTU1 Using the LiveData.xml file from your TED5000 as a guide add state variables and attributes or rename the existing state and attributes as needed to fit your configuration. The driver cam be downloaded from: https://github.com/andersonas25/Hubitat-TED5000.driver
3 Likes
I imagined I would have to start from scratch and found you driver, thanks. I am trying to use it with influxDB logger to log power (energy meter or power meter capability) and voltage but all I get is voltage, never power. I am not too familiar with this coding platform so it could take me a while to figure out by myself, any help is appreciated.
Update: OK, I just changed the variable name Net_power to power and that did it.
The TED5000 API doc is here:
http://files.theenergydetective.com/docs/TED5000-API-R330.pdf
Not 100% current but the differences are minor additions.
Thanks I already had that doc. I think the problem is the Hubitat platform expects power and voltage to be stored in attributes with the names "voltage" and "power" as part of the "capabilities" scheme. "Voltage" was already in your driver but you used "Net_power" instead of "power" in the driver.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
