Nico0084 / domogik-plugin-ozwave

Domogik ozwave plugin
GNU General Public License v3.0
1 stars 0 forks source link

ph-psm01 - Zipato Multisensor Trio #17

Open tikismoke opened 8 years ago

tikismoke commented 8 years ago

Sould be more easy all stats are in the advanced part:

Just need (i think) to look at how to update info.json to add this sort of device.

Will try (and make pull requests) but not certains of results.

tikismoke commented 8 years ago

got this on plxplugin_ozwave log

2016-01-03 21:09:53,737 domogik-ozwave DEBUG Publishing over MMQ , data : {'NetworkID': u'homeid', 'Node count': 8, 'Node sleeping': 6, 'data': {'i ndex': 1, 'units': '', 'type': 'Bool', 'nodeId': 15, 'value': False, 'commandClass': 'COMMAND_CLASS_SENSOR_BINARY', 'instance': 1, 'readOnly': True, 'homeId': 25485663 , 'label': 'Door/Window Sensor', 'genre': 'User', 'id': '72057594294566928'}, u'NodeID': 15, 'Node fail': 0, 'usermsg': 'Value has changed.', 'type': 'value-changed'}

Mais dans ozw.log il y ça:

2016-01-03 21:22:33.822 Info, Node015, Received SensorBinary report: Sensor:10 State=Off 2016-01-03 21:22:33.822 Detail, Node015, Refreshed Value: old value=true, new value=false, type=bool 2016-01-03 21:22:33.822 Detail, Node015, Changes to this value are not verified 2016-01-03 21:22:33.822 Detail, Node015, Notification: ValueChanged

Donc je pensais faire comme le fibaro motion utilisé simplement "sensor", mais ça ne semble pas fonctionner.

tikismoke commented 8 years ago

http://pastebin.com/tS6qZkUz Comment je l'ajoute au xPL?

tikismoke commented 8 years ago

Nico0084 Bsr 10:36 pm tikismoke, sur avec un label "Door/Window Sensor" tu vas avoir des soucis pour le lié à un device domogik 10:37 pm surtout en xpl

Maybe a string convertion somewhere in code? I did it in domodroid to avoid lot of problem replace all space by underscore, is it possible in the plugin?

Nico0084 commented 8 years ago

No interresting solution for xpl limitation. I thinks It's to much hard to handle many openzwave labels particularities in code

It was solved with non-xpl, so be patient ;) I have a version who begin work fine. I could merge it to develop next day.

Other problem is that your new devices ( FGMS001, NoON, Zipato) have sensor with same command_class and instance, so there is only label who can identify value, in this case, with domogik device, for the moment we must create a new json sensor with corresponding label (sensor "name" key)

With non-xpl (0.5) this is much easy to do.

2016-01-07 11:17 GMT+01:00 tikismoke notifications@github.com:

Nico0084 Bsr 10:36 pm tikismoke, sur avec un label "Door/Window Sensor" tu vas avoir des soucis pour le lié à un device domogik 10:37 pm surtout en xpl

Maybe a string convertion somewhere in code? I did it in domodroid to avoid lot of problem replace all space by underscore, is it possible in the plugin?

— Reply to this email directly or view it on GitHub https://github.com/Nico0084/domogik-plugin-ozwave/issues/17#issuecomment-169619575 .

tikismoke commented 8 years ago

Bon après t'es explication j'en suis là ce coup là: domogik-ozwave WARNING +++ More than one compatibility of domogik sensor. Device_type : 5in1.level.battery, sensors : {u'door_window_sensor': {u'conversion': u'from_Opening_Sensor_to_DT_OpenClose', u'value_min': None, u'data_type': u'DT_OpenClose', u'reference': u'door_window_sensor', u'last_received': None, u'value_max': None, u'incremental': False, u'timeout': 0, u'formula': None, u'last_value': None, u'id': 301, u'name': u'Door/Window Sensor'}, u'tamper_sensor': {u'conversion': u'from_Tamper_Event_to_DT_OpenClose', u'value_min': None, u'data_type': u'DT_OpenClose', u'reference': u'tamper_sensor', u'last_received': None, u'value_max': None, u'incremental': False, u'timeout': 0, u'formula': None, u'last_value': None, u'id': 304, u'name': u'Tamper sensor'}}