More than 500 different modules(adapters) that can be interconnected with each other. E.g. Homematic or KNX can control HUE or sonos and vice versa.
ioBroker's answer:
ioBroker's answer:
Compatibility: ioBroker supports a vast range of devices and protocols, making it one of the most versatile smart home automation systems available. It is compatible with many popular brands and can integrate with virtually any smart device, offering a level of flexibility that might not be available with other platforms.
Open Source: As an open-source platform, ioBroker is free to use and continuously updated and improved by a community of developers. This allows for greater customization, transparency, and control over your home automation setup.
Scalability: ioBroker is designed to handle complex smart home setups. No matter how many devices you have or plan to add in the future, the platform is designed to scale and manage a large and diverse range of devices efficiently.
JavaScript and Blockly support: For those comfortable with programming, ioBroker offers the option to write scripts in JavaScript. For users who prefer a graphical interface, Blockly is available. This versatility can be appealing for both beginners and experienced users.
Data Logging: ioBroker has extensive data logging capabilities, allowing users to store, analyze, and visualize data from their smart devices over long periods of time. This can be incredibly valuable for monitoring energy usage, tracking trends, and optimizing your smart home setup.
Community and Support: ioBroker has a strong and active community of users and developers who can provide assistance, share ideas, and help troubleshoot any issues you may encounter.
ioBroker's answer:
Mostly users are german speaking, but all documentation is primary in english.
ioBroker's answer:
ioBroker is an open-source Internet of Things (IoT) platform that was developed with the aim to provide a unified and flexible solution for smart home automation. It's primarily driven by a community of enthusiasts and developers contributing to its ongoing development and expansion.
The project was initiated to overcome the limitations of existing smart home platforms, particularly the inability of many platforms to integrate with a wide variety of devices and brands. ioBroker was designed with a focus on compatibility, scalability, and flexibility, aiming to provide a solution that can integrate a vast array of smart devices, regardless of manufacturer or protocol, and handle complex home automation setups.
While the platform was initially more popular among the tech-savvy due to its need for more technical involvement, over time, efforts have been made to make it more user-friendly and accessible to a wider audience.
As an open-source project, the ongoing development of ioBroker is dependent on the contributions of its community, including software developers and end-users, who continually work on refining the software, expanding its compatibility with different devices, and improving its features.
ioBroker's answer:
JavaScript, Redis, Mqtt, MUI-UI.
Based on our record, Huginn seems to be more popular. It has been mentiond 65 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Https://n8n.io/, https://github.com/huginn/huginn, https://automatisch.io/, https://www.activepieces.com/ and theres a lot more... I've used n8n, node-red, and huginn (a while back), but imo n8n has been the simplest off the shelf. - Source: Hacker News / 4 months ago
The device itself is really cute. I'm not sure about handing oauth tokens to all my accounts to a third party for them to run huginn/selenium on a backend that might not be online for more than a year. I'm barely comfortable with Alexa having a connection to my iTunes for podcasts. What happens when Uber or whoever decides to throw a captcha between Rabbit and the web frontend? I'd like to see it do more than help... - Source: Hacker News / 5 months ago
I skipped to chapter 9 in the article ("Clogged"), and it looked like Pipes failed because it didn't have a large enough team or a well-defined mission. As a result they couldn't offer a super robust product that would lure in enterprise users. "You could not purchase some number of guaranteed-to-work Pipes calls per month" is the quote from the article. The reason I think that interesting is because that's the... - Source: Hacker News / 6 months ago
"correct" is a value judgement that depends on lots of different things. Only you can decide which tool is correct. Here are some ideas: - https://camel.apache.org/ - https://www.windmill.dev/ Your idea about a queue (in redis, or postgres, or sqlite, etc) is also totally valid. These off-the-shelf tools I listed probably wouldn't give you a huge advantage IMO. - Source: Hacker News / 8 months ago
Huginn (https://github.com/huginn/huginn) has like some 39K stars on Github and the use cases it covered looks good. Source: 10 months ago
n8n.io - Free and open fair-code licensed node based Workflow Automation Tool. Easily automate tasks across different services.
Home-Assistant.io - Home Assistant is an open-source home automation platform running on Python 3.
ifttt - IFTTT puts the internet to work for you. Create simple connections between the products you use every day.
openHAB - "empowering the smart home" - vendor and technology agnostic open source home automation
Zapier - Connect the apps you use everyday to automate your work and be more productive. 1000+ apps and easy integrations - get started in minutes.
Google Home - Set up, manage, and control your Chromecast, Chromecast Audio and Google Home devices.