Closed snail59 closed 4 years ago
You're right. I also think this should be raw_value
in the MQTT entity, per the Snips docs. I'm also failing to remember why I had value
set to an object with kind
and value
.
I can fix this in the next version of 2.4 (it's already fixed in 2.5).
I won't be of a great help as I did not read the snips docs, but I think you did right when creating this object because:
By the way, thank you for your work ;-)
Will be fixed in 2.4.20
I just tested, it does work.
Thank you
Hello,
Then the mqtt message will contain (if one asked for the living light to be turned off)
==> rawValue contains "downstairs" ( as of value ) while it should be "living"
On line 269, file ./rhasspy/mqtt.py reads
"rawValue": ev["value"],
while it should be ( I think )"rawValue": ev["raw_value"],
. At least it works for me.2.The same goes for the input content. It will read
Turn off the downstairs light
while I think this should readTurn off the bedroom light
as this was the real input. This might depend on people's point of view, of course.