-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Generic Usage Sensor #178
Comments
Hi @ThetaGamma, Thanks for the neat suggestion! Wouldn't be InventoryLevelSensor even be more fitting for your use case? |
Much better, you‘re right! It even has the option of defining individual units for the count object |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I still think this would be a nice Feature (comment to remove stale label) |
In the attempt to integrate support for Inventory Level Sensors, I discovered that the reported levels cannot be queried through Alexa or the Alexa app, making them essentially impractical. Apparently, Alexa implemented Inventory Sensors to facilitate automated reordering of supplies (Amazon Dash) rather than to display actionable information. |
Hi @csuermann
I'd like ask Alexa to tell me the remaining range of my electric car (eg: "Alexa, what is the range of my Fiat?" -> "Your Fiat has 156km left"
Describe the solution you'd like
As far I understand, this might be implemented by using the Alexa.InventoryUsageSensor Interface 3. As Input I'd use an existing value e.g. from IOBroker.
This object could also be used as a generic output of any given value. (I like the example of remaining coffee pads)
Describe alternatives you've considered
currently I use a flow with input from IOBroker for the range, create a new msg Object (msg.payload = "Der Fiat hat noch eine Reichweite von " + msg.payload + " Kilometern";" and pass it to an Object from "node-red-contrib-alexa-remote2-applestrudel" to say the result. Downsite of this solution, that the answer always comes from one device, no matter which echo device you asked. (--> low WAF ;) )
The text was updated successfully, but these errors were encountered: