wow... that was unexpected ... nice.
My Neeo is going to be here on Monday 
I've already created a virtual device using the new Neeo driver in readiness but I'm just wondering what will the driver enable me to do?
Can I trigger a Neeo activity (or recipe I think they call it) from HE, and have HE rules triggered based on an recipe happening in the Neeo?
Yes
After you have your activities configured on your Neeo, enter the neeo ip address in the driver, select create child activity devices in the preferences, after this the driver will create a switch for each of your activities.
You can then use these in rules.
2 Likes
Awesome Mike - can't wait to get a minute to try these out.
Does it work the other way? Ie allow me (or more accurately the Mrs) to use the remote to trigger a Rule Machine?
Activities (recipes) on the remote can be turned into switches in the driver and used like any other switch.
Starting or stopping recipe xyz on the neeo will turn switch xyz on or off, also turning switch xyz on or off turns recipe xyz on or off.
1 Like
I'm really looking forward to getting mine now. As my TV Remote is always close at hand, it makes perfect sense to use it to trigger some HE commands too.
Well now I sort of have to order one.. or at least that's what I'm going to tell the wife.
Had a really quick play Mike, between mince pies - so far so good but will post a few more informed findings when I have more time to use it.
I saw I could start a recipe from the device screen (works) but not stop one ? Not that I think I'd use that very often. Will explore the recipe virtual switches shortly.
Yeah, setup the child device option, then use the on/off for each of the activities.
I've done a very basic set up on mine and now linked it to HE. Works perfectly Turned a recipe on from HE, and TV and STB powered up, turned it off and they both turned off. So lots of potential there.
Apart from that though I am a bit disappointed so far though with the actual remote. It feels a quality item and they've spend a lot of time making the packaging feel upmarket but there is much less customisation available for the buttons and screens than I expected. As I think Mike mentioned there is no ability to customise the hard buttons at all, and although you can create a custom button page on the screen, the icons are smallish and fixed and they have compulsory text below them which makes for a messy and hard to read interface, especially as the background is a coloured image with no option to change it to anything else. They don't seem to use the real estate on the screen very well at all. I'm at the reading glasses stage of life but don't normally have to put them on to use a TV remote, but with the Neeo I do. This could all be fixed within the firmware, but compared to Hubitat where you mention a feature request and its often implemented within a few weeks (once in a few hours!) there have been quite reasonable requests on Neeo going back a year that still haven't been done, which is a worry. For such an expensive bit of kit it still feels very Beta to me. I will keep playing but I'm not sure I'm going to keep it.
Much more customisation is the big feature that we expect in every new firmware release. It has been promised but only a few drips have been implemented. It has been a long time since the last update so I am hoping the next ‘imminent’ one addresses this. If you can await that within your return window it may be worth it. I have no inside knowledge of what’s in the next update though.
Hard buttons are sparse but with some integrations you can intercept those presses and do with them as you wish automation wise.
Anyone else finding it’s a bit ‘intermittent’ in its working?
I’m largely just controlling a LG oled, Bt 4K, Sonos playbar and nvidia shield at this point but often need to go back the original remotes as it doesn’t pair the sonos or the controls are glitchy with the shield where it will go up and down a bit or randomly play a video when using in Kodi
Controlling the shield via hdmi sucks, us the ir device.
I've boxed mine up and am awaiting the returns label to send It back for a refund. It just isn't good enough to justify the cost IMO. I now have a Harmony Elite and its way more functional and reliable for half the price. The Neeo looks and feels good but its a sheep in wolfs clothing.
Not sure if everyone has seen the latest news from Neeo.
@mike.maxwell what I’m not clear on is what happens when they turn off the infrastructure in 24months... will the neeo stop working or will whatever has been set up on it continue to run - and what happens if you ever need to make a change on it?!
On another note, how do I get rule machine to perform actions when an activity is turned off?
I can get it to run when an activity turns on (not sure if this is a bug btw but after an activity turns on it seems to immediately turn the component switch off and I have to manually refresh to see that the activity is still running)
But because of the above it is not possible to know which activity just got turned off
The app and remote are all local, so everything should still work, but who really knows.
My activity switches turn on and off when I switch activities, and they stay on while the activity is running, not sure why yours aren't doing this.
Do you have an activity off within each recipe?
nope.. For the time being I've gotten around this by making a rule that refreshes the component switch after 15 seconds and pauses the rule that has actions associated with it turning off for the immediate period after it is turned on. However, as I try and add more automations around this it is getting more and more complex and I think I've run into a few race conditions.
I'll do some tests tonight by making a new activity in Neeo that only does one thing and will see if it behaves the same way - and will report back
each activity needs an explicit off to work correctly
