Problems after update to 4.032

[jojo1967 1]

After waiting for almost 1 year I updated my fibaro to the current firmware 4.032. Unfortunately I got some problems. Maybe someone had similiar experiences and some ideas or tricks...

- I got a message on the top of the screen that lots of my controllers have to be reconfigured. But I'm not sure how to do this (exclude / include?) and if this is a good idea because they still work

- Some devices changed there device type and picture but I could change it again

- Others still work but lost there room connection. When I tried to correct this I got a 403 message. I found no possibily to configure these devices anymore

- Whenever I include new battery devices under 4.032 the system said that the battery is empty. Even when I changed them against new ones

Please login or register to see this image.

/emoticons/default_icon_confused.gif" alt=":-?" />

- When I tried to include a ZWave.me Wallc controller it was recognized as an unknown Z-Wave device and I had no chance to change the device type to 'remote control' like for the same other devices

Please login or register to see this image.

/emoticons/default_icon_eek.gif" alt=":shock:" />

- And last but not least I hoped that the range of my Z-Wave network would get better with the new firmware (and a better antenna) but I still have some windows sensors out of range (not marked as dead nodes but without recognition of open/clos). I although bought a Z-Wave range extender from Aeonlabs but it doesn't work

Please login or register to see this image.

/emoticons/default_icon_cry.gif" alt=":cry:" />

Has anyone else similar problems or a solution for one of these problems?

Thanks a lot!

[djackson 0]

I have the same problems - I can't get the Zwave ME Wall Controller working again and now have a bunch of "Zwave_main_device" showing up in various rooms.

Plus Fibaro's Smoke Sensor and Motion Sensors have spawned a bunch of child devices.

A real mess.

I'll probably roll back and start looking for an alternative controller. Fibaro don't seem to be able to produce working software as is apparent from all the comments on the main thread re this release.

A shame. They could have been a leader.

[boomx 43]

- I got a message on the top of the screen that lots of my controllers have to be reconfigured. But I'm not sure how to do this (exclude / include?) and if this is a good idea because they still work

Go to Configuration -> Diagnostis -> ZWAVE... Click on reconfigure

- Whenever I include new battery devices under 4.032 the system said that the battery is empty. Even when I changed them against new ones

Please login or register to see this image.

/emoticons/default_icon_confused.gif" alt=":-?" />

It's a non-bug for non-Fibaro devices

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

- And last but not least I hoped that the range of my Z-Wave network would get better with the new firmware (and a better antenna) but I still have some windows sensors out of range (not marked as dead nodes but without recognition of open/clos). I although bought a Z-Wave range extender from Aeonlabs but it doesn't work

Please login or register to see this image.

/emoticons/default_icon_cry.gif" alt=":cry:" />

You can use non-battery-powered-devices (Wallplug, switches, rugby-controllers) to extend the range of your z-wave network.

Hope it helps...

[Joacim 11]

jojo and djackson: the forum is mostly complaints at the moment. That said most of the things actually do work as they should however the environment has changed a bit since 3.xx like the change is probably as large as moving from win95 to win98 some things are exactly the same but some are different.

Now I can't answer everything but if you browse the forum a bit you will find some more.

- I got a message on the top of the screen that lots of my controllers have to be reconfigured. But I'm not sure how to do this (exclude / include?) and if this is a good idea because they still work

--- If it is Fibaro devices you do a soft reconfig. Soft means you keep all the basics like ID and stuff. Scenes will work. If it is other brand devices and they work, you don't have to care about the warning, its just about that particular device doesn't have a parameter template yet.

- Some devices changed there device type and picture but I could change it again

-- I suppose this device needs a soft reconfig.

- Others still work but lost there room connection. When I tried to correct this I got a 403 message. I found no possibily to configure these devices anymore

-- First soft reconfig. Then try to change room for z wave main device and child.

- Whenever I include new battery devices under 4.032 the system said that the battery is empty. Even when I changed them against new ones

Please login or register to see this image.

/emoticons/default_icon_confused.gif" alt=":-?" />

-- My memory fails me but I belive somewhere in this forum someone is discussing the same issue.

- When I tried to include a ZWave.me Wallc controller it was recognized as an unknown Z-Wave device and I had no chance to change the device type to 'remote control' like for the same other devices

Please login or register to see this image.

/emoticons/default_icon_eek.gif" alt=":shock:" />

-- Same answer as above but maybe you need to contact support for this one.

- And last but not least I hoped that the range of my Z-Wave network would get better with the new firmware (and a better antenna) but I still have some windows sensors out of range (not marked as dead nodes but without recognition of open/clos). I although bought a Z-Wave range extender from Aeonlabs but it doesn't work

Please login or register to see this image.

/emoticons/default_icon_cry.gif" alt=":cry:" />

-- The hardware is still the same no possible changes in radiomodule. Zwave network is a mesh network that uses mains powered units as routers and doesn't rely on the controller to reach all devices. - If you got a main powered unit close to your battery powered ones the network can be routed trough that unit.

Oh well hope some of it makes sense and perhaps someone more knowledgeable will fill in the blanks.

Cheers!

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

[jojo1967 1]

Thanks for your ideas.

I didn´t know about the ZWave diagnostic tool. I will give it a try.

Yes, I although have the problem with lots of child devices.

Unfortunately the soft reconfig didn´t work. Even excluding and including again didn´t work. The wall controllers are allways recognized as an unknown ZWave device and I can´t change the type of device or anything else. Therefore I can´t use it in Magic Mode, because it´s not listed as a possible device.

Yes, there is something written in this forum about battery problems with the ZWave.me wall controllers too. It was my post, because I already had this problem with the old firmware but I still got no solution on this topic. Maybe someone from Fibaro could help.

I installed a Roller Shutter 2 from Fibaro 4m away from the window sensors but they are still out of range and don´t recognize open/close. I will try to reconfigure the Z-Wave network with the diagnostic tool. Is there a special reason, why the range extender from Aeonlabs is not supported?

Thanks

JoJo

[petergebruers 1,268]

You may want to check the bug tracker

Please login or register to see this link.

- certainly several bugs are devoted to zwave.me. Devices changing room after upgrade is another one.

From V4 onwards all devices have a master and at least one slave. You don't actually use the master, only the slave(s).