Very cool! I removed “Day” and my Mode Item was discovered by Alexa again! It would be great if you could get it added back in. Thank you!
That’s the plan.
1 Like
@5iver I just pushed a change to the live skill that only restrict the not allowed friendly names to capability resources only. Any mode or preset resource names will not be subject to that restriction. Your use-case should be discoverable again.
1 Like
Confirmed! Removed it from Alexa, added Day mode into the .items file, rediscovered and it was now found. Thank you!
1 Like
Sorry to jump into this discussion with an off topic question, but I started a new thread and haven’t received any help. I see that you have Insteon fanlincs working in your environment and wondered if you might be able to help. I have 2 fanlincs and when I enter them as items in OH2 with the #fan feature, I get errors stating that my item references an unknown feature. Is there anything special that needs to be done to get the fan control working? Here is my item entry and the log errors. Any help would really be appreciated. Thank you.
Number GuestfanLincFan “Guest fanlinc fan” {insteonplm=“XX.XX.XX:F00.00.1C#fan”}
[ERROR] [g.insteonplm.InsteonPLMActiveBinding] - item MasterfanLincFan references unknown feature: fan, item disabled! Known features for F00.00.1C are: dimmer, fastonoff, lastheardfrom, ledbrightness, manualchange, onlevel, ramprate.
Is it possible to ask Alexa “What is current power consumption?” and have her reply by reading value in openhab provided by electricity meter via modbus? Below is the item.
Number PowerTotal “PowerTotal [%.1f]” (gCharts) {channel=“modbus:data:endpoint:inputRegisters1:powtot:number” }
You can setup non controllable devices, for the sole purpose of getting its status, with any of the Building Block APIs controllers.
Number PowerTotal "Total [%.1f]" (gCharts) {alexa="RangeController.rangeValue" [friendlyNames="Power Consumption", nonControllable=true], channel="modbus:data:endpoint:inputRegisters1:powtot:number"}
thanks, it works. How to specify unit - watt?
This unit is not supported as of yet on the Alexa side. So you won’t be able to define a unit on this one.
3 Likes
@digitaldan I have read about using window contacts and motion detection sensors in alexa routines (https://stadt-bremerhaven.de/so-erinnert-euch-alexa-an-geoeffnete-fenster/)
I’m missing this with my items in the Alexa App. Is it a miss-configuration on my side or a missing feature in the Alexa Smart Home Skill? (I’m on openhab 2.5.1).
Unfortunately, as mentioned in the contact and motion sensor documentation, these cannot be used to trigger Alexa routines for the time being. Currently, the only support for these is requesting their state via voice commands.
Hi All,
Is this tagging incorrect? The item is discovered but it finds it as a switch, not a light which is odd.
Dimmer EnsuiteCeilingDim1 "Ensuite [%d %%]" (Group_HabPanel_Dashboard,gAllDimmers) { mqtt="<[broker:/house/out/EnsuiteCeilingDim1/state:state:default], >[broker:/house/in/EnsuiteCeilingDim1/command:command:*:default]", alexa="PowerController.powerState,BrightnessController.brightness" }
You can either use the Lighting metadata label or define the endpoint as a light by adding the meta parameter category="LIGHT".
Thank you!
Hi All
I decided to update the Alexa skill code. The one I was using previously was very old. I had no issues following the instructions here https://github.com/openhab/openhab-alexa and created the ASK-CLI details and deployed the skill. Its visible in the Alexa companion app and I was able to link it via the CLI. I couldnt see any errors, everything looks OK
I forgot all my devices using the Alexa website and ran a discovery.
No new devices found using the alexa skill, only devices from other enabled skills
Any suggestions? CloudWatch shows no errors
I should note its using Login via Amazon to my private openhab cloud server. None of this has changed and worked without issue on the old skill.
Have you gone over the troubleshooting guide? This is the typical syndrome of a bad item configuration causing the discovery process to silently fail on the Alexa side. Staggering is the key in resolving this one.
If we want to increase log verbosity, add environmental variable LOG_LEVEL = info to your Lambda function configuration.
Hi Jeremy I did yes, but given the items were being discovered by previously working skills I didnt think there could be an issue with syntax, is that not correct?
