I have one request and one question regarding your explanation above. I am not a developer so I need to understand the logic to try to replicate it. Do you mind on sharing the entire code above with the variables declaration and such? That would help me a lot regarding the programming on my side.
The other question is related to Alexa is any other voice command. Using that virtual device does it supports voice commands?
One more question, do I need to use the modified tasmota fo HE or can be the the normal one from the official release?
Is the custom firmware for this now redundant? Im looking in the console and I can see status updates from my Tasmota devices is being sent to my Smartthings hub.... How can I switch these to Hubitat? I cant find the websend details anywhere in the configuration of Tasmota....?
Thanks
I didn't, but I have tested it on a couple of devices and it does seem easier in Markus' version. Having done some more research it seems possible to configure notifications in the 'standard' Tasmota firmware, but perhaps requires some custom setup commands that I would need to research (can be done with Websend from what I can tell).
I dont know the benefits of each approach yet, but perhaps somebody else here does!
I've only used Marcus's version since it was specifically modified to fill the gaps needed with HE. By adding the IP address of the HE hub in the tasmota devices, and using Tasmota Device Manager to add them to the hub, all Tasmota devices act natively as a Z-wave or Zigbee device do.
First of all, great job and thanks for all the hard work bringing Tasmota into Hubitat more easily! Along with Tasmotizer, it is now relatively simple (even for me) to get devices integrated with Hubitat without RPi or other MQTT servers/hardware.
Still, I have a newbie question here. I flashed a Sonoff S31 with the tasmota-sensors-httphook-8.5.1.bin via serial/usb and was able to have Hubitat recognize the device utilizing the Tasmota Device Manager v1.1.1.1123T. I am able to control the plug through Hubitat, and the plug reports power usage with about a 15 - 20 second delay when a device is initially powered on. However, updates to the wattage power occurs only when I manually refresh the status of the device in Hubitat.
In my use case (monitoring power usage of a washer and dryer to announce when the laundry is done), I need to be able to monitor changes in power draw continuously, not just the power draw at the time the plug is turned on. I am currently not getting automatic status updates of changes in power usage (which I get from my Kasa EM smart plugs). I am trying to get away from cloud based solutions (my Kasa EM smart plugs do refresh automatically without polling but only every 5 minutes to keep from “overloading” the Hubitat) hence my move to Tasmota as I thought that T4HE was able to do this without polling.
Can anyone point me to a setting that I am missing to enable recording of power draw changes while the plug is left in the ON position? Or, is there another way to control the frequency of when the plug reports changes in power draw? I am using the S31 template and and everything seems to work except for the status changes.
TIA for any help!
Hi Sebastien,
Thank you so much for your quick response! I am using Markus’ version of Tasmota. I have sent the initialize command via the button on the parent device (although I’m not sure if this is what you were referring to). I’ll have to see if this works.
In Markus’ web interface, I had previously put in my Hubitat’s local IP address into the configuration menu where it asked for the hub ip (or httphook, don’t recall the exact terminology now). However, when I tried this, the plug became no longer recognized. So I resoldered and reflashed and got it into Hubitat again, but still with the problem with not reporting status updates. Again, thanks for your time and any further help.
Sebastien,
Thank you so much! I was just hitting initialize. I’ll try hitting configure first then initialize. BTW, in your experience, when this is properly set up, what is the refresh rate for the status updates?
When properly working, what is your experience as to the status refresh rate (want to avoid polling as much as possible with Hubitat due to potential hub/network issues)?
Has anyone had any luck with the New (I think) Gosund DS 1 Dimmers. I was able to get them on Tasmota using Tuya Convert Easy Peasy. I found a version 9.2.0.4 with scripting that works great via the Gui and manually on the dimmer but cannot get that to work with HE. If I use the 8.5.1 Tasmota4HE with http hooks it communicates with HE but functions do not work with the GUI, HE, or manually. Is there a version out there anywhere of Tasmota for HE that has scripting enabled? Can it be done from the console?
As far as I know the highest version of Tasmota that will work is the 8.5.1. In the 9.2.0.4 does it have the option to add in the ip of the hubitat in the HttpHook section. If not then I don't think it will work. Maybe try the 8.5.1 sensor version of Tasmota (YMMV).
No that is the issue, the 9.2.0.4 does have scripting enabled but no config for setting up HE ip address. I'll try that Sensor version of tas4he and see what I get.
I have some Zemismart YH002 blind motors that I am trying to get working in HE.
When I flash them with the latest Tasmota 9.2 I have to set them up manually and configure everything individually on both the device and in HE. This works except there are no HE specific things like web hook or prescense operating.
When I flash the last HE firmware 8.5.1 all the HE specific stuff like autodiscovery, web hooks, presecense work as detailed but the level slider on the device requires 2 change levels before the motor will move.
eg. the first change is always ignored and a second change is required
The slider itself responds perfectly and quickly from HE and also on the device GUI so I think its actually something in the device firmware, has any had this issue?
