NEWS
Zwave 0.4
-
Hast du log dafür? ` ich versuche es mal…
> ****1:) Rollo oben (99) –> setze Wert 50 in Objekte --> Relais "klickt", Rollo fährt nicht, Wert geht wieder auf 99 zurück****! ````
2016-11-12 20:22:20.887 Info, Node002, SwitchMultilevel::Set - Setting to level 50
2016-11-12 20:22:20.888 Info, Node002, Duration: Default
2016-11-12 20:22:20.888 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0b, 0x00, 0x13, 0x02, 0x04, 0x26, 0x01, 0x32, 0xff, 0x25, 0x46, 0x68
2016-11-12 20:22:20.888 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0x47, 0xa3
2016-11-12 20:22:20.888 Detail,
2016-11-12 20:22:20.889 Info, Node002, Sending (Send) message (Callback ID=0x46, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0b, 0x00, 0x13, 0x02, 0x04, 0x26, 0x01, 0x32, 0xff, 0x25, 0x46, 0x68
2016-11-12 20:22:20.897 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-11-12 20:22:20.898 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2016-11-12 20:22:20.915 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x46, 0x00, 0x00, 0x02, 0xaf
2016-11-12 20:22:20.915 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x46 received (expected 0x46)
2016-11-12 20:22:20.915 Info, Node002, Request RTT 26 Average Request RTT 26
2016-11-12 20:22:20.915 Detail, Expected callbackId was received
2016-11-12 20:22:20.915 Detail, Expected reply was received
2016-11-12 20:22:20.916 Detail, Message transaction complete
2016-11-12 20:22:20.916 Detail,
2016-11-12 20:22:20.916 Detail, Node002, Removing current message
2016-11-12 20:22:20.916 Detail,
2016-11-12 20:22:20.916 Info, Node002, Sending (Send) message (Callback ID=0x47, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0x47, 0xa3
2016-11-12 20:22:20.926 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-11-12 20:22:20.926 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2016-11-12 20:22:20.943 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x47, 0x00, 0x00, 0x02, 0xae
2016-11-12 20:22:20.943 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x47 received (expected 0x47)
2016-11-12 20:22:20.943 Info, Node002, Request RTT 23 Average Request RTT 24
2016-11-12 20:22:20.943 Detail, Expected callbackId was received
2016-11-12 20:22:20.955 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x63, 0xb5
2016-11-12 20:22:20.956 Detail,
2016-11-12 20:22:20.956 Info, Node002, Response RTT 35 Average Response RTT 36
2016-11-12 20:22:20.956 Info, Node002, Received SwitchMultiLevel report: level=99
2016-11-12 20:22:20.956 Detail, Node002, Refreshed Value: old value=99, new value=99, type=byte
2016-11-12 20:22:20.956 Detail, Node002, Changes to this value are not verified
2016-11-12 20:22:20.956 Detail, Node002, Expected reply and command class was received
2016-11-12 20:22:20.957 Detail, Node002, Message transaction complete
2016-11-12 20:22:20.957 Detail,
2016-11-12 20:22:20.957 Detail, Node002, Removing current message
2016-11-12 20:22:20.957 Detail, Node002, Notification: ValueChanged
2016-11-12 20:22:22.976 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x63, 0xb5
2016-11-12 20:22:22.976 Detail,
2016-11-12 20:22:22.977 Info, Node002, Received SwitchMultiLevel report: level=99
2016-11-12 20:22:22.977 Detail, Node002, Refreshed Value: old value=99, new value=99, type=byte
2016-11-12 20:22:22.977 Detail, Node002, Changes to this value are not verified
2016-11-12 20:22:22.977 Detail, Node002, Notification: ValueChanged
2016-11-12 20:22:23.001 Detail, Node002, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xe1
2016-11-12 20:22:23.001 Detail,
2016-11-12 20:22:23.001 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Power: value=0.0W
2016-11-12 20:22:23.001 Detail, Node002, Refreshed Value: old value=0.0, new value=0.0, type=decimal
2016-11-12 20:22:23.001 Detail, Node002, Changes to this value are not verified
2016-11-12 20:22:23.002 Detail, Node002, Notification: ValueChanged` > ****2:) Rollo oben (99) –> setze Wert 0 in Objekte --> Relais "klickt", Rollo fährt ganz runter, Wert geht auf 0**** ` >! ```` 2016-11-12 20:25:31.015 Info, Node002, SwitchMultilevel::Set - Setting to level 0 2016-11-12 20:25:31.015 Info, Node002, Duration: Default 2016-11-12 20:25:31.015 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0b, 0x00, 0x13, 0x02, 0x04, 0x26, 0x01, 0x00, 0xff, 0x25, 0x48, 0x54 2016-11-12 20:25:31.015 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0x49, 0xad 2016-11-12 20:25:31.015 Detail, 2016-11-12 20:25:31.016 Info, Node002, Sending (Send) message (Callback ID=0x48, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0b, 0x00, 0x13, 0x02, 0x04, 0x26, 0x01, 0x00, 0xff, 0x25, 0x48, 0x54 2016-11-12 20:25:31.025 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2016-11-12 20:25:31.025 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack 2016-11-12 20:25:31.042 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x48, 0x00, 0x00, 0x02, 0xa1 2016-11-12 20:25:31.043 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x48 received (expected 0x48) 2016-11-12 20:25:31.043 Info, Node002, Request RTT 26 Average Request RTT 25 2016-11-12 20:25:31.043 Detail, Expected callbackId was received 2016-11-12 20:25:31.043 Detail, Expected reply was received 2016-11-12 20:25:31.043 Detail, Message transaction complete 2016-11-12 20:25:31.043 Detail, 2016-11-12 20:25:31.044 Detail, Node002, Removing current message 2016-11-12 20:25:31.044 Detail, 2016-11-12 20:25:31.044 Info, Node002, Sending (Send) message (Callback ID=0x49, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0x49, 0xad 2016-11-12 20:25:31.057 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2016-11-12 20:25:31.058 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack 2016-11-12 20:25:31.071 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x49, 0x00, 0x00, 0x02, 0xa0 2016-11-12 20:25:31.071 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x49 received (expected 0x49) 2016-11-12 20:25:31.071 Info, Node002, Request RTT 26 Average Request RTT 25 2016-11-12 20:25:31.071 Detail, Expected callbackId was received 2016-11-12 20:25:31.080 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x63, 0xb5 2016-11-12 20:25:31.081 Detail, 2016-11-12 20:25:31.081 Info, Node002, Response RTT 36 Average Response RTT 36 2016-11-12 20:25:31.081 Info, Node002, Received SwitchMultiLevel report: level=99 2016-11-12 20:25:31.081 Detail, Node002, Refreshed Value: old value=99, new value=99, type=byte 2016-11-12 20:25:31.081 Detail, Node002, Changes to this value are not verified 2016-11-12 20:25:31.081 Detail, Node002, Expected reply and command class was received 2016-11-12 20:25:31.081 Detail, Node002, Message transaction complete 2016-11-12 20:25:31.081 Detail, 2016-11-12 20:25:31.081 Detail, Node002, Removing current message 2016-11-12 20:25:31.082 Detail, Node002, Notification: ValueChanged 2016-11-12 20:25:32.188 Detail, Node002, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x31, 0x05, 0x04, 0x22, 0x04, 0xdd, 0x38 2016-11-12 20:25:32.188 Detail, 2016-11-12 20:25:32.188 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Power: value=124.5W 2016-11-12 20:25:32.189 Detail, Node002, Refreshed Value: old value=0.0, new value=124.5, type=decimal 2016-11-12 20:25:32.189 Detail, Node002, Changes to this value are not verified 2016-11-12 20:25:32.189 Detail, Node002, Notification: ValueChanged 2016-11-12 20:25:47.501 Detail, Node002, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xe1 2016-11-12 20:25:47.501 Detail, 2016-11-12 20:25:47.502 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Power: value=0.0W 2016-11-12 20:25:47.502 Detail, Node002, Refreshed Value: old value=124.5, new value=0.0, type=decimal 2016-11-12 20:25:47.502 Detail, Node002, Changes to this value are not verified 2016-11-12 20:25:47.502 Detail, Node002, Notification: ValueChanged 2016-11-12 20:25:48.661 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x00, 0xd6 2016-11-12 20:25:48.661 Detail, 2016-11-12 20:25:48.661 Info, Node002, Received SwitchMultiLevel report: level=0 2016-11-12 20:25:48.661 Detail, Node002, Refreshed Value: old value=99, new value=0, type=byte 2016-11-12 20:25:48.662 Detail, Node002, Changes to this value are not verified 2016-11-12 20:25:48.662 Detail, Node002, Notification: ValueChanged 2016-11-12 20:25:48.681 Detail, Node002, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xe1 2016-11-12 20:25:48.681 Detail, 2016-11-12 20:25:48.681 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Power: value=0.0W 2016-11-12 20:25:48.682 Detail, Node002, Refreshed Value: old value=0.0, new value=0.0, type=decimal 2016-11-12 20:25:48.682 Detail, Node002, Changes to this value are not verified 2016-11-12 20:25:48.682 Detail, Node002, Notification: ValueChanged> ****3:) Rollo unten (0) –> setze Wert 50 in Objekte --> Relais "klickt", Rollo fährt ganz hoch, Wert geht auf 99****! ````
2016-11-12 20:27:09.764 Info, Node002, SwitchMultilevel::Set - Setting to level 50
2016-11-12 20:27:09.764 Info, Node002, Duration: Default
2016-11-12 20:27:09.764 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0b, 0x00, 0x13, 0x02, 0x04, 0x26, 0x01, 0x32, 0xff, 0x25, 0x4a, 0x64
2016-11-12 20:27:09.764 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0x4b, 0xaf
2016-11-12 20:27:09.765 Detail,
2016-11-12 20:27:09.765 Info, Node002, Sending (Send) message (Callback ID=0x4a, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0b, 0x00, 0x13, 0x02, 0x04, 0x26, 0x01, 0x32, 0xff, 0x25, 0x4a, 0x64
2016-11-12 20:27:09.774 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-11-12 20:27:09.774 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2016-11-12 20:27:09.792 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x4a, 0x00, 0x00, 0x02, 0xa3
2016-11-12 20:27:09.792 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x4a received (expected 0x4a)
2016-11-12 20:27:09.792 Info, Node002, Request RTT 26 Average Request RTT 25
2016-11-12 20:27:09.792 Detail, Expected callbackId was received
2016-11-12 20:27:09.792 Detail, Expected reply was received
2016-11-12 20:27:09.793 Detail, Message transaction complete
2016-11-12 20:27:09.793 Detail,
2016-11-12 20:27:09.793 Detail, Node002, Removing current message
2016-11-12 20:27:09.793 Detail,
2016-11-12 20:27:09.793 Info, Node002, Sending (Send) message (Callback ID=0x4b, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0x4b, 0xaf
2016-11-12 20:27:09.802 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-11-12 20:27:09.802 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2016-11-12 20:27:09.819 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x4b, 0x00, 0x00, 0x03, 0xa3
2016-11-12 20:27:09.819 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x4b received (expected 0x4b)
2016-11-12 20:27:09.819 Info, Node002, Request RTT 25 Average Request RTT 25
2016-11-12 20:27:09.819 Detail, Expected callbackId was received
2016-11-12 20:27:09.833 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x00, 0xd6
2016-11-12 20:27:09.833 Detail,
2016-11-12 20:27:09.834 Info, Node002, Response RTT 39 Average Response RTT 37
2016-11-12 20:27:09.834 Info, Node002, Received SwitchMultiLevel report: level=0
2016-11-12 20:27:09.834 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte
2016-11-12 20:27:09.834 Detail, Node002, Changes to this value are not verified
2016-11-12 20:27:09.834 Detail, Node002, Expected reply and command class was received
2016-11-12 20:27:09.834 Detail, Node002, Message transaction complete
2016-11-12 20:27:09.835 Detail,
2016-11-12 20:27:09.835 Detail, Node002, Removing current message
2016-11-12 20:27:09.835 Detail, Node002, Notification: ValueChanged
2016-11-12 20:27:10.937 Detail, Node002, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x31, 0x05, 0x04, 0x22, 0x04, 0xe6, 0x03
2016-11-12 20:27:10.938 Detail,
2016-11-12 20:27:10.938 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Power: value=125.4W
2016-11-12 20:27:10.938 Detail, Node002, Refreshed Value: old value=0.0, new value=125.4, type=decimal
2016-11-12 20:27:10.938 Detail, Node002, Changes to this value are not verified
2016-11-12 20:27:10.938 Detail, Node002, Notification: ValueChanged
2016-11-12 20:27:26.252 Detail, Node002, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xe1
2016-11-12 20:27:26.253 Detail,
2016-11-12 20:27:26.253 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Power: value=0.0W
2016-11-12 20:27:26.253 Detail, Node002, Refreshed Value: old value=125.4, new value=0.0, type=decimal
2016-11-12 20:27:26.253 Detail, Node002, Changes to this value are not verified
2016-11-12 20:27:26.253 Detail, Node002, Notification: ValueChanged
2016-11-12 20:27:27.583 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x63, 0xb5
2016-11-12 20:27:27.584 Detail,
2016-11-12 20:27:27.584 Info, Node002, Received SwitchMultiLevel report: level=99
2016-11-12 20:27:27.584 Detail, Node002, Refreshed Value: old value=0, new value=99, type=byte
2016-11-12 20:27:27.584 Detail, Node002, Changes to this value are not verified
2016-11-12 20:27:27.585 Detail, Node002, Notification: ValueChanged
2016-11-12 20:27:27.602 Detail, Node002, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xe1
2016-11-12 20:27:27.603 Detail,
2016-11-12 20:27:27.603 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Power: value=0.0W
2016-11-12 20:27:27.603 Detail, Node002, Refreshed Value: old value=0.0, new value=0.0, type=decimal
2016-11-12 20:27:27.603 Detail, Node002, Changes to this value are not verified
2016-11-12 20:27:27.604 Detail, Node002, Notification: ValueChanged -
Kleiner Bug, Zeile 811:
zwave.on('driver failed', function () { adapter.setState('info.connection', false, true); adapter.log.error('failed to start driver'); >>> zwave.disconnect('/dev/' + adapter.config.usb); <<< process.exit(); });In der markierten Zeile müsste '/dev/' + raus, das ist noch ein Relikt der alten Version.
-
Ich habe die Möglichkeit benötigt, die Gerätekonfiguration zu modifizieren. Da das noch nicht implementiert ist in 0.4, habe ich es eben mal nachgerüstet.
main.js, Zeile 388 - 390 (vorher)
adapter.log.debug('setState for: nodeID=' + obj.native.node_id + ': comClass=' + obj.native.class_id + ': index=' + obj.native.index + ': instance=' + obj.native.instance + ': value=' + value); if (zwave) zwave.setValue(obj.native.node_id, obj.native.class_id, obj.native.instance, obj.native.index, value);wird zu
if (obj.common.role === 'meta.config') { // set a configuration parameter adapter.log.debug('setConfigParam for: nodeID=' + obj.native.node_id + ': index=' + obj.native.index + ': value=' + value); if (zwave) zwave.setConfigParam( obj.native.node_id, obj.native.index, value, value.length ) } else { // set a value adapter.log.debug('setState for: nodeID=' + obj.native.node_id + ': comClass=' + obj.native.class_id + ': index=' + obj.native.index + ': instance=' + obj.native.instance + ': value=' + value); if (zwave) zwave.setValue(obj.native.node_id, obj.native.class_id, obj.native.instance, obj.native.index, value); }Wenn ich dir solche Änderungen auf einem besseren Weg zukommen lassen kann, lass es mich bitte wissen. Helfe gerne dabei, den für mich (zweit-)wichtigsten Adapter vorwärts zu bringen.
-
-
@Bluefox: Dann tagge ich dich einfach jedesmal, wenn ich was für den Adapter habe, ok?
–-
Ich habe noch etwas weiter gebuddelt, um meinem Konfigurationsproblem auf den Grund zu gehen (siehe Post http://forum.iobroker.net/viewtopic.php ... 6ab#p39876 ).
Der Adapter verwendet das Serialport-Modul, um Informationen über die seriellen Schnittstellen zu erhalten. So wie ich das sehe, reicht die Liste der Adressen aus, das Modul geht allerdings weiter und ersetzt diese durch den COM-Namen. In meinem Fall heißt die Razberry-Platine auf Systemebene tatsächlich nur "ttyAMA0", was fälschlicherweise als ihr Pfad (der /dev/ttyAMA0 lautet) interpretiert wird.
Ich habe daraufhin den Adapter modifiziert, sodass er die Erkennung der seriellen Schnittstellen selbst macht. Der beschriebene Fehler ist weg und ioBroker erkennt beide Pfadnamen korrekt.
Zeile 12 ersetzt
var Serialport = require('serialport');durch
var path = require('path');Ergänzt (du wirst wissen, wo du sowas am liebsten hättest):
var listSerial = function () { // Filter out the devices that aren't serial ports filterSerialPorts = function (path) { // get only serial port names if (!(/(tty(S|ACM|USB|AMA|MFD)|rfcomm)/).test(path)) { return false; } return fs .statSync(path) .isCharacterDevice() ; }; var dirName = '/dev'; var serialPorts = fs .readdirSync(dirName) .map(function (file) { return path.join(dirName, file); }) .filter(filterSerialPorts) .map(function (port) { return { comName: port }; }) ; return serialPorts; };Zeilen 112 - 121 ersetzt
if (Serialport) { // read all found serial ports Serialport.list(function (err, ports) { adapter.log.info('List of port: ' + JSON.stringify(ports)); adapter.sendTo(obj.from, obj.command, ports, obj.callback); }); } else { adapter.log.warn('Module serialport is not available'); adapter.sendTo(obj.from, obj.command, [{ comName: 'Not available' }], obj.callback); }durch
var ports = listSerial(); adapter.log.info('List of ports: ' + JSON.stringify(ports)); adapter.sendTo(obj.from, obj.command, ports, obj.callback);–-
Bezüglich des UI-Bugs (ebenfalls Post http://forum.iobroker.net/viewtopic.php ... 6ab#p39876):
Brauchst du Logs oder irgendwas, um das nachzuvollziehen?
-
` > Allerdings scheint auch hier die UI etwas buggy:
Изображение
Ich setze den Haken, bestätige und das Relais schaltet an. In der Oberfläche steht aber weiterhin "false" als Zustand, egal ob das Relais nun an ist oder nicht. `
Bedienelement zeigt aktuellen Zustand. Normalerweise wenn ein Befehl gesendet wird wird der Text rot, dann wenn ein Feedback (Update) vom Gerät kommt, wird den Text mit dem aktuellen Zustand als Schwarz dargestellt.
D.h. wenn du steuerst, dann antwortet das Gerät mit "false" zurück. Man kann das in den Logs sehen. Kannst du hier die posten?
> Wäre es möglich, das Konfigurationsfenster standardmäßig etwas größer zu gestalten? Ich muss schon scrollen, wenn ich in der Geräteliste das Aktions-Dropdown anzeigen will.
Screenshot? -
Habe eingepflegt. 0.4.2 Danke. `
Ein Traum![…] D.h. wenn du steuerst, dann antwortet das Gerät mit "false" zurück. Man kann das in den Logs sehen. Kannst du hier die posten? `
Bittesehr:!
2016-11-15 20:25:18.623 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True 2016-11-15 20:25:18.625 Info, Node003, SwitchBinary::Set - Setting node 3 to On 2016-11-15 20:25:18.626 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0xb7, 0xaf 2016-11-15 20:25:18.627 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0xb8, 0x5e 2016-11-15 20:25:18.628 Detail, 2016-11-15 20:25:18.629 Info, Node003, Sending (Send) message (Callback ID=0xb7, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0xff, 0x25, 0xb7, 0xaf 2016-11-15 20:25:18.636 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2016-11-15 20:25:18.638 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack 2016-11-15 20:25:18.652 Detail, Node003, Received: 0x01, 0x07, 0x00, 0x13, 0xb7, 0x00, 0x00, 0x02, 0x5e 2016-11-15 20:25:18.653 Detail, Node003, ZW_SEND_DATA Request with callback ID 0xb7 received (expected 0xb7) 2016-11-15 20:25:18.653 Info, Node003, Request RTT 23 Average Request RTT 22 2016-11-15 20:25:18.654 Detail, Expected callbackId was received 2016-11-15 20:25:18.654 Detail, Expected reply was received 2016-11-15 20:25:18.655 Detail, Message transaction complete 2016-11-15 20:25:18.655 Detail, 2016-11-15 20:25:18.655 Detail, Node003, Removing current message 2016-11-15 20:25:18.656 Detail, 2016-11-15 20:25:18.657 Info, Node003, Sending (Send) message (Callback ID=0xb8, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0xb8, 0x5e 2016-11-15 20:25:18.663 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8 2016-11-15 20:25:18.664 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack 2016-11-15 20:25:18.679 Detail, Node003, Received: 0x01, 0x07, 0x00, 0x13, 0xb8, 0x00, 0x00, 0x01, 0x52 2016-11-15 20:25:18.680 Detail, Node003, ZW_SEND_DATA Request with callback ID 0xb8 received (expected 0xb8) 2016-11-15 20:25:18.680 Info, Node003, Request RTT 22 Average Request RTT 22 2016-11-15 20:25:18.681 Detail, Expected callbackId was received 2016-11-15 20:25:18.688 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x25, 0x03, 0xff, 0x2b 2016-11-15 20:25:18.689 Detail, 2016-11-15 20:25:18.689 Info, Node003, Response RTT 31 Average Response RTT 31 2016-11-15 20:25:18.689 Info, Node003, Received SwitchBinary report from node 3: level=On 2016-11-15 20:25:18.690 Detail, Node003, Refreshed Value: old value=false, new value=true, type=bool 2016-11-15 20:25:18.690 Detail, Node003, Changes to this value are not verified 2016-11-15 20:25:18.691 Detail, Node003, Expected reply and command class was received 2016-11-15 20:25:18.691 Detail, Node003, Message transaction complete 2016-11-15 20:25:18.691 Detail, 2016-11-15 20:25:18.692 Detail, Node003, Removing current message 2016-11-15 20:25:18.692 Detail, Node003, Notification: ValueChanged !
Das sieht für mich nach der korrekten Antwort aus: old value=false, new value=true. Da mein Sensor plötzlich Mist baut, werde ich mal mit Adapter und OZW-Log spielen. Vielleicht stoße ich dann auch auf die Ursache dieses Problems.>> Wäre es möglich, das Konfigurationsfenster standardmäßig etwas größer zu gestalten? Ich muss schon scrollen, wenn ich in der Geräteliste das Aktions-Dropdown anzeigen will. `Screenshot? `
Habe das Fenster inzwischen etwas größer gezogen, die Einstellung scheint ioBroker sich zu merken. Vielleicht ein Überbleibsel der alten Version, das bei der Installation nicht richtig überschrieben wurde?Habe mal versucht, die Abmaße aus der io-package.json herzustellen. Hier passt alles drauf, insgesamt bleibt relativ wenig Platz für die Geräteliste übrig (ca. 50%). Vielleicht kann man hier was an der Schriftgröße optimieren, insbesondere im Dropdown kann es IMO kleiner.
-
Bekomme Fibaro FIBEFGMS-001-ZW5 5G 4-in-1 Multisensor nicht angemeldet.. :( Geht das überhaupt mit dem ZME_UZB1 USB Stick? `
Ja, pass auf dass er zwave+ unterstützt.
Also nimm am besten den G5, unterstütz alles und du kannst mit der batterie im Haus rumlaufen und alles ab zu lernen
Das ist der fuffie Wert
Sent from my iPhone using Tapatalk
-
Habe das Problem mit dem falschen Schalter-Zustand gefunden. Das war übrigens auch die Ursache für das seltsame Verhalten meines Sensors.
In Zeile 624-625 wird aus allen möglichen Variablentypen in "boolean" umgewandelt:
if (stateObj.common.type === 'boolean') { value = value === 'true' || value === 255 || value === '255' || value === 'On' || value === 1 || value === '1'; }Dabei ging allerdings der Fall vergessen, dass es sich bei der Variable bereits um ein Boolean handelt. In dem Fall wird value immer auf false gesetzt. Lässt sich mit einer kleinen Abfrage beheben:
if (stateObj.common.type === 'boolean') { // we might have to translate the value to boolean if (typeof value !== 'boolean') value = value === 'true' || value === 255 || value === '255' || value === 'On' || value === 1 || value === '1'; } -
Kleine Verständnisfrage…
Ich benutze
npm install https://github.com/ioBroker/ioBroker.zwave/tarball/master --production --unsave-perm --build-from-sourceAber damit wird jedesmal open-zwave neu installiert. Muss das so?
-
> Die Option heißt übrigens –unsafe-perm.
Auch wieder wahr. Ich hab's mit –unsave-perm laufen lassen und es hat sich installiert. --unsafe-perm scheint also nicht notwendig zu sein. Kann aber auch sein, dass es lief, weil ich schon die 0.4.0 drauf hatte. -
Sollte mit
npm install https://github.com/ioBroker/ioBroker.zwave/tarball/master --productionLaufen. Openzwave wird tatsächlich jedes mal neu übersetzt. `
Und das ist auch OK, die librarys werden auch regelmäßig geupdatet und so bekommt man immer die neuste git Source von openzwave (wichtig für neue Controller & Hardware !)
Sent from my iPhone using Tapatalk
-
-
@Bluefox: konntest du dir schon mal die OZW-Logs zum Rollo-Problem anschauen?
Support us
631
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge