Comments (7)
Thank you for your interest !
I know Home Assistant cenvention, but it's not a really true standard. My interest is to come back some interoperability in home automation ...
I don't know how many HC3 to mqtt exists and how many with homie but it's not my point here. To be honest I don't use Homie at all, but I'm interest by a standard something in common and well thinking .... the Home automation stuff is not very good and whereas to have a boolean for HA compliant, then another to another home automation software, it's better to respect a standard, this one (and it's pretty well done) at the end the goal is HA use this standard too because all don't turn around HA ;)
I'm from the NextDom community and we start from scratch to devvelop a new solution for home automation but we are more like an orchestrator between MQTT, Node-Red , an API and finaly an UI but we can be compliant with Domoticz, or HA or OpenHAB, becasue at the end we respect a standard the Homie one ... I hope you understand my point :)
from hc3-to-mqtt.
Hi @slobberbone!
I like the spec and the idea behind it.
Can you please advise on the few questions before we jump into discussing implementation details and timelines?
- have you considered Home Assistant MQTT convention as an alternative? This may be not an industry standard, but many people use it de-facto. Home Assistant is able to push your devices further to HomeKit, and then you can control your smart home with voice using Apple Watch, AirPods/iPhone, etc... which is nice bonus to have with almost zero additional efforts :)
- do we have any kind of understanding how many smart home installations may benefit from Fibaro HC3 <-> Homie MQTT convention for Q1-Q2 2021? Just some rough figures so I can prioritise the work for March or later months, depending how many people need it :)
from hc3-to-mqtt.
Let me see what I can do about it over weekend
from hc3-to-mqtt.
And so by doing a bit of analysis, it feels like the implementation should be ready in few weeks time.
The efforts come from:
- refactor the codebase and separate "MQTT conventions" related logic from other other functions (e.g. HC3, core specific). This will improve the codebase maintainability by implementing some of the SOLID principles, and thus establish a healthy foundation for expanding the QuickApp with more features in a future by avoiding Spaghetti code
- add new QuickApp variables, to let users set which conventions they like to use, e.g. "Only Home Assistant", "Only Homie", "Home Assistant + Homie"
- implement Homie convention itself
Worth mentioning: I work on the HC3-MQTT integration during evenings, weekends as I have other job to do full-time :)
from hc3-to-mqtt.
I've recently committed a new QuickApp version that leverages a modular structure for (a) Device API (b) MQTT Convention API:
- this will simplify QuickApp extension with new features, and help to maintain a better functional quality in a long term
- improved bootstrap and events processing performance by nearly 30%
No Homio support yet... but all the preparations are done, which is roughly about 1/2 of the overall work. @slobberbone can you please clarify if you still need it? If not - then I'm planning to implement support for most basic Homio properties/attributes/commands only :)
from hc3-to-mqtt.
Hy @alexander-vitishchenko Thanks for your work and interest ;) We are still interest to have more and more project respecting this specification made by Homie. We are working a lot on our NextDom solution and in few time we will dev the adapter to Homie standard (and HA because these are the 2 standards for now).
from hc3-to-mqtt.
@slobberbone I've just submitted the initial implementation for "Homie" MQTT convention, including support for property read and set operations
- It needs to be enabled with QuickApp variable "mqttConvention" = "homie"
- I had no possibilities to test so far... do I need to install NextDom? :) Not sure if this is an easy thing to do, and perhaps you can do a bit of the initial testing by yourself and see if I'm moving to the right direction
- I could be wrong here, but it looks like Homie convention doesn't specify how "rooms" to be handled exactly... the spec seems to be "all purpose" IoT convention. So we need to make design decision by ourselves, for exposing rooms to the MQTT topic hierarchy
from hc3-to-mqtt.
Related Issues (20)
- Change MQTT Topic HOT 9
- Couldn't recognize device - com.fibaro.multilevelSwitch - com.fibaro.dimmer HOT 21
- Battery sensor created multiple times HOT 26
- feat request : nice blinder support HOT 15
- Unexpected response status HOT 49
- Problem in dispatchFibaroEventToMqtt(event) if a scene has the same identifier as a device HOT 6
- cover:close HOT 7
- Duplicate battery entities for each device HOT 4
- Error while fetching Fibaro HC3 events "End of file" HOT 7
- Problem with a keyFOB remote control in automations in HA HOT 6
- Unable to discoverDeviceHierarchy HOT 5
- Propose new device support (Zigbee RGB bulb) HOT 12
- elero blinds and shutters support HOT 18
- After update from 1.0.221 to 1.0.225 cover/curtain does not work anymore. HOT 14
- Control HA devices back from HC3 HOT 3
- Cover state does not update HOT 15
- Can't find a way to filter more than one device HOT 2
- Duplicates in home assistant for same device HOT 21
- Discovered entities with a name that starts with the device name HOT 12
- Door sensor not correctly detected. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hc3-to-mqtt.