Power state handling in Recipes
I do not quite understand how NEEO is doing the power state handling.
I have added a custom recipe and added just all Power Off commands of all my devices I own.
I expect that when I press on this recipe, NEEO sends the Power Off commands to all devices, independently if they have been used before or not. (I do not have stupid devices without discrete Power Off commands). If a device is on, it will swtich off, if the device is already off, the Power Off command is sent anyway but of course nothing happens.
NEEO on the other hand only sends the Power Off commands to the devices it thinks they are on. (started in a receipt before). If a device has been powered on not from NEEO (eg. original remote, CEC, Smarphone App), it will not be powered off.
I have modified an automatuic recipe (Watch Netflix with the devices TV, AVR) and deleted the steps "Power On TV" and "Power On AVR" because they are not needed. The TV turns on automatically with the "Send Netflix action to TV" and my AVR turns on automatically with the "Change Input of AVR to Input xy".
The advantage is that I dont have to wait xx seconds after powering on the devices to change the input when it can be done with just one action.
I expect that when i turn off the recipe that all my devices will be powered off
NEEO on the other hand does not send a Power Off command to my AVR (because I have deleted the Power On and it thinks that the AVR is not running?)
Why does't NEEO sends the dicrete Power Commands any logic?
Hi Beni , although I cannot help with your current issues, I wanted to ask, where did you get the Netflix recipe from? I'm wondering because I would like to have one myself, though it might not really work since we might have different TV's, nevertheless, maybe I can twist it a bit... :)
Thanks in advance and regards
Beni you can look forward to the next release with will include not only a clever assumption mode as an alternative to the current stupid device handling but also a true Smartener that listens to CEC and allows devices that are actually power-status-stupid to become smart with true feedback.
The other case you mentioned of fully handling the power off when a device is powered on by something else than NEEO is not happening short term though for IR devices. This would cause a hole lot of other issues. For IP devices like Sonos though we track the real status. You can even turn it on on the speaker itself and it will pop up as an active device on NEEO. Hope this helps. Looking forward hearing your feedack once you messed with the coming release. GraciasReply
Raphael Thanks for the answer, but i do not understand why a Power Off command can not be sent every time for "non stupid" devices. I cant see any issue here, when a devicice is already off it just doesnt do anything.
What I actually want is to have a "Power off everything" recipe which powers off all my devices, independant of wheter they have been switched on by NEEO or by any other source.
When I leave my house such a recipe would be very useful.Reply
Anyone else figured out a workaround to pwer off all the devices in a house with a custom recipe as NEEO does not to be able to do this (as per Raphaels comment).
I often stream Spotify to my AVR via Spotify Connect (which of course powers on the AVR device) but then the only way to turn the AVR off again is using the original Onkyo Remote.
I thought that the aim of a universal remote should be that we do not have to use multiple different remotes again.....Reply