Alexa Smart Home Skill V3 is now live!

Tried that just now, sadly not working :confused:

Hi, i have a question regarding the alexa ios app: is it possible to show rollershutters inside a group as rollershutter? Like the light switches for example?

item config:

Rollershutter Elternbad_Nord “Elternbad Nord [%d %%]” { channel=“knx:device:652ac361:Rollladen_D6:Elternbad_Nord”, alexa=“RangeController.rangeValue” [category=“EXTERIOR_BLIND”, friendlyNames="@Setting.Opening", supportedRange=“0:100:10”, unitOfMeasure=“Percent”, actionMappings=“Close=100,Open=0,Lower=(+10),Raise=(-10)”, stateMappings=“Closed=100,Open=0”]}

Rollershutter Elternbad_Ost “Elternbad Ost [%d %%]” { channel=“knx:device:652ac361:Rollladen_D6:Elternbad_Ost”, alexa=“RangeController.rangeValue” [category=“EXTERIOR_BLIND”, friendlyNames="@Setting.Opening", supportedRange=“0:100:10”, unitOfMeasure=“Percent”, actionMappings=“Close=100,Open=0,Lower=(+10),Raise=(-10)”, stateMappings=“Closed=100,Open=0”]}

This is unfortunately not supported on the Alexa as of yet. It seems that only light and switch items are listed under a named group. Any other items would just be listed individually. I use the Android app and I am seeing the same behavior.

Ok thank you. I thought it could be handled by the property “category”.

Thanks for this post.

It helped me to map the Thermostat Modes for Velbus devices

This worked

alexa="ThermostatController.thermostatMode" [OFF="NIGHT",ECO="DAY",HEAT="COMFORT"]

My only gripe is that Velbus thermostats have 4 Thermostat Modes, which are SAFE, NIGHT, DAY & COMFORT
and a ThermostatOperatingMode which flips the Thermostat between HEATING and COOLING

(So effectively, there are 8 Thermostat Modes, split across heating and cooling.

Can anyone suggest a way to get Items like these working in Alexa, or am I just wasting my time?

    Group BackBedroomGP2_Thermostat					"Back Bedroom Thermostat"													{ga="Thermostat" [roomHint="Back Bedroom"], alexa="Endpoint.Thermostat" }
    Number BackBedroomGP2_CurrentTemperature 		"Back Bedroom Current Temperature" 			(BackBedroomGP2_Thermostat,WholeHouse_CurrentTemperature		)		{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:input#CH9", 								ga="thermostatTemperatureAmbient" ,		 alexa="TemperatureSensor.temperature" }
    Number BackBedroomGP2_CurrentTargetTemperature 	"Back Bedroom Current Target Temperature"	(BackBedroomGP2_Thermostat,WholeHouse_CurrentTargetTemperature	)		{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#CURRENTTEMPERATURESETPOINT", 	ga="thermostatTemperatureSetpoint",		 alexa="ThermostatController.targetSetpoint"}
	String BackBedroomGP2_ThermostatMode 			"Back Bedroom Thermostat mode"	  	 		(BackBedroomGP2_Thermostat)		{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#MODE", 							ga="thermostatMode" [modes="off=SAFE,heat=COMFORT,eco=NIGHT,on=DAY"] ,					alexa="ThermostatController.thermostatMode" [OFF="NIGHT",ECO="DAY",HEAT="COMFORT"]}
	String BackBedroomGP2_ThermostatOperatingMode 	"Back Bedroom Thermostat operating mode"	(BackBedroomGP2_Thermostat)		{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#OPERATINGMODE",																											alexa="ThermostatController.thermostatMode" [COOL="COOLING",HEAT="HEATING"]

I believe that this is also possible

    Number BackBedroomGP2_HeatingComfortTarget 		"Back Bedroom Heating Comfort Target Temperature"	{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#HEATINGMODECOMFORTTEMPERATURESETPOINT"	,		alexa="ThermostatController.lowerSetpoint#HEAT"		}
	Number BackBedroomGP2_HeatingDayTarget 			"Back Bedroom Heating Day Target Temperature"	  	{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#HEATINGMODEDAYTEMPERATURESETPOINT"		,		alexa="ThermostatController.lowerSetpoint#ECO"		}
	Number BackBedroomGP2_HeatingNightTarget 		"Back Bedroom Heating Night Target Temperature"	 	{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#HEATINGMODENIGHTTEMPERATURESETPOINT"																	}
	Number BackBedroomGP2_HeatingAntifrostTarget	"Back Bedroom Heating Antifrost Target Temperature"	{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#HEATINGMODEANTIFROSTTEMPERATURESETPOINT"	,		alexa="ThermostatController.lowerSetpoint#OFF"		}
	Number BackBedroomGP2_CoolingComfortTarget 		"Back Bedroom Cooling Comfort Target Temperature"	{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#COOLINGMODECOMFORTTEMPERATURESETPOINT",			alexa="ThermostatController.upperSetpoint#HEAT"		}
	Number BackBedroomGP2_CoolingDayTarget			"Back Bedroom Cooling Day Target Temperature"		{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#COOLINGMODEDAYTEMPERATURESETPOINT"	,			alexa="ThermostatController.upperSetpoint#ECO"		}
	Number BackBedroomGP2_CoolingNightTarget 		"Back Bedroom Cooling Night Target Temperature"		{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#COOLINGMODENIGHTTEMPERATURESETPOINT"																	}
	Number BackBedroomGP2_CoolingSafeTarget			"Back Bedroom Cooling Safe Target Temperature"		{channel="velbus:vmbgp2:VelbusNetworkBridge:1C:thermostat#COOLINGMODESAFETEMPERATURESETPOINT"	,			alexa="ThermostatController.upperSetpoint#OFF"		}

Based on my understanding it seems that what you call “thermostat mode” is more like preset target temperature settings and the “operating mode” is the actual thermostat mode. Out of curiosity, is there a way to turn off your thermostat?

The setpoint tagging example you mentioned wouldn’t work as it is limited to #eco only at this point and to thermostats supporting dual setpoint modes. Anyway, wouldn’t BackBedroomGP2_CurrentTargetTemperature point to the relevant item when the thermostat is set to a specific operating mode/preset setting?

My recommendation would be to keep the operating mode as ThermostatController.thermostatMode to control the heat/cool, and model the preset setting as ModeController interface. The downside is that you wouldn’t be able to control the preset value in the Alexa app. The solution for this one would be to set that item outside of the group endpoint.

Group BackBedroomGP2_Thermostat "Back Bedroom Thermostat" {alexa="Endpoint.Thermostat"}
Number BackBedroomGP2_CurrentTemperature "Back Bedroom Current Temperature" (BackBedroomGP2_Thermostat) {alexa="TemperatureSensor.temperature"}
Number BackBedroomGP2_CurrentTargetTemperature "Back Bedroom Current Target Temperature" (BackBedroomGP2_Thermostat) {alexa="ThermostatController.targetSetpoint"}
String BackBedroomGP2_ThermostatMode "Back Bedroom Thermostat Mode"	(BackBedroomGP2_Thermostat) {alexa="ModeController.mode" [friendlyNames="@Setting.Preset", supportedModes="SAFE=Safe,NIGHT=Night,DAY=Day,COMFORT=Comfort"]}
String BackBedroomGP2_ThermostatOperatingMode "Back Bedroom Thermostat operating mode" (BackBedroomGP2_Thermostat) {alexa="ThermostatController.thermostatMode" [COOL="COOLING",HEAT="HEATING"]}

Alexa, set the back bedroom to heat
Alexa, set the back bedroom preset to night
Alexa, what’s the back bedroom set to?
Alexa, what’s the back bedroom preset set to?

1 Like


Thanks for your detailed reply.

The Velbus Thermostat Operating Mode channel has 2 possible states, COOLING and HEATING, where each then has 4 possible Thermostat Mode states, SAFE, NIGHT, DAY and COMFORT.

Each Thermostat Mode has a Preset Target Temperature. (Changeable via openHAB)

If I’m understanding your reply correctly, you’re suggesting that it’s possible to get Alexa to swap the thermostat between it’s Cooling and Heating Modes and then call a Preset Target Temperature by name.

I’ll give this a try and report back…


Adding in the Operating Mode just didn’t work, and without all I am getting is “Customised” for the mode

I’ll keep trying

That part I understood but if, for example, your thermostat is set to HEATING and NIGHT modes, wouldn’t the relevant item BackBedroomGP2_HeatingNightTarget reflect the same value when changing BackBedroomGP2_CurrentTargetTemperature value. That was my point. It seems unnecessary to expose the individual target setpoints via Alexa if this is how it would be working.

You understood correctly. That gives the best and more natural way to control your thermostat mode matrix via Alexa.

Okay… Yes

I have caught up with your train of thought now.

I’ve removed the setpoint Items from Alexa, so now just got to get it to re-discover .

(I’ve been trying to map the thermostat modes to Google Assistant, but with even less success)

As far as I know, there is no equivalent for ModeController in the Google Assistant ecosystem as of yet. I may be wrong though as I am not fully up to date on the latest updates on their end.

I think there is going to be in the near future, as it’s mentioned in the documentation and on GitHub

Something along these lines…

ga="thermostatMode" [ Modes="off=SAFE,heat=COMFORT,eco=NIGHT,on=DAY" ]

the ThermostatMode feature works, but the mapping just seems to get ignored

My point was regarding having two separate controls one for the thermostat mode and another for presets to mirror my recommended solution. No matter what, I highly doubt that an integration with two separate items modeled as thermostat mode under the same endpoint would be supported as this is not a standard setup.

I think you are right and that I’m just walking down a dark path to nowhere

There is no such thing using OH :smile: You can always use a proxy item and rules to setup an alternative solution but I do agree that it may not be as straight forward than the Alexa integration. Although, I might be a bit biased.

1 Like

OKAY :smile:

So this does work :slight_smile:

It’s not the most intuitive phrasing, but it’s working.

A massive thank you for your support and advice / persistence / tolerance

1 Like

Hi Guys,

after lots of readings and tests, i really dont know how to fix this and i hope someone will help me.

Using Openwebnet bindings i created a CEN+ scenario things a follow:

Thing 	bus_cenplus_scenario_control    iCenplus_Cancello   			"CEN+ Cancello"  				@	"CenPlus"		[ where="29", buttons="1" ]		

Than i created the relevant item

String   iCenplus_Cancello  "Cancello"     <switch>    {channel="openwebnet:bus_cenplus_scenario_control:mybridge:iCenplus_Cancello:button_1"} 

and this scenario is working perfectly using the PRESS_EXT command.

Now i would like Alexa to trigger this Scenario, therefore i added this Items:

String CEN_command "Cancello" {alexa="ModeController.mode" [supportedModes="OPEN=xxx,CLOSE=xxxx", actionMappings="Close=xxx,Open=xxxxx,autoupdate="false"]}

i used the xxx because i tried almost everithing but alexa always replay " i don’t know how to adjust this device to that setting"

Any tips??

Thanks in advance for the patience

Ha ha so you are dulicating your posts here… not good…

I posted the solution here:

I have seen some say that the a more natural phrasing works for them; maybe it depends on the language.

However, you can create a more natural phrase by creating a routine for your desired phrase on the Alexa app


That’s a good idea…


I’m almost at my solution using dummy switch and rule and yes, i asked also here as you suggested in your last post… or this is what i understood.

Thanks for your solution but First i want to find my way, to learn, than i will have a look at your solution which will be the best! :wink:

1 Like