Christian Schwinne
Christian Schwinne
Thank you :) I've had this issue with mDNS before. Often it helps to switch the LwiP versions to either 1.4 or 2 High Bandwith, one of them may solve...
@Matheus-Alvarenga that fix is already implemented in Espalexa 2.7.0 too, so it should help. If Espalexa does not work for you, but Fauxmo does, we need to look into how...
Only lights, however Alexa will still understand "set to x degrees" and set the device % accordingly. You can use `espalexaDevice->getDegrees()` to use this in your code.
> So there's not a way to have a thermostat interface in the alexa app? True unfortunately. Espalexa uses the legacy local Philips hue API, which by definition only supports...
Hi, yes, sure, it is easy to get the value as a percentage :) Just use `byte valueInPercent = espalexa.toPercent(brightness);`
That's unfortunate... Espalexa works with the hue protocol, so all Alexa will ever send is a brightness between 0 and 255. Thermostats and the like probably use a more specialized...
@eos1d3 that rate sounds bad. I'll let you know once I had time to run a few discovery tests.
Luckily they are not enforcing an encrypted connection on the local Hue api. Once they start doing it that would be problematic resource-wise. Of course you can use it, but...
Hi, this `response` was erraneously left in version 2.4.6 of Espalexa when building for ESP32. Please make sure you have the latest 2.4.7, the issue should be fixed there :)