List of bugs

[nicholas-s]

Hi,

I´m currently encountering the following bugs with my Razberry installation:

- The Meter interview does not finish for any of my ~15 Everspring AN158 Switches with Metering function.
Re-including them or forcing the interview manually does not do anything. This behaviour is the same for every single one of them. They do support the METER_V2 command class.

This is the log file for the Force Re-interview of the Meter class:

[2013-06-09 15:47:04.534] Adding job: Meter supported get
[2013-06-09 15:47:04.536] SENDING (cb 0x96): ( 01 09 00 13 05 02 32 03 25 96 60 )
[2013-06-09 15:47:04.566] RECEIVED ACK
[2013-06-09 15:47:04.578] RECEIVED: ( 01 04 01 13 01 E8 )
[2013-06-09 15:47:04.587] SENT ACK
[2013-06-09 15:47:04.589] Delivered to Z-Wave stack
[2013-06-09 15:47:04.683] RECEIVED: ( 01 05 00 13 96 00 7F )
[2013-06-09 15:47:04.694] SENT ACK
[2013-06-09 15:47:04.696] Job 0x13 (Meter supported get): Delivered
[2013-06-09 15:47:04.698] SendData Response with callback 0x96 received: received by recipient
[2013-06-09 15:47:04.700] SETDATA devices.5.data.lastSend = 56690335 (0x0361069f)
[2013-06-09 15:47:04.702] Job 0x13 (Meter supported get): success
[2013-06-09 15:47:04.704] Removing job: Meter supported get

- I have two Aeon Labs Multisensors, both are detected as "Multi Sensor 1.18". After including them, they show up as sensors for Humidity,Temperature,Luminiscence and "State" (=motion detected). These values are all that they support. After a few days, new random sensors show up magically like "Generic", "Power" etc. This is very annoying as the values mix up with the "real" existing values and the readings are useless.

- Sometimes, lights do magically switch on and off e.g. at night.

- Configuration values from devices seem to be wandering across devices, e.g. if I read the configuration from all devices the configuration values do not seem to be associated to the correct device and show up at another one. This happens randomly.

I suspect that the whole queue management / data management is a bit messed up in Razberry and that this might be causing the effects I´m experiencing.

Unfortunately Razberry is not open software so I´m unable to fix this myself.
What can I do to get this right ? My installation is unusable at this point. I did already clean the network and start with a fresh installation, however this did not help.


Regards,
Nicholas

[PoltoS]

- Everspring interview unfinished is due to a bug in Everspring AN158 device. Not a RaZberry bug.
- The problem with Aeon Multisensor is unknown to us. Please provide the log (you can tell us the date it appeared and we will find the correct event in the log)
- Nightly switching are certainly not due to RaZberry At least in my home I've nothing like that Again, find this in the log and you will probably find the source of switch on commands. Also inspect queue will help to see if there are pending packets in the queue
- Config values mess: can you reproduce this? Never seen this problem. Please provide more info with screenshots.

The only reason I see for such problems are dead nodes. If the node is marked as dead Z-Way (only from version 1.3) will suspend further packets for several seconds, then for minutes, then for hours and if the device is still not reachable, for a day. May be in your case this happens.

May be it is a good idea to delete packets instead of delaying them to hours. All this is made not to block the queue by one single dead node.

[nicholas-s]

The everspring interview used to work in previous versions of Razberry (at least the first one) and works in Z-Cloud as well. Even if there is a bug in the Everspring firmware, the showing up of this effect might have something to do with a recent change in the RaZberry codebase. Regardless of that: What can I do to fix this ? I´m´still collecting the other data. Will get back later with that. How can I send screenshots to you ?