Endless problems of jobs stuck in queue

[bogr]

Yes, they are both already at approx the same distance now, for testing, 1-2m. I also thought the device could be problematic at first (I've already replaced one due to battery drainage), but it "feels" more like a software problem. It sounds a bit strange that the device can behave this flakey, it should be either broken or working - more or less. Some kind of in-the-middle status sounds a bit unlogical. Especially with the fact in mind that there have been multiple additional strange behaviours after upgrading to 2.2.0 - Callback execution error, Too many bindings to one dataholder, Associations...I have no problems in understanding there might be bugs in the SW, but the most important thing is addressing the bugs....

I was also hoping for the zwave.me to give some more input, but nothing yet.

[pz1]

These wireless networks are evil. I have one Fibaro Universal sensor 4 meters away from my controller. Only 9mm plasterboard in between. Very weak connection, often erroneous readings. On the other hand one Fibaro Wall plug stowed away in a kitchen cupboard, just next to a dishwasher underneath a stainless steel top. The Z-wave signal has to pass through 2 brick walls with doors and a 4cm wooden floor. Direct distance 8 meters. It does have a light green level on the routing map, but still it operates fine.....