Domoticz full integration
-
In latest release of Domoticz I can see first implementations of MySensors!
Maybe it's worth a shot for someone to register on Domoticz forum and help their team out? -
Posted a new beta of domoticz.
Lots have been changedIf anyone can supply me with serial log messages of:
S_LIGHT_LEVEL
S_WATT
S_KWHThat would be helpfull
With regards,
Rob -
@AWI said:
@hek I am almost done with the python -Domoticz "full integration" but strugling with a few message types. The code for Vera is a good source for information but it is hard to determine the role of the controller in the construction/routing of the network. For now I assumed only node numbering and keeping track of the sensors. Is the controller supposed to do something with the relay nodes? what is the function of the I_CHILDREN message?
@hek said:
Just skip it. It's deprecated and will be removed.
@hek:
The I_CHILDREN+"C" message is useful during development/implementation/repositioning of nodes with repeater functionality (changing node location may alter routing).From my experience, this function is helpful and should even be expanded to clearing the parent_node_id: i.e. I faced the situation where the parent node (not gw) was out of range and the node could not communicate back to the gateway. The only resolution is to clear the eeprom or sending the I_CHILDREN + "C" command
-
@andriej I have managed to get a MySensor DHT11 sensor reporting consistently in Domoticz, via the Ethernet option. My next steps are to try a couple of other sensor types (eg distance, switches) and multiple sensors on one arduino node. After a first look at how the Serial and Ethernet options have been done in Domoticz, it looks to me like MQTT might also provide a third 'transport' option for integrating MySensors, with some development. I will be building my knowledge across MySensors and Domoticz over the coming week or two, so might be able to contribute to integration development in the future.
-
I've motion sensors, barometer, lux sensors 4 dallas sensors on 4 arduinos fully working on domoticz.
It's al working fine, sensors don't always appear in the right tab, but that's no problem for now, new to mysensors, very happy with it! -
Status of native Domoticz MySensors support:: For the ones who are interested @GizMoCuz did a great job in building native MySensors support in Domoticz. As documentation is lagging behind ;) I have examined the code and come up with a basic understanding of functionality.
First of all: you need the beta version of Domoticz (can be enabled in setup->settings) for now to get MySensors support. By enabling the MySensors hardware (setup->hardware) you can enable MySensors USB/ LAN interface.The supported "V" types as of today for "SET" (read from the code):
V_TEMP:, V_HUM, V_PRESSURE, V_VARx, V_TRIPPED, V_ARMED, V_LOCK_STATUS, V_LIGHT, V_DIMMER, V_DUST_LEVEL, V_WATT, V_KWH, V_DISTANCE, V_FLOW, V_VOLUME:, V_WIND, V_GUST, V_DIRECTION, V_LIGHT_LEVEL,:V_FORECAST,: V_VOLTAGE, V_UV, (so almost all )The list for 'REQ' is (and will be.?) limited to V_LIGHT, V_DIMMER and V_VAR types. If anyone needs more please address this on the Domticz forum as I am out of arguments.
Be aware that the MySensor support is beta, but very promissing.
-
Is the Watt-sensor working ok for every of you?
I've switched my installation to MySensors, but reports of current usage seems strange to me...I don't see how many watts my house is using that often as it's possible (so every 60 secs you could say how much pulses were counted...).
I can't catch how often the value is refreshed.Second thing is - is it possible to enter 'current status' of the electrical counter?
I can write down the value and I'd like to see new counts added to already measured value (to see after i.e. a month if the counts are counted same as by meter).Maybe it can be done by V_VAR? If yes, how to use it/push it to node?
-
Status of native Domoticz MySensors support:: For the ones who are interested @GizMoCuz did a great job in building native MySensors support in Domoticz. As documentation is lagging behind ;) I have examined the code and come up with a basic understanding of functionality.
First of all: you need the beta version of Domoticz (can be enabled in setup->settings) for now to get MySensors support. By enabling the MySensors hardware (setup->hardware) you can enable MySensors USB/ LAN interface.The supported "V" types as of today for "SET" (read from the code):
V_TEMP:, V_HUM, V_PRESSURE, V_VARx, V_TRIPPED, V_ARMED, V_LOCK_STATUS, V_LIGHT, V_DIMMER, V_DUST_LEVEL, V_WATT, V_KWH, V_DISTANCE, V_FLOW, V_VOLUME:, V_WIND, V_GUST, V_DIRECTION, V_LIGHT_LEVEL,:V_FORECAST,: V_VOLTAGE, V_UV, (so almost all )The list for 'REQ' is (and will be.?) limited to V_LIGHT, V_DIMMER and V_VAR types. If anyone needs more please address this on the Domticz forum as I am out of arguments.
Be aware that the MySensor support is beta, but very promissing.
@AWI I installed the latest BETA version and Enabled MySensor via the Serial/USB gateway. I have a simple network with one PIR Motion Sensor which sends a V_TRIPPED and a battery status message every time the motion detector goes off. I can see in the log that Domoticz communicates with the serial GW and that it gets a message every time the sensor goes of.
HOWEVER the system identified the motion sensor as "Lighting 2" and doesn't convey the status of the PIR, but rather thinks it's a light bulb. The last seen date never changes after the initial startup of the sensor , however the battery percentage seems to read correctly,Where is the MySensor implementation coded ? Is it modifiable on the end system via scripts or is it compiled in?
G
-
@AWI I installed the latest BETA version and Enabled MySensor via the Serial/USB gateway. I have a simple network with one PIR Motion Sensor which sends a V_TRIPPED and a battery status message every time the motion detector goes off. I can see in the log that Domoticz communicates with the serial GW and that it gets a message every time the sensor goes of.
HOWEVER the system identified the motion sensor as "Lighting 2" and doesn't convey the status of the PIR, but rather thinks it's a light bulb. The last seen date never changes after the initial startup of the sensor , however the battery percentage seems to read correctly,Where is the MySensor implementation coded ? Is it modifiable on the end system via scripts or is it compiled in?
G
@GaryStofer You should change the "Switch type" in the GUI (edit sensor -> switchtype -> motion sensor) to change between the different switch types. The naming of the sensors like "lighting 2" is a Domoticz thing coming from history. It is better to ignore this.
I don't know yhy the "last seen" never changes if you see the changes in the log file. Better to address these things on the Domoticz forum.
The implementation is compiled in the Domoticz code (although I am using my own script for now) -
@GaryStofer You should change the "Switch type" in the GUI (edit sensor -> switchtype -> motion sensor) to change between the different switch types. The naming of the sensors like "lighting 2" is a Domoticz thing coming from history. It is better to ignore this.
I don't know yhy the "last seen" never changes if you see the changes in the log file. Better to address these things on the Domoticz forum.
The implementation is compiled in the Domoticz code (although I am using my own script for now)Yes, changing the "switch type" to Motion helped a great deal. I would never have thought of a motion detector to be considered a switch. I guess it works in a backwards kind of way. I get the source on my RPi next and have fun with that and trying to figure out why the simplest of Blockly events all fail to execute with error message. Have not found much deliberate documentation on their site, such is opens source I guess ..... Seems to be snappy though.
How is your own script tying into the system?
G
-
Yes, changing the "switch type" to Motion helped a great deal. I would never have thought of a motion detector to be considered a switch. I guess it works in a backwards kind of way. I get the source on my RPi next and have fun with that and trying to figure out why the simplest of Blockly events all fail to execute with error message. Have not found much deliberate documentation on their site, such is opens source I guess ..... Seems to be snappy though.
How is your own script tying into the system?
G
@GaryStofer I suggest you put a screen dump on the Domoticz forum for the Blockly issue. Lot's of helping hands over there. My "own script" is a Python interface to Domoticz, It works well but has a separate "database" (.csv file ;)) to store all the sensor to domoticz bindings. It makes everything very flexible and complete but installation etc. is a bit of a pain... I still use it because of missing functionality to "read" values from Domoticz. If you want I can update the version on GitHub.
-
Status of native Domoticz MySensors support:: For the ones who are interested @GizMoCuz did a great job in building native MySensors support in Domoticz. As documentation is lagging behind ;) I have examined the code and come up with a basic understanding of functionality.
First of all: you need the beta version of Domoticz (can be enabled in setup->settings) for now to get MySensors support. By enabling the MySensors hardware (setup->hardware) you can enable MySensors USB/ LAN interface.The supported "V" types as of today for "SET" (read from the code):
V_TEMP:, V_HUM, V_PRESSURE, V_VARx, V_TRIPPED, V_ARMED, V_LOCK_STATUS, V_LIGHT, V_DIMMER, V_DUST_LEVEL, V_WATT, V_KWH, V_DISTANCE, V_FLOW, V_VOLUME:, V_WIND, V_GUST, V_DIRECTION, V_LIGHT_LEVEL,:V_FORECAST,: V_VOLTAGE, V_UV, (so almost all )The list for 'REQ' is (and will be.?) limited to V_LIGHT, V_DIMMER and V_VAR types. If anyone needs more please address this on the Domticz forum as I am out of arguments.
Be aware that the MySensor support is beta, but very promissing.
@AWI said:
The supported "V" types as of today for "SET" (read from the code):
V_TEMP:, V_HUM, V_PRESSURE, V_VARx, V_TRIPPED, V_ARMED, V_LOCK_STATUS, V_LIGHT, V_DIMMER, V_DUST_LEVEL, V_WATT, V_KWH, V_DISTANCE, V_FLOW, V_VOLUME:, V_WIND, V_GUST, V_DIRECTION, V_LIGHT_LEVEL,:V_FORECAST,: V_VOLTAGE, V_UV, (so almost all )The list for 'REQ' is (and will be.?) limited to V_LIGHT, V_DIMMER and V_VAR types. If anyone needs more please address this on the Domticz forum as I am out of arguments.
Be aware that the MySensor support is beta, but very promissing.
are the V_VARx types realy supported? because I can run domoticz with V_DISTANCE , V_TEMP:, V_HUM, V_PRESSURE etc but V_VARx types only showed on the log but not recognized on the devices list...
-
@AWI said:
The supported "V" types as of today for "SET" (read from the code):
V_TEMP:, V_HUM, V_PRESSURE, V_VARx, V_TRIPPED, V_ARMED, V_LOCK_STATUS, V_LIGHT, V_DIMMER, V_DUST_LEVEL, V_WATT, V_KWH, V_DISTANCE, V_FLOW, V_VOLUME:, V_WIND, V_GUST, V_DIRECTION, V_LIGHT_LEVEL,:V_FORECAST,: V_VOLTAGE, V_UV, (so almost all )The list for 'REQ' is (and will be.?) limited to V_LIGHT, V_DIMMER and V_VAR types. If anyone needs more please address this on the Domticz forum as I am out of arguments.
Be aware that the MySensor support is beta, but very promissing.
are the V_VARx types realy supported? because I can run domoticz with V_DISTANCE , V_TEMP:, V_HUM, V_PRESSURE etc but V_VARx types only showed on the log but not recognized on the devices list...
@Mickey It is supposed to be supported. Have a look at the Domoticz code. I also remember seeing a discussion on the Domoticz forum.
