Request for contribution - controller selection matrix
-
Kindly update MyController.org changes. Updated in this doc
-
OpenHAB was a little outdated. Updated the column in the editable google sheet. Thanks
-
OpenHAB was a little outdated. Updated the column in the editable google sheet. Thanks
-
Thanks @guillermo-schimmel. I have updated the controller table.
@mfalkvidd Hi there. It is still the same table on:
https://www.mysensors.org/controller
How can I help in order to update it?
Thanks!
-
@mfalkvidd Hi there. It is still the same table on:
https://www.mysensors.org/controller
How can I help in order to update it?
Thanks!
@guillermo-schimmel The update is a 100% manual process. I looked in the changelog of the Google spreadsheet and updated everything I could find. If something wasn't updated, it's because I was unable to see that it needed to be updated.
Maybe you could mark the cells that need updating with a different background color (in the Google spreadsheet), to make it easier to find them?
Preferably, we could find a way to ditch the manual table update and embed the google spreadsheet directly.
-
In case someone wants to add FHEM to the controller list, here's the state to date:
Controller, (Sorted by alphabet, if filled) FHEM
Complete list of S & V types supported (V2)
S_DOOR Y
S_MOTION Y
S_SMOKE Y
S_LIGHT Y
S_BINARY Y
S_DIMMER Y
S_COVER Y
S_TEMP Y
S_HUM Y
S_BARO Y
S_WIND Y
S_RAIN Y
S_UV Y
S_WEIGHT Y
S_POWER Y
S_HEATER Y
S_DISTANCE Y
S_LIGHT_LEVEL Y
S_ARDUINO_NODE Y
S_ARDUINO_REPEATER_NODE Y
S_LOCK Y
S_IR Y
S_WATER Y
S_AIR_QUALITY Y
S_CUSTOM Y
S_DUST Y
S_SCENE_CONTROLLER Y
S_RGB_LIGHT Y
S_RGBW_LIGHT Y
S_COLOR_SENSOR Y
S_HVAC Y
S_MULTIMETER Y
S_SPRINKLER Y
S_WATER_LEAK Y
S_SOUND Y*
S_VIBRATION Y
S_MOISTURE Y
S_INFO Y
S_GAS Y
S_GPS Y*
S_WATER_QUALITY Y*
Controller, (Sorted by alphabet, if filled) FHEM
V_TEMP Y
V_HUM Y
V_STATUS Y
V_LIGHT Y
V_PERCENTAGE Y
V_DIMMER Y
V_PRESSURE Y
V_FORECAST Y
V_RAIN Y
V_RAINRATE Y
V_WIND Y
V_GUST Y
V_DIRECTION Y
V_UV Y
V_WEIGHT Y
V_DISTANCE Y
V_IMPEDANCE Y
V_ARMED Y
V_TRIPPED Y
V_WATT Y
V_KWH Y
V_SCENE_ON Y
V_SCENE_OFF Y
V_HVAC_FLOW_STATE Y
V_HVAC_SPEED Y
V_LIGHT_LEVEL Y
V_VAR1 Y
V_VAR2 Y
V_VAR3 Y
V_VAR4 Y
V_VAR5 Y
V_UP Y
V_DOWN Y
V_STOP Y
V_IR_SEND Y
V_IR_RECEIVE Y
V_FLOW Y
V_VOLUME Y
V_LOCK_STATUS Y
V_LEVEL Y
V_VOLTAGE Y
V_CURRENT Y
V_RGB Y
V_RGBW Y
Advanced (new) types
V_ID Y
V_UNIT_PREFIX Y*
V_HVAC_SETPOINT_COOL Y*
V_HVAC_SETPOINT_HEAT Y*
V_HVAC_FLOW_MODE Y*
V_TEXT Y
V_CUSTOM Y
V_POSITION Y
V_IR_RECORD Y
V_PH Y*
V_ORP Y*
V_EC Y*
V_VAR Y*
V_VA Y*
V_POWER_FACTOR Y*
* Untested(sorry for part of the table format has disapperared)
Kind regards.Controller: FHEM; MySensors: 2.3.1, RS485,nRF24,RFM69, serial Gateways
-
In case someone wants to add FHEM to the controller list, here's the state to date:
Controller, (Sorted by alphabet, if filled) FHEM
Complete list of S & V types supported (V2)
S_DOOR Y
S_MOTION Y
S_SMOKE Y
S_LIGHT Y
S_BINARY Y
S_DIMMER Y
S_COVER Y
S_TEMP Y
S_HUM Y
S_BARO Y
S_WIND Y
S_RAIN Y
S_UV Y
S_WEIGHT Y
S_POWER Y
S_HEATER Y
S_DISTANCE Y
S_LIGHT_LEVEL Y
S_ARDUINO_NODE Y
S_ARDUINO_REPEATER_NODE Y
S_LOCK Y
S_IR Y
S_WATER Y
S_AIR_QUALITY Y
S_CUSTOM Y
S_DUST Y
S_SCENE_CONTROLLER Y
S_RGB_LIGHT Y
S_RGBW_LIGHT Y
S_COLOR_SENSOR Y
S_HVAC Y
S_MULTIMETER Y
S_SPRINKLER Y
S_WATER_LEAK Y
S_SOUND Y*
S_VIBRATION Y
S_MOISTURE Y
S_INFO Y
S_GAS Y
S_GPS Y*
S_WATER_QUALITY Y*
Controller, (Sorted by alphabet, if filled) FHEM
V_TEMP Y
V_HUM Y
V_STATUS Y
V_LIGHT Y
V_PERCENTAGE Y
V_DIMMER Y
V_PRESSURE Y
V_FORECAST Y
V_RAIN Y
V_RAINRATE Y
V_WIND Y
V_GUST Y
V_DIRECTION Y
V_UV Y
V_WEIGHT Y
V_DISTANCE Y
V_IMPEDANCE Y
V_ARMED Y
V_TRIPPED Y
V_WATT Y
V_KWH Y
V_SCENE_ON Y
V_SCENE_OFF Y
V_HVAC_FLOW_STATE Y
V_HVAC_SPEED Y
V_LIGHT_LEVEL Y
V_VAR1 Y
V_VAR2 Y
V_VAR3 Y
V_VAR4 Y
V_VAR5 Y
V_UP Y
V_DOWN Y
V_STOP Y
V_IR_SEND Y
V_IR_RECEIVE Y
V_FLOW Y
V_VOLUME Y
V_LOCK_STATUS Y
V_LEVEL Y
V_VOLTAGE Y
V_CURRENT Y
V_RGB Y
V_RGBW Y
Advanced (new) types
V_ID Y
V_UNIT_PREFIX Y*
V_HVAC_SETPOINT_COOL Y*
V_HVAC_SETPOINT_HEAT Y*
V_HVAC_FLOW_MODE Y*
V_TEXT Y
V_CUSTOM Y
V_POSITION Y
V_IR_RECORD Y
V_PH Y*
V_ORP Y*
V_EC Y*
V_VAR Y*
V_VA Y*
V_POWER_FACTOR Y*
* Untested(sorry for part of the table format has disapperared)
Kind regards.@rejoe2 said in Request for contribution - controller selection matrix:
As recently a lot of MySensors features have been added to the official FHEM module (smartSleep, heartbeat, RSSI-requests, OTA), here's the most recent list for addition to the controller matrix overview. Please do not hesitate to contact me for other formats (upload of xls is not allowed here)Last update date / update frequency FHEM base: continuously/MySensors-Modules: when needed MySensors Types Basic S & V types All Advanced S & V types All MYSensors Functionality Heartbeat support Y node ID generation Y Ack support Y OTA support Y Request Y Smart sleep Y Gateways Serial Gateway support Y LAN Gateway support Y MQTT gateway support Y Multiple gateway support Y* Scripting IFTT alike programming Blockly n Other Hardware platform(s) Propietary n Windows Y Unix Y Raspberry Y Other Y Software Licence/ Open Source GPL Programming language Perl Interfaces Web interface Y Android app Y** Apple app Y** Windows app *limited support for active components like switches or displays directly attached on a GW **3:rd party Controller, (Sorted by alphabet, if filled) FHEM Complete list of S & V types supported (V2) S_DOOR Y S_MOTION Y S_SMOKE Y S_LIGHT Y S_BINARY Y S_DIMMER Y S_COVER Y S_TEMP Y S_HUM Y S_BARO Y S_WIND Y S_RAIN Y S_UV Y S_WEIGHT Y S_POWER Y S_HEATER Y S_DISTANCE Y S_LIGHT_LEVEL Y S_ARDUINO_NODE Y S_ARDUINO_REPEATER_NODE Y S_LOCK Y S_IR Y S_WATER Y S_AIR_QUALITY Y S_CUSTOM Y S_DUST Y S_SCENE_CONTROLLER Y S_RGB_LIGHT Y S_RGBW_LIGHT Y S_COLOR_SENSOR Y S_HVAC Y S_MULTIMETER Y S_SPRINKLER Y S_WATER_LEAK Y S_SOUND Y* S_VIBRATION Y S_MOISTURE Y S_INFO Y S_GAS Y S_GPS Y* S_WATER_QUALITY Y* Controller, (Sorted by alphabet, if filled) FHEM V_TEMP Y V_HUM Y V_STATUS Y V_LIGHT Y V_PERCENTAGE Y V_DIMMER Y V_PRESSURE Y V_FORECAST Y V_RAIN Y V_RAINRATE Y V_WIND Y V_GUST Y V_DIRECTION Y V_UV Y V_WEIGHT Y V_DISTANCE Y V_IMPEDANCE Y V_ARMED Y V_TRIPPED Y V_WATT Y V_KWH Y V_SCENE_ON Y V_SCENE_OFF Y V_HVAC_FLOW_STATE Y V_HVAC_SPEED Y V_LIGHT_LEVEL Y V_VAR1 Y V_VAR2 Y V_VAR3 Y V_VAR4 Y V_VAR5 Y V_UP Y V_DOWN Y V_STOP Y V_IR_SEND Y V_IR_RECEIVE Y V_FLOW Y V_VOLUME Y V_LOCK_STATUS Y V_LEVEL Y V_VOLTAGE Y V_CURRENT Y V_RGB Y V_RGBW Y Advanced (new) types V_ID Y V_UNIT_PREFIX Y* V_HVAC_SETPOINT_COOL Y* V_HVAC_SETPOINT_HEAT Y* V_HVAC_FLOW_MODE Y* V_TEXT Y V_CUSTOM Y V_POSITION Y V_IR_RECORD Y V_PH Y* V_ORP Y* V_EC Y* V_VAR Y* V_VA Y* V_POWER_FACTOR Y* * Untested -
During the last year I've invested my spare time in re-designing and re-architecting my old Home Automation project called myHouse which was also acting as a MySensors controller (https://www.mysensors.org/controller/myhouse). Now, I've given the project a brand new name (eGeoffrey - https://www.egeoffrey.com) and despite the basic principles are the same (likewise MySensors support), now is supposed to be way simpler to configure, use, customize and extend. Before doing any change, @AWI is it the correct approach if I delete the existing myHouse entry from the controller section, add a new one for eGeoffrey (since it is replacing it) and do the same with the column of the matrix? (do I need any special permission for editing the spreadsheet?) Thanks!
-
During the last year I've invested my spare time in re-designing and re-architecting my old Home Automation project called myHouse which was also acting as a MySensors controller (https://www.mysensors.org/controller/myhouse). Now, I've given the project a brand new name (eGeoffrey - https://www.egeoffrey.com) and despite the basic principles are the same (likewise MySensors support), now is supposed to be way simpler to configure, use, customize and extend. Before doing any change, @AWI is it the correct approach if I delete the existing myHouse entry from the controller section, add a new one for eGeoffrey (since it is replacing it) and do the same with the column of the matrix? (do I need any special permission for editing the spreadsheet?) Thanks!
-
During the last year I've invested my spare time in re-designing and re-architecting my old Home Automation project called myHouse which was also acting as a MySensors controller (https://www.mysensors.org/controller/myhouse). Now, I've given the project a brand new name (eGeoffrey - https://www.egeoffrey.com) and despite the basic principles are the same (likewise MySensors support), now is supposed to be way simpler to configure, use, customize and extend. Before doing any change, @AWI is it the correct approach if I delete the existing myHouse entry from the controller section, add a new one for eGeoffrey (since it is replacing it) and do the same with the column of the matrix? (do I need any special permission for editing the spreadsheet?) Thanks!
-
@mfalkvidd, I think he doesn't have permissions to update the mysensors.org page.
UPDATE: Hmm, I now see it's owned by user2684... so I guess he CAN update it using the login on openhardware.io.@user2684, just PM or email me new screenshots and textual changes on hek@mysensors.org and I'll update the page. -
Thanks all, yes I do have privileges to edit pages. Will work on it and when ready publish directly the changes. Should I face any issue in the process I'll get back here. Thanks again!
-
Done it! (https://www.mysensors.org/controller/egeoffrey). I've already removed the legacy myHouse project and updated the spreadsheet. If there is anything wrong in the changes, just let me know. Do I also need to create a subcategory under https://forum.mysensors.org/category/3/controllers? Thanks!
-
@hek thanks! It took us way more than expected to re-architect all the thing but now that is ready, happy with the result so your positive feedback is appreciated :-) Legacy myHouse issue was mainly around extensibility hence this distributed, plugin-based architecture allowing users to package functionalities and/or contents without me doing any change in the core code. And turning it in a cloud-based service (as an option) could be also really easy. But for now the hope is to build a little community around it so to make it evolve further. Just as a starting point :-)
