hi @tomw
Yes it is a separate entry, but I don't know where to find the "sensor" section. Just as a note it brings through the voltage, just not the power and current.
Sorry I am not that good with HA, I am basically just running it to get some devices into Hubitat that are not supported directly.
This is how it is reported.
Usually the voltage on the grid is constant. So the current and power are directly related. isn't it two way of reporting the same thing?
I added PowerMeter support for the power device_class. This is in version 0.1.31, on GitHub and in the HPM listing.
Hello @ymerj ! The HTTPS option on the Home Assistant Device Bridge Driver is working really well with my HE on https. Thanks for that!! Is there any possibility of extending the https option to the main app ( Home Assistant Device Bridge App)? I know that the app is optional, but as far as I know, it is the only way to select the specific devices from HA that I want on my HE, correct?
The app is only required if you want to limit which HA entities to have mirrored into HE. When you use the driver only, anything that is supported by Home Assistant Device Bridge and which reports state changes from the HA websocket event interface will be added to HE.
The Home Assistant Device Bridge app uses the REST API instead of the ws/wss event interface used by the driver. Do you have HTTPS working on your HA web config pages? We can just try switching to HTTPS for the REST interface if that is already working. But you will have to make sure as a prerequisite that HE has the necessary certs to trust the HTTPS connection to HA.
Correct, I have HTTPS working on my HA config, and your driver with the HTTPS option is working really well. Not sure how I can make HE to have the necessary certs to trust HTTPS, but I am open to explore and test that! Thanks!!
The quickest path to check would be just to manually edit the Home Assistant Device Bridge code in Apps Code on your Hubitat installation.
Edit line ~187 to be https for the base uri. Then re-run the app configuration with Logs open to see what happens.
If it works, I can add it as a configurable option like what @ymerj did on the driver. If it fails, we'll have to investigate more to see what is missing.
You are right, I need to find how HE can trust the certificate from HA 
app:182021-09-25 14:23:40.692 debughttpGetExec() failed: Certificate for doesn't match any of the subject alternative names: [xxwhateverxx.duckdns.org]
To provide more visibility on my /config/configuration.yaml on HA I have:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
This cert is produced by the DuckDNS with Let's Encrypt support AddOn.
I am not using DuckDns for remote access (I haven't set port forwarding) but just for auto-managing the cert. However, DuckDns add-on configuration requires a "dummy" domain on it's configuration file (whatever.duckdns.org - I am not using that) and the cert will be issued to that domain, and even though it's a valid cert, HE won't trust it cause I am accessing HA using the IP address, not via the dummy domain.
Interesting, that's a weird one. Since you clearly know what you are doing, I'll ask: there's an option to disable HE checking the validity of the signature. We could enable that option, unless that defeats the purpose for what you're after.
I'm in the same boat and this is exactly what I would be after.
I'm running both Home Assistant and Hubitat and I have devices that are only compatible with one or the other, so I'd love to have the ability to control which devices that Hubitat picks up. I'm using the secure connection option on the driver but now I have duplicate devices in Hubitat.
modified the source myself and it's working perfectly.
Thanks for the pointer!
Quick note.. I also added an input and a command to pass a "require secure connection" to the device itself.
Would you mind submitting a pull request on GitHub for your changes?
I do not think it's possible. I am only using https due to some integrations require it to work. However, I will be moving these integrations to homebridge, and reverting my HA to HTTP. I prioritize this HE smart app, as managing HA entities from HE is amazing!
Is there any way that the driver could be made to support the cover template? With all the issues the HE is having with MyQ lately, it would be great to have it integrated to HE through Home Assistant. Thanks!
Submitted
Looks good. I merged your change. @pgux , please give the new version a try (0.1.32). It's available now on GitHub and through HPM.
I added the garage device_class in version 0.1.33, which is now available on GitHub and via HPM. Thanks for your help with testing, @g.shepperd. Please let me know if you have any issues with this version.
Download the Hubitat app
