New Ideas To Excel Domoticz on SmartHome Market...
Posted: Monday 29 January 2018 13:55
Hi All,
There are many open source Smart Home Controller Software on the market, be it Domoticz, openhab, Jeedom, Home Assistant etc. The more user a software has, the more it is open to develop further. I really don't know the number of active Domoticz users out there, or any of the other software at all. All these software has their own pros and cons; I believe we, as users, should participate more on Domoticz, and not leave it all to the developers, so that Domoticz might get more users and become single handedly the leader...
Comparatively, i used openhab before domoticz, it was very nice, however the move from openhab 1 to 2 made everything more complex instead of making it more user friendly. And the bugs were increasing everyday, when my ZWave network was unusable with openhab, that's when i decided to go for domoticz and i am happier now. With the possibility of Python Plugins (The best language ever imo), i feel there are no boundaries to develop further.
Again, to make Domoticz better that its competitors, and have what they don't have, i have my humble ideas:
1. Native support for Homekit, Alexa, Google Home etc.: Looking at this, i feel like everyone has their own choice or patch solutions. Needless to say HomeKit is the most important one imo, because it seems like it is the only one which supports multinational languages. Instead of using homebridge, nodejs, docker or any other alternatives, Homekit should be natively supported either on Domoticz or a Python plugin. Since Python Plugins for me are so succesful, i keep this solution as native also.
2. ZWave Support: As tough i believe OZW is stable enough, this side of Domoticz might be better; like adding unsupported zWave solutions to Domoticz (like Seismic Intensity and Seismic Magnitude Sensors, OZW supports it but not Domoticz) and also a more stable OZW Control Panel. Using OZW is still good enough i think but this two weak sides could be better.
3. More Python Plugins: I am really surprised to see that once we had a Python Plugin Framework, we should have much more Plugins that are already here. Python is really limitless and we still have too few Plugins. I believe solving everything with lua or dzvents scripting is one way of handling it but having a plugin is so easy to deal with for the end users (once the plugin framework is stable of course). I still can't believe why we don't have Plex or Google Traffic Plugins? Right now i am using the scripts, but Plugin is something else...
4. Native Imperihome support: @epierre have this fantastic job of MyDomoAtHome gateway for us, to be used for Imperihome. The only thing i miss from my openhab experience is the IOS application. It was so good and customizable, i was easily doing everything with it. When i first started using Domoticz i was disappointed with IOS applications comparatively, then i started using Imperihome; which helped me do a better job for overall control. With Pilot and Domoticz IOS it took me a while to get used to, but now it is all better. However i still goo for Imperihome unconciously since the UI and overall structure is easier to use. So, there are 2 alternatives, have a customizable app like openhab; or have native Imperihome support either on Imperihome or Domoticz side.
5. Domoticz Users Count: Is there a way to have a counter on Domoticz which can tell the number of active Domoticz users out there?
Please note that these are all my humble personal opinions; you are most welcome to support or not any of these and share your own opinions. In the meantime, personally i am trying to get most from the Plugin Framework and prepare plugins for community use; and have a plan to work on Homekit as a plugin, since i am using Synology and only able to run homebridge with a docker. If anyone of you Plugin writers are interested, we might work together...
There are many open source Smart Home Controller Software on the market, be it Domoticz, openhab, Jeedom, Home Assistant etc. The more user a software has, the more it is open to develop further. I really don't know the number of active Domoticz users out there, or any of the other software at all. All these software has their own pros and cons; I believe we, as users, should participate more on Domoticz, and not leave it all to the developers, so that Domoticz might get more users and become single handedly the leader...
Comparatively, i used openhab before domoticz, it was very nice, however the move from openhab 1 to 2 made everything more complex instead of making it more user friendly. And the bugs were increasing everyday, when my ZWave network was unusable with openhab, that's when i decided to go for domoticz and i am happier now. With the possibility of Python Plugins (The best language ever imo), i feel there are no boundaries to develop further.
Again, to make Domoticz better that its competitors, and have what they don't have, i have my humble ideas:
1. Native support for Homekit, Alexa, Google Home etc.: Looking at this, i feel like everyone has their own choice or patch solutions. Needless to say HomeKit is the most important one imo, because it seems like it is the only one which supports multinational languages. Instead of using homebridge, nodejs, docker or any other alternatives, Homekit should be natively supported either on Domoticz or a Python plugin. Since Python Plugins for me are so succesful, i keep this solution as native also.
2. ZWave Support: As tough i believe OZW is stable enough, this side of Domoticz might be better; like adding unsupported zWave solutions to Domoticz (like Seismic Intensity and Seismic Magnitude Sensors, OZW supports it but not Domoticz) and also a more stable OZW Control Panel. Using OZW is still good enough i think but this two weak sides could be better.
3. More Python Plugins: I am really surprised to see that once we had a Python Plugin Framework, we should have much more Plugins that are already here. Python is really limitless and we still have too few Plugins. I believe solving everything with lua or dzvents scripting is one way of handling it but having a plugin is so easy to deal with for the end users (once the plugin framework is stable of course). I still can't believe why we don't have Plex or Google Traffic Plugins? Right now i am using the scripts, but Plugin is something else...
4. Native Imperihome support: @epierre have this fantastic job of MyDomoAtHome gateway for us, to be used for Imperihome. The only thing i miss from my openhab experience is the IOS application. It was so good and customizable, i was easily doing everything with it. When i first started using Domoticz i was disappointed with IOS applications comparatively, then i started using Imperihome; which helped me do a better job for overall control. With Pilot and Domoticz IOS it took me a while to get used to, but now it is all better. However i still goo for Imperihome unconciously since the UI and overall structure is easier to use. So, there are 2 alternatives, have a customizable app like openhab; or have native Imperihome support either on Imperihome or Domoticz side.
5. Domoticz Users Count: Is there a way to have a counter on Domoticz which can tell the number of active Domoticz users out there?
Please note that these are all my humble personal opinions; you are most welcome to support or not any of these and share your own opinions. In the meantime, personally i am trying to get most from the Plugin Framework and prepare plugins for community use; and have a plan to work on Homekit as a plugin, since i am using Synology and only able to run homebridge with a docker. If anyone of you Plugin writers are interested, we might work together...
