Hacking and continuation conversation
Is there a new place or a centrally located place for discussion around trying to continue use after "shutdown"? Searching this place may be unreliable soon and data seems to be scattered. Anyone want to start one ?
Just as a reminder: if you still want to use your neeo after the servers are shut down, then join the community on telegram.
me/joinchat/NocMDU9RCVP9hSCJxPsCEg (you have to add https in front like in the posts above)
We have a tool called "meta". Please read on to get a rough idea of what "meta" is.
The neeo brain / remote is offering a software development kit (SDK) from day one to write custom drivers. Creating those custom drivers to communicate directly with the neeo sdk has some drawbacks that I do not want to go into further here.
So using drivers via meta introduces some extra features to neeo like:
- running multiple custom drivers while only using one sdk adapter in the brain
- ability to create and maintain custom drivers after neeo server shutdown (cloud storage with drivers offline)
- custom drivers can talk to devices through several types of ip commands
- ... or the build in ir blaster of the brain can be used to send any custom command in global cache format (recording ir commands from physical ir remote is not reliable with build in ir sensors but broadlink is a solution to this). So creating custom new ir drives is possible too.
The community has created and shared some very nice drivers which are taking the original neeo to a whole new level.
- philips hue (fully functional like the original philips hue integration that cones with neeo)
- Yamaha AVR/ MusicCast Multiroom audio
- Denon/ Marantz AVR
- LG TV
- Broadlink IR (external ip to ir device to record and replay any ir command)
- blerc (Control Devices via simulated Bluetooth Keyboard (e.g. Nvidia Shield). Additional Hardware (ESP32) needed!)
- some shelly devices
- Sony Bravia TV
... and probably a few more that i forgot. And some other highly individual drivers that are just usable in the individual setup.
As mentioned above meta adds a lot to the original neeo and i probably just scratched the surface with the above description.
There are instructions on how to use and install meta on a raspberry pi. If you have more questions, meet me on Telegram.
Here we are 2 years later for me... is there no possible way to move this extension of communication to a more web friendly platform instead of a mobile app? Using a phone for typing any messages of length is annoying and I'd like to join in and follow what's going on, but if it's like a single chat group and no threaded conversations, you can count me out. Maybe someone could just create a web page with all the updates and information on the development of what's happened?