Hue emulation and alexa

202 views
Skip to first unread message

James

unread,
Dec 11, 2020, 3:15:06 AM12/11/20
to TasmotaUsers
I only recently discovered Tasmota and have been impressed with how well it works, finally something that makes "smart" plugs and switches more than a gimmick tied to an unreliable smartphone app that probably won't work anymore once the phone is only a few years old. IMO a viable home automation system needs to last decades so open-ness, no cloud requirement and multiple hardware choices is a must. As finicky as X10 modules were, I used the same hardware for 25 years until it just got too hard to make it work reliably with so many switchmode power supplies spraying noise onto the power line. 

Anyway I had a pile of esp8266 boards so I built a couple of relay boards to play around with Tasmota while waiting for the Sonoff modules I ordered to arrive here from China. I was amazed how painlessly the Wemo emulation was, I enabled it and it just worked, I can control it from my laptop using the command line or web interface, from a Python script on my Raspberry Pi, from the web interface on my phone and even the Echo my mother in law gave us several years ago, it just worked right off the bat.

So being impressed with that, I decided to try out the Philips Hue emulation so I wired up an RGB LED to another esp8266 board, verified the web interface works to control it, everything seems great. So now I try to get alexa to find it and.. nothing. I've tried everything I can think of, I even managed to find a couple of Hue compatible apps that would work on iOS10 and they were able to find it but alexa stubbornly refuses. I tried enabling log level 3 and I can see loads of UPNP messages from my Plex server and security camera NVR and occasionally one will show up from the Echo during the scan but it never finds it. Is this just broken? Should it work with the early gen Echo that we have? I'm kind of at my wit's end with this, I didn't even plan to use the Echo to control lights in the first place but now it's just bugging me that I can't get it to work. I don't have any smart home skills enabled, but the Wemo stuff works perfectly, it just doesn't support dimming which makes it kind of useless for most of my interior lighting. 

Philip Knowles

unread,
Dec 11, 2020, 3:25:12 AM12/11/20
to James, TasmotaUsers

just checking that you’ve read this page first

Alexa - Tasmota

Regards

 

Phil K

 

Sent from Mail for Windows 10

--
You received this message because you are subscribed to the Google Groups "TasmotaUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/18be3dec-832b-49d7-95fc-f73c14988f81n%40googlegroups.com.

 

Stephan Hadinger

unread,
Dec 11, 2020, 4:29:58 AM12/11/20
to TasmotaUsers
Main causes of Alexa not finding the Tasmota devices are:
1- multicast issue, enabling `WebLog 4` will show you if Alexa finds the device
2- broken third party Smart Home Alexa skill that may break the discovery process
3- some users have reported that it worked better if you close all Alexa phone apps and do the discovery from the Echo device (although I never had this issue).

Barry Parr

unread,
Dec 11, 2020, 5:58:15 AM12/11/20
to sonof...@googlegroups.com
just configured a spare board with 3 pwm's and hue
alexa found it
dunno what models I have but the sw ver is 4262172036

James

unread,
Dec 11, 2020, 12:52:23 PM12/11/20
to TasmotaUsers
Yes, I scoured the web looking for solutions and that page was one of the first things I came across and read.

There are no smart home skills enabled on the Echo, up until now we've really only used it for timers and reminders and for streaming music from radio stations and from my Plex server. 

We don't have the Alexa app installed on any devices and never have, the only Alexa-enabled device in the household is that one first gen Echo tower. 

Below is a segment of the log. 192.168.1.43 is the Plex server, .30 is the Echo, .100 is my security NVR. I asked Alexa to search for connected devices near the start of this snippet and at the end the response is that "she" couldn't find any connected devices, if you have Philips Hue press the button on the bridge and try searching again. This is Tasmota 9.1.0 running on a generic NodeMCU board. 


09:35:46 UDP: Packet (119)
09:35:46 UDP: Packet (119)
09:35:48 UDP: Packet (119)
09:35:48 UDP: Packet (119)
09:35:53 UDP: Packet (101)
09:35:55 UPP: Hue 3 response packets sent to 192.168.1.43:43933
09:35:56 UDP: Packet (107)
09:35:56 UDP: Packet (107)
09:35:56 UDP: Packet (119)
09:35:56 UDP: Packet (119)
09:35:58 UPP: Hue 3 response packets sent to 192.168.1.30:50000
09:35:58 HTP: Hue setup
09:35:59 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF/lights) from 192.168.1.30
09:35:59 HTP: Hue Result ({"63634769":{"state":{"on":false,"bri":212,"colormode":"hs","xy":[0.52203,0.43049],"hue":6918,"sat":201,"alert":"none","effect":"none","reachable":true},"type":"Extended color light","name":"Hue","modelid":"Generic","manufacturername":"Tasmota","uniqueid":"cc:50:e3:3c:af:d5:00:11-1"}})
09:35:59 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF) from 192.168.1.30
09:35:59 WIF: Checking connection...
09:36:02 UDP: Packet (101)
09:36:02 UDP: Packet (119)
09:36:03 UDP: Packet (101)
09:36:04 UPP: Hue 3 response packets sent to 192.168.1.100:53411
09:36:04 HTP: Hue setup
09:36:05 UDP: Packet (119)
09:36:08 UDP: Packet (119)
09:36:11 UDP: Packet (119)
09:36:13 UDP: Packet (101)
09:36:14 UDP: Packet (119)
09:36:14 UPP: Hue 3 response packets sent to 192.168.1.43:43933
09:36:17 UDP: Packet (119)
09:36:17 UDP: Packet (119)
09:36:19 UDP: Packet (119)
09:36:19 UDP: Packet (119)
09:36:20 WIF: Checking connection...
09:36:20 UDP: Packet (119)
09:36:21 UDP: Packet (119)
09:36:21 UDP: Packet (119)
09:36:21 UDP: Packet (119)
09:36:21 UDP: Packet (119)
09:36:21 UDP: Packet (119)
09:36:21 UDP: Packet (119)
09:36:22 UDP: Packet (119)
09:36:22 UDP: Packet (119)
09:36:22 UDP: Packet (119)
09:36:23 UDP: Packet (101)
09:36:25 UPP: Hue 3 response packets sent to 192.168.1.43:43933
09:36:33 UDP: Packet (101)
09:36:33 UDP: Packet (119)
09:36:35 UPP: Hue 3 response packets sent to 192.168.1.43:43933
09:36:36 UDP: Packet (119)

Barry Parr

unread,
Dec 11, 2020, 3:48:35 PM12/11/20
to sonof...@googlegroups.com

James

unread,
Dec 11, 2020, 6:37:56 PM12/11/20
to TasmotaUsers
So does that mean that Amazon has broken or disabled Hue detection on the Gen 1 Echo devices? I'm starting to think I should just give up and forget the idea of using the echo to control anything, even if I do manage to get it working it's likely they'll break it at some point in the future.

That's the fundamental problem with so much of this IoT crap. It's all dependent on these cloud frameworks and mobile apps that are in a constant state of flux and these companies act like everyone should just buy all new gadgets every year, that's just completely unacceptable and will limit this stuff to being toys for geeks. I enjoy tinkering with gadgets but there's no way any of this will pass the wife test if once it's set up you can't just flip a switch or issue a command to turn the light on and have the light turn on, 100% of the time without any messing around the way it does with an old fashioned switch. If it works today, I need to know that it will work the same way 5 years from now or it's not even worth screwing with as anything more than a toy. 

Barry Parr

unread,
Dec 12, 2020, 3:42:41 AM12/12/20
to sonof...@googlegroups.com
did you try setoption109 ? it forces gen1 responses apparently .
I don't have any gen1 devices so can't test that.

Stephan Hadinger

unread,
Dec 12, 2020, 1:41:49 PM12/12/20
to TasmotaUsers
Gen 1 Echo never supported Hue devices. Supported started with Echo 2nd Gen.

Your logs show that Tasmota receives UPNP requests from 3 different devices which is not normal. Try again and disable/disconnect your Plex and NVR.

James Sweet

unread,
Dec 12, 2020, 3:20:06 PM12/12/20
to Stephan Hadinger, TasmotaUsers
Maybe ours is 2nd gen then? I don't really know, we've had it for several years and I don't even remember when they came out, I never paid any attention to that until we had one.

I tried disconnecting the Plex server from the network today and ran several scans without any luck, it starts scanning, then I can clearly see the activity show up in the Tasmota log but then at the end it says no devices detected blah blah if you have Philips Hue press the button on the hub and blah blah blah. I looked at the Hue skill in the Amazon account and I see a bunch of low reviews this month with comments saying it isn't working so I wonder if something is broken with this particular combination of things? I tried enabling that skill but it requires an account so I made a Hue account with an email address I use for spammy stuff and tried but that couldn't find any Hue stuff either. At this point it's just bugging me, I wish Tasmota supported Wemo dimmers because the Wemo switch emulation is working flawlessly, it has picked that up every time right away. It doesn't support dimming though and I have most of my interior lighting on dimmers.


12:07:57 HTP: Hue setup
12:07:58 WIF: Checking connection...
12:08:07 UDP: Packet (107)
12:08:07 UDP: Packet (107)
12:08:07 UDP: Packet (119)
12:08:07 UDP: Packet (119)
12:08:09 UPP: Hue 3 response packets sent to 192.168.1.30:50000
12:08:10 UDP: Packet (119)
12:08:10 UDP: Packet (119)
12:08:10 UDP: Packet (119)
12:08:10 UDP: Packet (119)
12:08:10 UDP: Packet (119)
12:08:10 UDP: Packet (119)
12:08:10 UDP: Packet (119)
12:08:10 UDP: Packet (119)
12:08:11 HTP: Hue setup
12:08:11 UDP: Packet (119)
12:08:12 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF/lights) from 192.168.1.30
12:08:12 HTP: Hue Result ({"63634769":{"state":{"on":false,"bri":212,"colormode":"hs","xy":[0.52203,0.43049],"hue":6918,"sat":201,"alert":"none","effect":"none","reachable":true},"type":"Extended color light","name":"Hue","modelid":"Generic","manufacturername":"Tasmota","uniqueid":"cc:50:e3:3c:af:d5:00:11-1"}})
12:08:12 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF) from 192.168.1.30
12:08:14 UDP: Packet (119)
12:08:15 UDP: Packet (119)
12:08:16 UDP: Packet (119)
12:08:17 UDP: Packet (119)
12:08:17 UDP: Packet (119)
12:08:18 UDP: Packet (119)
12:08:18 WIF: Checking connection...
12:08:20 UDP: Packet (119)
12:08:23 UDP: Packet (119)
12:08:26 UDP: Packet (119)
12:08:30 UDP: Packet (101)
12:08:32 HTP: Hue setup
12:08:38 WIF: Checking connection...
12:08:46 UDP: Packet (107)
12:08:47 UDP: Packet (107)
12:08:47 UDP: Packet (119)
12:08:47 UDP: Packet (119)
12:08:49 HTP: Hue setup
12:08:49 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF/lights) from 192.168.1.30
12:08:49 HTP: Hue Result ({"63634769":{"state":{"on":false,"bri":212,"colormode":"hs","xy":[0.52203,0.43049],"hue":6918,"sat":201,"alert":"none","effect":"none","reachable":true},"type":"Extended color light","name":"Hue","modelid":"Generic","manufacturername":"Tasmota","uniqueid":"cc:50:e3:3c:af:d5:00:11-1"}})
12:08:50 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF) from 192.168.1.30
12:08:59 WIF: Checking connection...
12:09:05 UDP: Packet (101)
12:09:06 HTP: Hue setup
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:10 UDP: Packet (119)
12:09:19 WIF: Checking connection...
12:09:20 CMD: setoption109 1
12:09:20 SRC: WebConsole from 192.168.1.20
12:09:20 CMD: Group 0, Index 109, Command "SETOPTION", Data "1"
12:09:20 RSL: RESULT = {"SetOption109":"ON"}
12:09:21 CFG: Saved to flash at FB, Count 877, Bytes 4096
12:09:29 UDP: Packet (107)
12:09:29 UDP: Packet (107)
12:09:29 UDP: Packet (119)
12:09:30 UDP: Packet (119)
12:09:31 UPP: Hue 3 response packets sent to 192.168.1.30:50000
12:09:31 HTP: Hue setup
12:09:32 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF/lights) from 192.168.1.30
12:09:32 HTP: Hue Result ({"63634769":{"state":{"on":false,"bri":212,"colormode":"hs","xy":[0.52203,0.43049],"hue":6918,"sat":201,"alert":"none","effect":"none","reachable":true},"type":"Extended color light","name":"Hue","modelid":"Generic","manufacturername":"Tasmota","uniqueid":"cc:50:e3:3c:af:d5:00:11-1"}})
12:09:32 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF) from 192.168.1.30
12:09:39 WIF: Checking connection...
12:09:40 UDP: Packet (101)
12:09:42 HTP: Hue setup
12:10:00 WIF: Checking connection...
12:10:00 UDP: Packet (107)
12:10:01 UDP: Packet (107)
12:10:01 UDP: Packet (119)
12:10:01 UDP: Packet (119)
12:10:02 UPP: Hue 3 response packets sent to 192.168.1.30:50000
12:10:02 HTP: Hue setup
12:10:03 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF/lights) from 192.168.1.30
12:10:03 HTP: Hue Result ({"63634769":{"state":{"on":false,"bri":212,"colormode":"hs","xy":[0.52203,0.43049],"hue":6918,"sat":201,"alert":"none","effect":"none","reachable":true},"type":"Extended color light","name":"Hue","modelid":"Generic","manufacturername":"Tasmota","uniqueid":"cc:50:e3:3c:af:d5:00:11-1"}})
12:10:03 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF) from 192.168.1.30
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:10 UDP: Packet (119)
12:10:15 UDP: Packet (101)
12:10:15 UDP: Packet (119)
12:10:16 UDP: Packet (119)
12:10:17 HTP: Hue setup
12:10:17 UDP: Packet (119)
12:10:18 UDP: Packet (119)
12:10:20 WIF: Checking connection...
12:10:40 WIF: Checking connection...
12:10:44 RSL: STATE = {"Time":"2020-12-12T12:10:44","Uptime":"0T01:10:09","UptimeSec":4209,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"POWER":"OFF","Dimmer":83,"Color":"D4962D","HSBColor":"38,79,83","Channel":[83,59,18],"Scheme":0,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"Synergy","BSSId":"9C:3D:CF:92:9D:23","Channel":1,"RSSI":90,"Signal":-55,"LinkCount":1,"Downtime":"0T00:00:03"}}
12:10:50 UDP: Packet (101)
12:10:52 UPP: Hue 3 response packets sent to 192.168.1.100:53411
12:10:52 HTP: Hue setup
12:11:00 WIF: Checking connection...
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:10 UDP: Packet (119)
12:11:21 WIF: Checking connection...
12:11:22 UDP: Packet (107)
12:11:22 UDP: Packet (107)
12:11:23 UDP: Packet (119)
12:11:23 UDP: Packet (119)
12:11:25 UPP: Hue 3 response packets sent to 192.168.1.30:50000
12:11:25 HTP: Hue setup
12:11:25 UDP: Packet (101)
12:11:25 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF/lights) from 192.168.1.30
12:11:25 HTP: Hue Result ({"63634769":{"state":{"on":false,"bri":212,"colormode":"hs","xy":[0.52203,0.43049],"hue":6918,"sat":201,"alert":"none","effect":"none","reachable":true},"type":"Extended color light","name":"Hue","modelid":"Generic","manufacturername":"Tasmota","uniqueid":"cc:50:e3:3c:af:d5:00:11-1"}})
12:11:25 HTP: Hue API (/5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF) from 192.168.1.30
12:11:26 HTP: Hue setup
12:11:41 WIF: Checking connection...
12:12:00 UDP: Packet (101)
12:12:01 WIF: Checking connection...
12:12:02 UPP: Hue 3 response packets sent to 192.168.1.100:53411
12:12:02 HTP: Hue setup
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:10 UDP: Packet (119)
12:12:14 UDP: Packet (119)
12:12:15 UDP: Packet (119)
12:12:15 UDP: Packet (119)
12:12:16 UDP: Packet (119)
12:12:16 UDP: Packet (119)
12:12:17 UDP: Packet (119)
12:12:17 UDP: Packet (119)
12:12:18 UDP: Packet (119)
12:12:20 UDP: Packet (119)

Stephan Hadinger wrote:
You received this message because you are subscribed to a topic in the Google Groups "TasmotaUsers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonoffusers/zeCJ5OFOzeE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/98cfea6d-24e2-4e01-8657-d05d49e22a23n%40googlegroups.com.

Stephan Hadinger

unread,
Dec 13, 2020, 1:54:05 PM12/13/20
to TasmotaUsers
Your logs still show 2 different IP addresses: 192.168.1.30 and 192.168.1.100. This could be the cause of the problem. Please disconnect BOTH devices (as said before).

I'm surprised by the id Alexa received: `5Yz6bK0EIvaWrYgFLqk5oiRzViKpyjKZxjOD7UXF`, it should be a smaller value. What is your Tasmota version?

Also, when pairing, just select "Others" in the Alexa app, don't select a Hue device. Don't install the Philips Hue Alexa skill, it will be of no help.

James Sweet

unread,
Dec 13, 2020, 2:16:41 PM12/13/20
to Stephan Hadinger, TasmotaUsers
I'll have to try that later, the NVR and wiring is not easily accessible for security reasons and the Plex server is often in use so I have to find a window when nobody is using it before I unplug it. I the NVR shows up much more rarely in the logs though, I did multiple discovery cycles without anything from that showing up.

Tasmota is the latest version as of a few days ago:

Program Version    9.1.0(tasmota)
Build Date & Time    2020-11-07T11:57:45
Core/SDK Version    2_7_4_5/2.2.2-dev(38a443e)

I don't have the Alexa app, we've never had the app installed on anything and it isn't supported on iOS 10 so I can't use it anyway. There are no smart home skills installed at all, I tried to install one via the web portal when I was messing with it but aborted when that didn't find the Hue either. The only Alexa enabled device in our home is the Echo which I confirmed is a first generation unit which you said earlier won't work. I'm confused though because Alexa certainly is aware of Hue devices and specifically mentions to push a button on the bridge. If Hue is not supported by this hardware then that's a huge fail on Amazon's part to have every indication of supporting something but not actually support it. Can the first gen devices control Hue lamps once they have been discovered by a later generation device?


Stephan Hadinger wrote:

Stephan Hadinger

unread,
Dec 13, 2020, 3:11:10 PM12/13/20
to TasmotaUsers
Looking at your logs, they are not detailed enough. Can you set `Weblog 4` or `Seriallog 4`
You should see something like:
```
21:09:30 UPP: Hue 3 response packets sent to 192.168.x.xx:50000
21:09:32 HTP: Hue setup
21:09:33 HTP: Hue API () from 192.168.x.xx
21:09:33 HTP: Hue POST args ({"devicetype": "Echo"})
21:09:33 HTP: Hue Authentication Result ([{"success":{"username":"67b1e9"}}])
21:09:33 HTP: Hue API (/67b1e9/lights) from 192.168.x.xx 
```

The Echo 1st gen is this one Echo1.jpg. I believe it's the only one that has no support for Philips Hue.

James Sweet

unread,
Dec 13, 2020, 3:53:45 PM12/13/20
to Stephan Hadinger, TasmotaUsers
That was with weblog 4, that's all it gives me. 

Yep, that's the one we have. If it doesn't support Hue then Amazon screwed up because it acts like it supports it, the search specifically mentions Philips Hue, it just doesn't work. 

On Dec 13, 2020, at 12:11 PM, Stephan Hadinger <stephan....@gmail.com> wrote:

Looking at your logs, they are not detailed enough. Can you set `Weblog 4` or `Seriallog 4`
You should see something like:
```
21:09:30 UPP: Hue 3 response packets sent to 192.168.x.xx:50000
21:09:32 HTP: Hue setup
21:09:33 HTP: Hue API () from 192.168.x.xx
21:09:33 HTP: Hue POST args ({"devicetype": "Echo"})
21:09:33 HTP: Hue Authentication Result ([{"success":{"username":"67b1e9"}}])
21:09:33 HTP: Hue API (/67b1e9/lights) from 192.168.x.xx 
```

The Echo 1st gen is this one <Echo1.jpg>. I believe it's the only one that has no support for Philips Hue.

James

unread,
Dec 30, 2020, 2:13:47 PM12/30/20
to TasmotaUsers
So just an update here, I never did get the standalone Tasmota devices with Hue emulation to be picked up by Alexa. I set that aside and worked on getting a Home Assistant server set up and then the other day on a whim I tried enabling Hue emulation on that and was surprised when the echo picked it up immediately and found all of the devices. I don't know why it wasn't working before, although there is a note in the config for emulated Hue that it stopped working on other ports or something to that effect. Anyway whatever the reasons, it's working brilliantly at the moment, here's hoping it keeps working. Home Assistant is fantastic but the documentation is awful so setting anything up is 10x as hard as it ought to be but hopefully that will gradually improve. 

Anil Garg

unread,
Sep 20, 2023, 4:52:34 PM9/20/23
to TasmotaUsers
I too have found this to be true. I love Tesmota but I think it works best with MQTT.

Philip Knowles

unread,
Sep 20, 2023, 11:39:41 PM9/20/23
to Anil Garg, TasmotaUsers
Tasmota's basic premise is for MQTT (it's what the M in Tasmota stands for - Theo Arends Sonoff MQTT Over The Air).


From: sonof...@googlegroups.com <sonof...@googlegroups.com> on behalf of Anil Garg <anilga...@gmail.com>
Sent: Wednesday, September 20, 2023 9:52:33 PM
To: TasmotaUsers <sonof...@googlegroups.com>
Subject: Re: Hue emulation and alexa
 
Reply all
Reply to author
Forward
0 new messages