I’ve seen two strategies in stock drivers to report to ST Energy, which apparently mandates the reports must be spaced at least 15 minutes.
First strategy (no polling, no start-end info): assume you’re subscribed to the energy reports of the device so no need for polling, keep the time of the last time you reported to ST Energy and if it’s been more than 15 minutes, calculate the delta and emit the event.
Second strategy (polling, start-end): use polling every 15 minutes, keep the time of the last time you reported to ST Energy, calculate the delta and emit the event including a start and end time.
I find the first approach better since there’s no polling involved and no need to manage timers.
Also, the start and end attributes in the powerConsumptionReport events are prone to errors, especially if you have a custom driver and switch back to stock driver. In that case, the deltaEnergy will be correct since it’s calculated from the most recent value cached, but the start will be incorrect since it will be the last time the stock driver sent the report, not the last time a report was sent (by the custom driver).
Are you looking to certify a device and to be supported in SmartThings energy? Getting a device to appear there requires it to go through a special process during WWST certification.
I checked with the engineering team, and both approaches currently work in ST Energy. However, we encourage Partners to send a value in “end” and “start” for future reference and troubleshooting purposes.
Also, implementing the capability does not ensure the device will function with ST Energy. Only certified devices that have gone through the special process I mentioned earlier will work for certain.
@rboy It is certified, but is not showing with stock driver. It shows with @Mariano_Colmenarejo MC driver.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
13
Thanks, just realized it isn’t the Gen5 that’s why it’s not showing up. Having that said that it would be cool to have it work with non certified devices as long as the driver complies with the specs.
Is there any chance to see/learn exactly what “special process” is required in order to get an already certified WWST device to show and work in ST Energy.
An besides any possible certification fees, is there a public information on how to get this certification if its not only up to only standardised specs?
At the moment, I try to navigate between Aeotec support and ST support in order to understand, why an Aeotec SmartPlug/Outlet (with promoted energy measurement capabilities) does not work with all ST Services the way it should or can be.
RBoy
(www.rboyapps.com - Making SmartThings Easy!)
15
Looking at the latest driver code it appears the driver is handling everything is needed for the energy care service. Essentially the driver is doing most of the heavy lifting and it’s possible that the driver code doing these calculations could actually become part of hub core or built into the lua code framework itself and be handled automatically every time the driver reports energy usage. If that happens, then any driver that reports energy usage can technically be compatible with energy care without any additional certification requirements.
Once this happens, hundred of existing devices can automatically start showing up in energy care and you can get granular detail about which devices are using how much energy at what point across the home without any additional overhead
@nayelyz maybe this feedback can be provided to the technical team looking into this
Looks more like a business decision, not a technical one. If every device able to report energy to SmartThings would appear in SmartThings Energy, this press release introducing it as a groundbreaking partnership with a certain partner would not exist.
Although the situation is even more weird since some devices like the Tapo P110M are allowed into SmartThings Energy via the cloud but not via Matter 1.3! Talk about local-first!
Hi, @stillerson
This can only be done by the device’s manufacturer, who needs to contact partners@smartthings.com to receive assistance with the process.
Not that I’m aware of, each case is reviewed individually with the help of the Partners Management team.
For users who want certain features available on SmartThings that are not yet present, the suggestion is to contact the device manufacturer and explain the need for that feature. It will depend on them if they want to pursue its implementation.
