Hallo all,

ich habe bei mir Fehler im zwave Adapter.

Ich habe als controler den USB Stick Aeotec AEOEZW090-C Aeon Labs im Einsatz.

Bei mehreren meiner Fibaro Sensoren habe ich Fehler bei numerischen Werten.

1.

Device: FIBARO System FGWPE/F Wall Plug Gen5

! {
! "common": {
! "name": "FIBARO System FGWPE/F Wall Plug Gen5",
! "role": "state"
! },
! "native": {
! "manufacturer": "FIBARO System",
! "manufacturerid": "0x010f",
! "product": "FGWPE/F Wall Plug Gen5",
! "producttype": "0x0602",
! "productid": "0x1001",
! "type": "On/Off Power Switch",
! "name": "",
! "loc": "",
! "nodeID": 8
! },
! "acl": {
! "object": 1636,
! "owner": "system.user.admin",
! "ownerGroup": "system.group.administrator"
! },
! "_id": "zwave.0.NODE8",
! "type": "device"
! }
State: zwave.0.NODE8.SENSOR_MULTILEVEL.Power_1

! {
! "common": {
! "name": "Power",
! "type": "number",
! "role": "sensor",
! "read": true,
! "write": false
! },
! "native": {
! "value_id": "8-49-1-4",
! "node_id": 8,
! "class_id": 49,
! "type": "decimal",
! "genre": "user",
! "instance": 1,
! "index": 4,
! "label": "Power",
! "units": "W",
! "help": "",
! "read_only": true,
! "write_only": false,
! "min": 0,
! "max": 0,
! "is_polled": false
! },
! "type": "state",
! "_id": "zwave.0.NODE8.SENSOR_MULTILEVEL.Power_1",
! "acl": {
! "object": 1636,
! "state": 1636
! }
! }

Die numerischen Werte werden als string auf den state geschrieben.

Auszug aus den Events:

stateChange zwave.0.NODE8.SENSOR_MULTILEVEL.Power_1 "157.1" true zwave.0 2017-10-27 21:03:45.555 2017-10-27 21:03:45.555

Device: FIBARO System FGK10x Door Opening Sensor

! {
! "common": {
! "name": "FIBARO System FGK10x Door Opening Sensor",
! "role": "state"
! },
! "native": {
! "nodeID": 14,
! "manufacturer": "FIBARO System",
! "manufacturerid": "0x010f",
! "product": "FGK10x Door Opening Sensor",
! "producttype": "0x0701",
! "productid": "0x1001",
! "type": "Access Control Sensor",
! "name": "",
! "loc": ""
! },
! "type": "device",
! "_id": "zwave.0.NODE14",
! "acl": {
! "object": 1636
! }
! }
Styte: zwave.0.NODE14.SENSOR_MULTILEVEL.Temperature_1

! {
! "common": {
! "name": "Temperature",
! "type": "number",
! "role": "value.temperature",
! "read": true,
! "write": false
! },
! "native": {
! "value_id": "14-49-1-1",
! "node_id": 14,
! "class_id": 49,
! "type": "decimal",
! "genre": "user",
! "instance": 1,
! "index": 1,
! "label": "Temperature",
! "units": "C",
! "help": "",
! "read_only": true,
! "write_only": false,
! "min": 0,
! "max": 0,
! "is_polled": false
! },
! "type": "state",
! "_id": "zwave.0.NODE14.SENSOR_MULTILEVEL.Temperature_1",
! "acl": {
! "object": 1636,
! "state": 1636
! }
! }

Auszug aus den Events:

stateChange zwave.0.NODE14.SENSOR_MULTILEVEL.Temperature_1 "23.12" true zwave.0 2017-10-27 21:03:33.544 2017-10-27 21:03:33.544

Ein kleiner Test mithilfe des ergab:

log (typeof getState("zwave.0.NODE14.SENSOR_MULTILEVEL.Temperature_1").val);

21:15:37.784	[info]	javascript.1 script.js.test.zwave: string
21:15:37.784	[info]	javascript.1 script.js.test.zwave: registered 0 subscriptions and 0 schedules

Ist der Bug schon bekannt?

Hat jemand den Bug bei sich auch?

Folgende Versionen habe ich laufen:

ioBroker.zwave: 0.8.0

ioBroker.js-controller: 1.1.3

ioBroker.admin: 2.0.9