forum

Hallo Tobus, in meinem vorherigen Posting stand Blödsinn. Ich hatte Dein Beispiel nicht richtig gelesen - die Auswertung des Return-Arrays muss natürlich im Z-way erfolgen - nicht direkt im Script! Hier nun nochmal korrekt: Dein Python-Script gibt [0, "on"] (exit-, return-value) zurück. Du...

Hallo Tobus, hast Du es in der Zwischenzeit selbst lösen können? Das Problem liegt darin, dass Du in Deiner Abfrage den falschen Return-Wert auswertest. Wie Du in der Beispielzeile im Log siehst, kommt als Rückgabe [0,"on"] an. Das ist ein Array mit zwei Werten: der Erste ist der Exit-, de...

Hi Joachim, I also had such issues in the last years. They usually occur when I have not rebooted the raspberry pi for a long time. Approximately after 110 days. So far, I was able to rescue all devices, when I renewed the interview manually within the expertUI. I can imagine that this could be a si...

Hi nonnos, I'm afraid this will not work. Your systems are speaking different languages: Z-way (Z-wave) <-> trådfri (Zigbee). Not compatible! Unfortunately Trådfri is (at the moment) also not compatible to the Philips Hue system. Wait a few weeks until the Trådfri-Bridge gets an update and thus an o...

There are definitely issues with the notification.json! The included data starts with the time of the last system reboot and is not deleted even when restarting the z-way-server. If the file is to big, z-way crashs. Why are all notifications stored in this file permanently? This is not a good design...

Update to 2.3.1 brings no changes in behavior of V2.7 Fibaro Motion Sensors. Tamper Alarm is still not showing up in SmarthomeUI!

@Poltos: Are V2.7 Fibaro Motion Sensors not fully supported anymore?

I have also problems with the FGMS-01 in Razberry version 2.3.0. Specifically with hardware version 2.6 of the Multisensor. The tamper notification is no longer displayed in the Smarthome UI. In the Expert GUI, all sensors (Motion, Tamper, Illumination) are visible and are also updated correctly aft...

You are on the right way! The problem is, you will need a completed bluetooth connection between your Pebble and Pi for reading out live RSSI values. If you want to look up presence status only, the paired connection is not necessary! Just do a bluetooth name lookup with "hcitool name $MAC"...

Yes, for my setup it was necessary to change the existing file. The given postrotate script was not working properly! After the rotation the new logfile couldn't be written anymore.

With the config I posted above everything works so far now.

You may have already found a solution in the meantime. Here are my settings for a 24/7 duty, may be it helps anyway. 1) Mount /var/log to tempfs - edit /etc/fstab and add: tmpfs /var/log tmpfs defaults,noatime,nosuid,mode=0755,size=128m 0 0 tmpfs /var/run tmpfs defaults,noatime,nosuid,mode=0755,size...