Page 1 of 2
Openzwave Eneco ED2.0 Meter Adapter
Posted: Monday 23 November 2015 19:10
by patricx
Hello,
I have a Eneco ED2.0 Meter Adapter and jused openzwave.
If i link openzwave and the Eneco ED2.0 Meter Adapter then they get a connecion but in domoticz id do not see the gas and electrical.
Who can help me to config this adapter in domoticz.
thanks,
Patrick
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Monday 23 November 2015 22:08
by marcelr
Dunno,
I'm not an expert on z-wave, but the device supports the following
(from the z-wave alliance conformance statement):
Prodrive - ED2.0 Meter Adapter
General Information
Product Identifier: ED2.0 Meter Adapter
Brand Name: Prodrive B.V.
Product Version: 1
Z-Wave Certification #: ZC08-12050005
Z-Wave Product Information
Supports Z-Wave Beaming Technology? Yes
Supports Z-Wave Network Security? Yes
Supports Z-Wave AES-128 Security? No
Z-Wave Technical Information
Z-Wave Frequency: Europe
Z-Wave Device Class: METER / ADV_ENERGY_CONTROL
Supported Command Classes (11):
Meter Table Configuration
Meter Table Push Configuration
Basic
Firmware Update Meta Data
Application Status
Meter Table Monitoring
Multi Channel
Version
Manufacturer Specific
Time Parameters
Configuration
Not sure if these are all implemented in openzwave.
grtz,
marcelr
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Monday 23 November 2015 22:45
by patricx
I know al infomation i can find here
http://www.pepper1.net/zwavedb/device/310 but i do not know i to write a working xml file for the sensor.
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Tuesday 24 November 2015 0:31
by dijkdj
I have the same adapter but no toon. Do you know how to reset the meter adapter? Can not include it the way it is now
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Tuesday 24 November 2015 7:12
by patricx
You can reset it to default to push the button for 10 sec when you do the adapter in the wallsocket.
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Tuesday 24 November 2015 9:28
by patricx
I write a xml file :
Code: Select all
<?xml version="1.0" encoding="utf-8"?>
<Product xmlns='http://code.google.com/p/open-zwave/'>
<!-- ED2.0 Meter Adapter -->
<!-- Configuration -->
<CommandClass id="112">
<Value type="list" genre="config" instance="0" index="1" label="Gas Metering" size="1">
<Help>Enable and disable gas metering</Help>
<Item label="Enabled" value="1" />
<Item label="Disabled" value="0" />
</Value>
<Value type="short" genre="config" instance="1" index="2" label="Gas Meter resolution" min="0" max="9999" value="400" size="2">
<Help>The resolution of the analog gas meter (revolutions per m³) in unsigned Q14.2 notation.</Help>
</Value>
<Value type="list" genre="config" instance="2" index="3" label="Electricity metering" size="1">
<Help>Set Gas Metering mode</Help>
<Item label="Enabled" value="1" />
<Item label="Disabled" value="0" />
</Value>
<Value type="short" genre="config" instance="3" index="4" label="Electricity meter resolution" min="0" max="9999" value="400" size="2">
<Help>The resolution of the analog electricity meter (revolutions per kWh) in unsigned Q14.2 notation.</Help>
</Value>
</CommandClass>
<!-- Association Groups -->
<!-- Remove COMMAND_CLASS_BASIC -->
<CommandClass id="32" action="remove" />
<!-- Map endpoints to instances -->
<CommandClass id="96" mapping="endpoints" />
</Product>
I can config the adapter now but i do not see the adapter in the list of domoticz please can some one help me what do i forget in the config file of the adapter?
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Tuesday 24 November 2015 9:30
by gizmocuz
Do you have 'accept new hardware' enabled in the settings ?
Is it possible you could post here the 'node' section of your configuration file ?
You can export the configuration file if you goto the openzwave hardware setup, from the dropdown export the configuration file
Then copy/paste the node section of this node
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Tuesday 24 November 2015 13:35
by patricx
@gizmocuz i do accept new hardware.
my config file of zwave :
Code: Select all
<?xml version="1.0" encoding="utf-8" ?>
<Driver xmlns="http://code.google.com/p/open-zwave/" version="3" home_id="0xd4ed07c2" node_id="1" api_capabilities="0" controller_capabilities="40" poll_interval="60000" poll_interval_between="false">
<Node id="1" name="" location="" basic="2" generic="2" specific="1" type="Static PC Controller" listening="true" frequentListening="false" beaming="true" routing="false" max_baud_rate="40000" version="4" query_stage="Complete">
<Manufacturer id="0147" name="Z-Wave.Me">
<Product type="0400" id="0001" name="RaZberry Controller ZWave+" />
</Manufacturer>
<CommandClasses>
<CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" after_mark="true">
<Instance index="1" />
<Value type="byte" genre="basic" instance="1" index="0" label="Basic" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
</CommandClass>
</CommandClasses>
</Node>
<Node id="2" name="" location="" basic="4" generic="32" specific="1" type="Routing Slave" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
<Manufacturer id="010f" name="FIBARO System">
<Product type="0501" id="1002" name="FGBS001 Universal Binary Sensor" />
</Manufacturer>
<CommandClasses>
<CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" setasreport="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="43" name="COMMAND_CLASS_SCENE_ACTIVATION" version="1" request_flags="5" after_mark="true" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="48" name="COMMAND_CLASS_SENSOR_BINARY" version="1" request_flags="5" innif="true">
<Instance index="1" endpoint="1" />
<Instance index="2" endpoint="2" />
<Value type="bool" genre="user" instance="1" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="True" />
<Value type="bool" genre="user" instance="2" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="True" />
<SensorMap index="0" type="81" />
<SensorMap index="0" type="82" />
<SensorMap index="0" type="173" />
<SensorMap index="0" type="174" />
</CommandClass>
<CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="1">
<Instance index="1" endpoint="3" />
<Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="21.06" />
<Value type="decimal" genre="user" instance="1" index="9" label="Barometric Pressure" units="kPa" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.77" />
</CommandClass>
<CommandClass id="96" name="COMMAND_CLASS_MULTI_INSTANCE/CHANNEL" version="2" request_flags="1" innif="true" mapping="endpoints">
<Instance index="1" />
</CommandClass>
<CommandClass id="112" name="COMMAND_CLASS_CONFIGURATION" version="1" request_flags="5" innif="true">
<Instance index="1" />
<Value type="short" genre="config" instance="1" index="1" label="IN1 Alarm Cancellation Delay" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="65535" value="0">
<Help>Input I alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. Default 0.</Help>
</Value>
<Value type="short" genre="config" instance="1" index="2" label="IN2 Alarm Cancellation Delay" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="65535" value="0">
<Help>Input II alarm cancellation delay. Additional delay after an alarm from input IN1 has ceased. The parameter allows you to specify additional time, after which the input no. 1 alarm is cancelled once its violation has ceased. Default 0.</Help>
</Value>
<Value type="list" genre="config" instance="1" index="3" label="Type of input no. 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
<Help>Type of input no. 1, what the input 1 will report if no contact is made. Default 1.</Help>
<Item label="Input NO (Normal Open)" value="0" />
<Item label="Input NC (Normal Close)" value="1" />
<Item label="Input MONOSTABLE" value="2" />
<Item label="Input BISTABLE" value="3" />
</Value>
<Value type="list" genre="config" instance="1" index="4" label="Type of input no. 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
<Help>Type of input no. 2, what the input 2 will report if no contact is made. Default 1.</Help>
<Item label="Input NO (Normal Open)" value="0" />
<Item label="Input NC (Normal Close)" value="1" />
<Item label="Input MONOSTABLE" value="2" />
<Item label="Input BISTABLE" value="3" />
</Value>
<Value type="list" genre="config" instance="1" index="5" label="Type of transmitted control frame for association group 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="6" size="1">
<Help>Type of transmitted control frame for association group 1, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET). Default 255 - BASIC SET.</Help>
<Item label="ALARM GENERIC" value="0" />
<Item label="ALARM SMOKE" value="1" />
<Item label="ALARM CO" value="2" />
<Item label="ALARM CO2" value="3" />
<Item label="ALARM HEAT" value="4" />
<Item label="ALARM WATER" value="5" />
<Item label="BASIC_SET" value="255" />
</Value>
<Value type="list" genre="config" instance="1" index="6" label="Type of transmitted control frame for association group 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="6" size="1">
<Help>Type of transmitted control frame for association group 2, activated via input IN1. The parameter allows to specify the type of alarm frame or to force transmission of control commands (BASIC_SET). Default 255 - BASIC SET.</Help>
<Item label="ALARM GENERIC" value="0" />
<Item label="ALARM SMOKE" value="1" />
<Item label="ALARM CO" value="2" />
<Item label="ALARM CO2" value="3" />
<Item label="ALARM HEAT" value="4" />
<Item label="ALARM WATER" value="5" />
<Item label="BASIC_SET" value="255" />
</Value>
<Value type="byte" genre="config" instance="1" index="7" label="Forced Level of Dimming group 1" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
<Help>Value of the parameter specifying the forced level of dimming / opening sun blinds when comes "switch on" / "open" command to devices from association group no. 1. In the case of alarm frames the alarm priority is specified. Possible parameter settings: (1 – 99) and 255. Value of 255 makes it possible to activate the device when using the Dimmer module it means activating the device and setting it to the previous stored condition, e.g. when Dimmer is set to 30%, then deactivated, and then reactivated using command 255, it will automatically be set to the previous condition, i.e. 30%. Default 255.</Help>
</Value>
<Value type="byte" genre="config" instance="1" index="8" label="Forced Level of Dimming group 2" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
<Help>Value of the parameter specifying the forced level of dimming / opening sun blinds when comes "switch on" / "open" command to devices from association group no. 2. In the case of alarm frames the alarm priority is specified. Possible parameter settings: (1 – 99) and 255. Value of 255 makes it possible to activate the device when using the Dimmer module it means activating the device and setting it to the previous stored condition, e.g. when Dimmer is set to 30%, then deactivated, and then reactivated using command 255, it will automatically be set to the previous condition, i.e. 30%. Default 255.</Help>
</Value>
<Value type="list" genre="config" instance="1" index="9" label="Deactivate transmission of frame cancelling alarm" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Help>Deactivating transmission of the frame cancelling the alarm or the control frame deactivating the device (Basic). It allows for disabling the deactivation function or the alarm cancellation function for devices associated with the appropriate input of the Fibaro Sensor. NOTE: Information concerning alarm violation or activation commands for devices from association groups are always sent. Default 0. ATTENTION: Information alarm triggered or command enabled for devices with associative groups are always sent. NOTE: Value "Group 1 not sent, Group 2 not sent" is only available in version 2.1 and up</Help>
<Item label="Groups 1 and 2 sent" value="0" />
<Item label="Group 1 sent, Group 2 not sent." value="1" />
<Item label="Group 1 not sent, Group 2 sent." value="2" />
<Item label="Group 1 not sent, Group 2 not sent." value="3" />
</Value>
<Value type="byte" genre="config" instance="1" index="10" label="Interval between successive readings of temperature sensors" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="20">
<Help>Interval between successive readings of temperature from all sensors connected to the device in seconds. Possible parameter settings: (1 – 255). Default 20. ATTENTION: taking temperature readings from the sensor does not result in sending a temperature condition report to the central hub.</Help>
</Value>
<Value type="byte" genre="config" instance="1" index="11" label="Interval between forcing to send report concerning the temperature conditions" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="60">
<Help>Interval between forcing to send report concerning the temperature conditions. The forced report is sent immediately after the next reading of temperature from the sensor, irrespective of the settings of parameter no. 12. Value 0 = Deactivates the function. Default 200. ATTENTION: Frequent sending of temperature condition reports is reasonable when the sensor is located somewhere where can occure rapid changes of ambient temperature. In other cases it is recommended to leave the parameter set to the default value.</Help>
</Value>
<Value type="byte" genre="config" instance="1" index="12" label="Insensitiveness to temperature changes." units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="8">
<Help>Insensitiveness to temperature changes. This is the maximum acceptable difference between the last reported temperature and the current temperature taken from the sensor. If the temperatures differ by the set value or more, then a report with the current temperature value is sent to the device assigned to association group no. 3. Intervals between taking readings from sensors are specified by parameter no. 10. Possible parameter settings:0 – 255 [0oC to 16oC] [0 oF – 28.8oF] In order to set the appropriate value of the parameter, the following formula should be used: x = delta T x 16 - for Celsius x = delta T x 80 / 9 - for Fahrenheit x – parameter value delta T – maximum acceptable temperature gradient in Celsius or Fahrenheit If the value is set to 0, then information about the temperature will be sent every time, immediately once the readings have been taken from the sensor. Default 8.</Help>
</Value>
<Value type="list" genre="config" instance="1" index="13" label="Transmitting the alarm or control frame broadcast mode" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Help>Transmitting the alarm or control frame in "broadcast" mode (i.e. to all devices within range), information sent in this mode is not repeated by the mesh network. Default 0. ATTENTION: If the broadcast mode of information transmission is activated for a given channel, then transmission of information in singlecast mode to devices assigned to the association group of this channel is deactivated.</Help>
<Item label="Sensor 1 and 2 Broadcast inactive" value="0" />
<Item label="Sensor 1 broadcast mode active, Sensor 2 broadcast mode inactive" value="1" />
<Item label="Sensor 1 broadcast mode inactive, Sensor 2 broadcast mode active" value="2" />
<Item label="Sensor 1 and 2 broadcast mode active" value="3" />
</Value>
<Value type="list" genre="config" instance="1" index="14" label="Scene activation" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Help>Enable/Disable scene functionality. The device offers the possibility of sending commands compatible with Command class scene activation. Information is sent to devices assigned to association group no. 3. Default 0.</Help>
<Item label="Scenes disabled" value="0" />
<Item label="Scenes enabled" value="1" />
</Value>
</CommandClass>
<CommandClass id="114" name="COMMAND_CLASS_MANUFACTURER_SPECIFIC" version="1" request_flags="5" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="133" name="COMMAND_CLASS_ASSOCIATION" version="1" request_flags="5" innif="true">
<Instance index="1" />
<Associations num_groups="3">
<Group index="1" max_associations="5" label="Input IN1" auto="true" multiInstance="true">
<Node id="1" />
<Node id="255" />
</Group>
<Group index="2" max_associations="5" label="Input IN2" auto="true">
<Node id="1" />
<Node id="255" />
</Group>
<Group index="3" max_associations="1" label="Temperature Sensor(s)" auto="true">
<Node id="1" />
</Group>
</Associations>
</CommandClass>
<CommandClass id="134" name="COMMAND_CLASS_VERSION" version="1" request_flags="5" innif="true">
<Instance index="1" />
<Value type="string" genre="system" instance="1" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3" />
<Value type="string" genre="system" instance="1" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.52" />
<Value type="string" genre="system" instance="1" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="2.01" />
</CommandClass>
<CommandClass id="142" name="COMMAND_CLASS_MULTI_INSTANCE_ASSOCIATION" version="1" request_flags="5" innif="true">
<Instance index="1" />
<Associations num_groups="0">
<Group index="1" max_associations="5" label="Input IN1" auto="true" multiInstance="true">
<Node id="1" />
<Node id="255" />
</Group>
<Group index="2" max_associations="5" label="Input IN2" auto="true">
<Node id="1" />
<Node id="255" />
</Group>
<Group index="3" max_associations="1" label="Temperature Sensor(s)" auto="true">
<Node id="1" />
</Group>
</Associations>
</CommandClass>
<CommandClass id="156" name="COMMAND_CLASS_SENSOR_ALARM" version="1" request_flags="2">
<Instance index="1" endpoint="1" />
<Instance index="2" endpoint="2" />
</CommandClass>
</CommandClasses>
</Node>
<Node id="3" name="Energie meter" location="" basic="4" generic="49" specific="2" type="Advanced Energy Control" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
<Manufacturer id="0128" name="Eneco">
<Product type="0000" id="0000" name="ED2.0 Meter Adapter" />
</Manufacturer>
<CommandClasses>
<CommandClass id="34" name="COMMAND_CLASS_APPLICATION_STATUS" version="1" request_flags="5" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="86" name="COMMAND_CLASS_CRC_16_ENCAP" version="1" request_flags="5" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="96" name="COMMAND_CLASS_MULTI_INSTANCE/CHANNEL" version="2" request_flags="1" innif="true" mapping="endpoints">
<Instance index="1" />
</CommandClass>
<CommandClass id="112" name="COMMAND_CLASS_CONFIGURATION" version="1" request_flags="5" innif="true">
<Instance index="1" />
<Value type="list" genre="config" instance="0" index="1" label="Gas Metering" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Help>Enable and disable gas metering</Help>
<Item label="Enabled" value="1" />
<Item label="Disabled" value="0" />
</Value>
<Value type="short" genre="config" instance="1" index="2" label="Gas Meter resolution" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="9999" value="400">
<Help>The resolution of the analog gas meter (revolutions per m³) in unsigned Q14.2 notation.</Help>
</Value>
<Value type="list" genre="config" instance="2" index="3" label="Electricity metering" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Help>Set Gas Metering mode</Help>
<Item label="Enabled" value="1" />
<Item label="Disabled" value="0" />
</Value>
<Value type="short" genre="config" instance="3" index="4" label="Electricity meter resolution" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="9999" value="400">
<Help>The resolution of the analog electricity meter (revolutions per kWh) in unsigned Q14.2 notation.</Help>
</Value>
</CommandClass>
<CommandClass id="114" name="COMMAND_CLASS_MANUFACTURER_SPECIFIC" version="1" request_flags="5" innif="true">
<Instance index="1" endpoint="1" />
<Instance index="2" endpoint="2" />
<Instance index="3" endpoint="3" />
<Instance index="4" endpoint="4" />
<Instance index="5" endpoint="5" />
<Instance index="6" endpoint="6" />
</CommandClass>
<CommandClass id="115" name="COMMAND_CLASS_POWERLEVEL" version="1" request_flags="5" innif="true">
<Instance index="1" />
<Value type="list" genre="system" instance="1" index="0" label="Powerlevel" units="dB" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Normal" value="0" />
<Item label="-1dB" value="1" />
<Item label="-2dB" value="2" />
<Item label="-3dB" value="3" />
<Item label="-4dB" value="4" />
<Item label="-5dB" value="5" />
<Item label="-6dB" value="6" />
<Item label="-7dB" value="7" />
<Item label="-8dB" value="8" />
<Item label="-9dB" value="9" />
</Value>
<Value type="byte" genre="system" instance="1" index="1" label="Timeout" units="seconds" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="button" genre="system" instance="1" index="2" label="Set Powerlevel" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="byte" genre="system" instance="1" index="3" label="Test Node" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="list" genre="system" instance="1" index="4" label="Test Powerlevel" units="dB" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Normal" value="0" />
<Item label="-1dB" value="1" />
<Item label="-2dB" value="2" />
<Item label="-3dB" value="3" />
<Item label="-4dB" value="4" />
<Item label="-5dB" value="5" />
<Item label="-6dB" value="6" />
<Item label="-7dB" value="7" />
<Item label="-8dB" value="8" />
<Item label="-9dB" value="9" />
</Value>
<Value type="short" genre="system" instance="1" index="5" label="Frame Count" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="0" />
<Value type="button" genre="system" instance="1" index="6" label="Test" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="button" genre="system" instance="1" index="7" label="Report" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="list" genre="system" instance="1" index="8" label="Test Status" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Failed" value="0" />
<Item label="Success" value="1" />
<Item label="In Progress" value="2" />
</Value>
<Value type="short" genre="system" instance="1" index="9" label="Acked Frames" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="0" />
</CommandClass>
<CommandClass id="134" name="COMMAND_CLASS_VERSION" version="1" request_flags="5" innif="true">
<Instance index="1" endpoint="1" />
<Instance index="2" endpoint="2" />
<Instance index="3" endpoint="3" />
<Instance index="4" endpoint="4" />
<Instance index="5" endpoint="5" />
<Instance index="6" endpoint="6" />
<Value type="string" genre="system" instance="1" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3" />
<Value type="string" genre="system" instance="1" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3.67" />
<Value type="string" genre="system" instance="1" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="1.35" />
<Value type="string" genre="system" instance="2" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="2" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="2" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="3" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="3" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="3" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="4" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="4" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="4" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="5" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="5" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="5" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="6" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="6" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
<Value type="string" genre="system" instance="6" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Unknown" />
</CommandClass>
<CommandClass id="139" name="COMMAND_CLASS_TIME_PARAMETERS" version="1" request_flags="5" innif="true">
<Instance index="1" />
<Value type="string" genre="system" instance="1" index="0" label="Date" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="01/01/0000" />
<Value type="string" genre="system" instance="1" index="1" label="Time" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="17:28:41" />
<Value type="button" genre="system" instance="1" index="2" label="Set Date/Time" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="button" genre="system" instance="1" index="3" label="Refresh Date/Time" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
</CommandClass>
</CommandClasses>
</Node>
</Driver>
i also get this message in the log.
"OpenZWave: Received timeout notification from HomeID: 3572303810, NodeID: 3 (0x03)
I hope you can help me.
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Wednesday 25 November 2015 8:39
by gizmocuz
I see no values in the config, or value classes, only
COMMAND_CLASS_MULTI_INSTANCE/CHANNEL
i think this is not implemented in openzwave.
I suggest to make a request on their forum first, and if it is implemented/handled, then we can implement it
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Saturday 28 November 2015 12:10
by gizmocuz
Where can i get this sensor ? And what is the price ?
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Friday 01 January 2016 16:06
by Zwollenaar
patricx wrote:I write a xml file :
Code: Select all
<?xml version="1.0" encoding="utf-8"?>
<Product xmlns='http://code.google.com/p/open-zwave/'>
<!-- ED2.0 Meter Adapter -->
<!-- Configuration -->
<CommandClass id="112">
<Value type="list" genre="config" instance="0" index="1" label="Gas Metering" size="1">
<Help>Enable and disable gas metering</Help>
<Item label="Enabled" value="1" />
<Item label="Disabled" value="0" />
</Value>
<Value type="short" genre="config" instance="1" index="2" label="Gas Meter resolution" min="0" max="9999" value="400" size="2">
<Help>The resolution of the analog gas meter (revolutions per m³) in unsigned Q14.2 notation.</Help>
</Value>
<Value type="list" genre="config" instance="2" index="3" label="Electricity metering" size="1">
<Help>Set Gas Metering mode</Help>
<Item label="Enabled" value="1" />
<Item label="Disabled" value="0" />
</Value>
<Value type="short" genre="config" instance="3" index="4" label="Electricity meter resolution" min="0" max="9999" value="400" size="2">
<Help>The resolution of the analog electricity meter (revolutions per kWh) in unsigned Q14.2 notation.</Help>
</Value>
</CommandClass>
<!-- Association Groups -->
<!-- Remove COMMAND_CLASS_BASIC -->
<CommandClass id="32" action="remove" />
<!-- Map endpoints to instances -->
<CommandClass id="96" mapping="endpoints" />
</Product>
I can config the adapter now but i do not see the adapter in the list of domoticz please can some one help me what do i forget in the config file of the adapter?
I have an Z-wave adapter and an eneco meter adapter aswell, they are paired, and i see them in sensors. But there is no way to configure it.
(i am trying to get this working as a water meter, with counting pulses it doesn't matter if it is Electricity or water pulses)
- * But where do i put this file?
* And should it have a specific name? (for now i just picked the name eneco.xml)
* In the file itself it refers to: "ED2.0 Meter Adapter", but in domoticz my meter is default known as "Eneco ED2.0 Meter Adapter", does this make any difference?
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Wednesday 06 January 2016 14:04
by dijkdj
Ill keep an eye on this thread. Have not got my meter working yet
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Wednesday 06 January 2016 17:39
by jjnj
Gizmocuz, if you want I can send my meter to you for a week?
Verstuurd vanaf mijn LG-H960 met Tapatalk
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Wednesday 06 January 2016 19:33
by marcelr
Would be interested to have this in Domoticz via openzwave as well.
This adapter is normally connected to a toon (or ED2.0) thermostat.
A few weeks ago I tapped into my toon to read the output of the software that communicates with this adapter, in my toon. Simultaneously, I also made two strace logs of the same software, to trace the I/O of the serial interface of the zw300 module of the thermostat.
It should be possible to reconstruct the z-wave I/O from these files, I did something similar with the I/O of the boiler module of this thermostat. I'm still working on a thermostat controller, so I don't want to mix that with z-wave stuff (yet).
If you want, I can upload them to some spot, so someone else can have a go, but be aware that the strace logs are huge (12 and 26 MB).
grtz,
marcelr
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Saturday 09 January 2016 7:57
by gizmocuz
Can i buy this sensor somewhere ?
If not, it might be best to contact the openzwave team for implementation, but it is hard to test without the actual device
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Sunday 10 January 2016 17:02
by marcelr
Can i buy this sensor somewhere ?
It comes as a part of Eneco's toon room thermostat. AFAIK it's only being sold in the Netherlands, on a reasonable scale at least. The whole set ships for EUR 275,-- or thereabouts.
http://www.thermostaatstore.nl/product/ ... latie.html
(Dutch only, I'm afraid)
And, it's not a sensor, it's an interface between a z-wave controller and (a P1-port of a smart meter, OR two optical sensors for classic digital displays on meters).
As you may have seen in the logs I posted, I/O inside the controller is done over a serial port, and it's quite easy to record the communication. I could do some tests and find out what's being transmitted, to get to the protocols (did that successfully for the other interface of this thermostat), but I'm quite ignorant when it comes to low-level z-wave communication. Time is another issue. That's a rare commodity for me lately.
grtz,
marcelr
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Sunday 10 January 2016 17:45
by gizmocuz
Hi marcelr,
thanks for the information!
Now this is ridiculous...
If you own a smart meter, just by the p1 smart meter cable from
http://www.smartmeterdashboard.nl/webshop
and your done!
Even so (also expensive) to control your thermostat, you can use the opentherm gateway
toon can control more, like zwave devices i believe, for +/- 25 euro, you have an usb zwave stick
If you want a tabled on the wall (like toon) sure you can find a cheaper android device
Okey, it all does not come out of the box and needs some work, but for the gas/electric readings the above cable is enough
(and i think you can also make it parallel by splitting with a telephone splitter)
Question is, why... if you have the toon device you want to control/read the ED2 as we have native toon support ?
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Sunday 10 January 2016 19:31
by marcelr
Question is, why... if you have the toon device you want to control/read the ED2 as we have native toon support ?
The support Domoticz supplies is geared towards toon owners with an Eneco account.
Initial buyers of toon used to have a contract with Eneco (a utilities seller in NL-BE). For EUR 3.50 or thereabouts per month, toon displays weather info, traffic, power usage in terms of EUR/day or whatever, comparisons with other users, that kind of stuff. The subscription also includes software updates.
Since mid last year, this device is also sold to non-Eneco customers (they pay a higher monthly rate).
All I/O is made available after checking customer subscriptions through the servers of a small IT company in the Netherlands: Quby B.V. The Domoticz code taps into that verified I/O. So, this works for paying customers only.
The devices have been on the market for some three years now. In that period, a fairly active second-hand trade in toon thermostats has been established as well.
Second-hand toons sell for EUR 25-130,-- depending on the seller, completeness of the device and time of year. This summer, I bought two more or less complete ones, for EUR 25,-- each.
People without Eneco account may still have a working toon thermostat, but cannot tap into toon's data (unless they hack their way into the machine, like yours truly). I think the TS has just the zwave adapter, probably bought/acquired second-hand, without the thermostat. And no account at Eneco's.
I agree that there are simpler ways to get P1 data from a smart meter, but if you have the Eneco device lying around, I don't see why you would not try and connect it, at least if you don't have to travel to hell and back to get it working.
The reason why I'm interested in the ED2.0 support is different (BTW, ED2.0 is the international, rather prozaic, name of toon as a whole, not only the P1 adapter). I don't care too much about the P1 interface (nice feature, good for testing since it already works with the thermostat, but not important), I just want to control other z-wave stuff with my toon than the software manufacturer lets me. TRV's (Danfoss LC 13), in combination with a boiler, all through one device, and better control software than Eneco supplies. Besides that, it's a nice little project to tinker with.
grtz,
marcelr
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Monday 11 January 2016 5:07
by gizmocuz
That makes perfect sense indeed !
Would be interesting to know if any ports are open on the device, or if you can reroute the DNS to your local home and see if you could emulate the original site and see if it will publish there
A shame you need to pay more as non-enoco customer, since you fully paid the device already
Edit: Have done some reading (might be you where also involved) and it seems you could access toon directly
Re: Openzwave Eneco ED2.0 Meter Adapter
Posted: Monday 11 January 2016 17:34
by marcelr
Edit: Have done some reading (might be you where also involved) and it seems you could access toon directly
You mean this one ?
http://www.domoticaforum.eu/viewtopic.php?f=17&t=8743
yup, that was me (and a bunch of other guys)
grtz,
marcelr