Livisi / Innogy / RWE Smarthome

RWE was once selling a hub and devices for smarthomes, which is still in use by some people - probably mostly in germany. The unfortunately handed over the control of their smarhome to different providers over the years (thus the many names in Brand), and in the end fully disabled all servers. BUT they enabled the home centrals to be working completely offline!! They even have a local API which would be ideal to be controlled with homey (this is actually the reason i bought homey). I think providing a technical bridge from homey (and all its online functions incl. alexa) to the devices behind the innogy-hub would be a huge selling point for the Homey to all the users which have possibly thousands of € in smarthome devices which they can hardly control anymore. There is a javascript api-client-library ready to be used in an npm package: https://www.npmjs.com/package/innogy-smarthome-lib/v/0.10.1 I tested this to be working on my local smarthome central yesterday (from my pc). I am a dev, but not for javascript, and i believe this could be implemented in a matter of hours for an experienced Homey-Dev Maintainance should be low, as there are guaranteed no changes to the Device-API anymore :) So as long as the api package doesn't update (or you are not updating it) it should just work forever. Ill try working on this in the next weeks. But let me know if you want jump in. I can even open an temporary ngrok tunnel for testing the api if desired. Its hard to find reliable api documentation, so analyzing the code of the npm package is the best documentation i can offer. There are a few alternatives from HomeAssistant or IOBroker Integrations, but as there is this npm-package already, who would need this :)

Christian Seidltiz posted 7 months ago

Discussion