forum

After updating my software to v2.2.2. I am seeing the isAwake property sticking to true. Is there a bug related to security enabled devices and going to sleep properly?

I did see this in the v2.0.1-rc15 release notes.

Fixes:
- Queueing made more stable. Sleeping secure devices managed better.

I am testing one of the new Fibaro FGFS-101 500 Series and the isAwake property is not updating when I wake the device by pressing the button. This works perfectly with the older 300 series device. I am running 03.02.2015 v2.0.1-rc15. Any ideas besides updating the software? I would rather not updat...

Bump

[2015-08-06 12:51:20.886] RECEIVED: ( 01 12 00 04 00 08 0C 60 0D 02 02 31 05 01 44 00 00 A8 E3 BA ) [2015-08-06 12:51:20.887] SENT ACK [2015-08-06 12:51:20.888] SETDATA devices.8.data.lastReceived = 0 (0x00000000) [2015-08-06 12:51:20.888] SETDATA devices.8.instances.2.commandClasses.49.data.1.devic...

At times, my Fibaro flood sensors are reporting the temperature to be in the 1000C or above. I never seemed to have this problem in v1.72, but in v2.0.1-rc23 the problem is much more common. Anyone else seeing these issues?

Are all ZDDX assignments done manually? If there is a clear choice, is the assignment made automatically as the device is included? If it is automatic, what parameters must match in order for the ZDDX assignment to be made automatically? I am trying to include a Fibaro FGFS-101 but the ZDDX record h...

I figured it out. I had to add the RaZberry to the device's association group 3. That allowed for unsolicited temperature and battery updates. I had to connect a power supply to the battery terminals to adjust the battery level enough to trigger an update. The temperature updates are sent as a multi...

I am not receiving unsolicited battery level updates from the Fibaro FGFS-101 flood sensor. I have attached zniffer file of the Multi Channel Cmd Encap frame that is sent from the device whenever the temperature changes. Does that same command also include the battery level? This is the log that is ...

I have had multiple instances where a Wakeup Notification Command was incorrectly received and acknowledged by z-way-server, but correctly received by zniffer. [2015-05-04 06:54:45.408] RECEIVED: ( 01 08 00 04 00 0A 02 CB 07 37 ) [2015-05-04 06:54:45.409] SENT ACK [2015-05-04 06:54:45.410] Got frame...

I am currently running v1.7.2, but it has a memory leak issue that requires z-way-server to be restarted every several days. I thought about rolling back to v.1.7.1, but I see in the release notes where it has a memory leak in http.request(). Since I use http.request() very frequently, this doesn't ...