Just using few cubes.
- Zigbee
- Warema
- enOcean
Idea WAS good (as for state of many years ago). BUT not anymore, it stays on the same level as it was when project was a startup, where „staying“ means in the concurrent environment loosing positions.
After few years already, i see no any changes/improves in the project at all. UI and way how homeegrams are made not changed and literally, just TERRIBLE (cant find anyhow better word for it), its neither intuitive nor helpful.
We are in 2025, almost 2026 (many years since product was launched) and feels like its not moving anyhow at all. Sad to see how others quickly would take over…
Guys, you are using APIs behind the scene (if you can not move the product forward), why not just open the APIs to all (use open API), ideally add terraform connector so that can be easier provisioned all the homeegrams as a code at least… Stop development of that terrible webUI - its waste of human resources from your side. I think no one in good mind programs smart houses with UI, NOT doing it with monkey clicking through the UI.
Opening API and add things like terraform can open finally possibility to others to share homegrams with each other (e.g customer can add a motion sensor: it can quickly download templates for generic actions and build scenarios from the pieces, not from the scratch). There can be a good potential for products developmens and accelerating it.
Simple case:
For example: impossible to sort our Actions for homegraams at all? E.g simple case: i need when sensor is not detecting movement to dim the lights, and during this dimming change the color, then after dinning is finished, turn the light off IF not detected any motions (still). Fun part, turned on that Actions somehow chained automatically in really random sequence and no chance to change sequence (tried different browsers, app: i do not see possiblity to drag/drop actions). ChatGPT claims that there is possibility, buuuut… none of its propositions helped…
Moreover, i assume you might have also SDK, how about to open parts of SDK for community to let others either contribute OR at least solve own issues. Yes, you must Keep kernel proprietary to avoid serious failures, but connectors and SDK potentially can be opened for even better integrations. But start with terraform might be decent and no brainer (as soon as u have APIs, terraform would work, you only need to release it OR provide open API and then community can develop connectors/SDK).
If person takes any programming language to program listed actions, it would take 2-5 minutes. If used normal programming languages, can be also added test cases. You can get potential for quick growth by the community. And with your UI, it takes ages. And even after those ages, I literally can not use hardware i have on 100% unless i make LOTs of homegrams… Sry, but it just a facepalm, not with this bad UI with completely missing UX.
PS, I am more than 15 years in software development and leading big development team. I might be open to contribute into the project or help with it if needed. Feel free to drop a note into private (i check from time to time).