I have nothing to do with the built in drivers. And your not the only 1 who has had issues with alexa forcing thermostats as a device instead of its primary function.
I know you don't. I tried the builtin drivers just to check if it was the driver or not. The builtin driver is discovered as a switch. If I use your driver all my shellys which were configured with your driver are now seen as Temperature Sensors. But it has always worked, never had issues with your drivers and the discovery process of Alexa.
Might be the Amazon Echo Skill App, it's the one responsible to let Alexa discover HE devices...I don't know if they changed something in latest HE firmware versions, in the last weeks I had 3 updates of HE fw.
So I can exclude any issue with your driver? Happy to hear that. I'd just like to know why it works with the builtin driver and not with the driver I always used, and want to continue using.
Maybe a stupid question, in Belgium we don't have alexa. I use Google but not via Hubitat (Shelly>Google). I don't see the benefits to put HE in between. Is this possible with Alexa to?
Correct but no one will admit to this yet... It seems that any device that also has the temperature capability along with switch has this issue... The Alexa skill is forcing temperature instead. The only work around I have found is to comment out the temperature capability then add to Alexa then restore the temperature capability.
@mike.maxwell can you look into this please.
1 Like
Hello All,
Recent entrant to home automation and a lot of shelly 2.5 lying around my house. I managed to add the shelly 2.5 using both the built in driver and the SHELLYUSA driver. The shelly USA driver provides a lot of information, however the on/off actions don't work. The native driver is a simple on/off that works.
Is there any reason why it wouldn't work?
clicking the on/off buttons in the device page doesn't do anything, but I switch it on from the shelly app and poll the device it reports "on" stage.
It works here just fine
Ok I Figured it out. It seems the "Prevent Accidental on/off" needed to be changed for it to work.
Thanks Borg, very thankful for the efforts you put in for this.
1 Like
You're welcome
It would be nice to have a confirmation by @mike.maxwell about the issue. I'm not quite sure if it's an Alexa limitation or an Amazon Echo Skill app limitation. In the latter case it could be fixed I guess.
Thanks for any advice Mike.
I am correct on this issue. If you have a contact switch that also reports temperature and add it to Alexa the default attribute used is temperature in Alexa and not open/close.
I tested this using a spare Iris contact sensor(3320-L) that also reports temperature and Alexa reports it as the default a temperature sensor instead of a contact sensor. Now even though Alexa defaults to this I can still make a rule for the contact sensor using Alexa.
I have to admit this is very odd behavior considering this never happened until recently. @mike.maxwell may not answer this and confirm this but I am very sure of my testing.
1 Like
I don't doubt your observations Scott, I just wanted to understand if the problem is the HE app that presents the devices to Alexa or it's Alexa that doesn't manage correctly devices with multiple capabilities. Since this odd behaviour never happened before, it could be some changes in Alexa APIs or the HE Echo skill implementation.
Seriously it's the SKILL not the API... in either case why it's happening is beside the point here. What it is doing is exactly what I have explained which makes it NOT a driver issue or a Shelly one.
This issue shouldn't even be in this thread and instead reported under the support threads.
I know it's not your driver because it worked before and the driver didn't change.
1 Like
Exactly... I think I even made a post about it.. I'll see if I did.
Edit: No I guess I didn't. You can make one if you wish.
I have a VERY VERY beta driver ready for the Window/Door2 device if anyone is interested in it. You need to have a MQTT broker for this to work.
What doesn't work correctly still is the vibration detection... that seems to be a hit-or-miss problem which may or maynot be because of the device or the Shelly FW. Everything else works as far as I can tell.
Actually I'm waiting for a beta driver of the Button1. 
Scott, do I simply comment this line in the switch driver?
capability "TemperatureMeasurement"
yes then add to alexa and after you have done that uncomment that line again and save the driver.
Comment by adding // to the beginning of that line.
The driver will use MQTT so you will need a broker to use it then.
I already have Mosquitto setup on my Synology NAS.
