2
Choose style:

Author Topic: Status after somes tests.  (Read 7244 times)

0 Members and 1 Guest are viewing this topic.

Offline dsponz

  • Backer
  • *
  • Posts: 2
  • Thanks: 0
  • Registered : 04/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Status after somes tests.
« on: September 29, 2014, 03:11:32 am »
Hi,

I received my almond+ 20 september morning without any extra charge (France). Just after open the box I was very exited the product looks great with a perfect quality and design. Great jobs! Congratulations.

I have tested a lot of functions this weekend and it works for a lot features but I have tried to make changes and I found some bugs:

- if you change the ip of the almond+ on the lan bridge it works but the web server must be reboot if you want to access one the new ip.
- I created a new interface in the openwrt ui called "wlan" and I tried to associate the two wifi interfaces on it but nothing is working at this point on wifi. The new wlan bridge interface don't up and the brctl show command (in ssh access) don't show my new wlan. I want to do this because I want a second address range on my wifi network. Do you think this feature will be available?
- the last point it's about zwave feature, I bought a lot of fibaro modules and it doesn't work. I dont understand your configuration, you seems to use open zwave library that recognize my module ( I found in fibaro folder the all config files) but Almond+ don't recognize my roller shutter or my  FGWPE/F-101. I had two door / sensor module it works just few minutes and now it doesn't work at all and i can't remove all module because it failed and I reset the Almond+ without success my module are still there and it doesn't work. Now I can't add more modules too and I don't know what I can do to resolve this.

Can you help me ?

Thank's.

Best,
Damien.

LGNilsson

  • Guest
Re: Status after somes tests.
« Reply #1 on: September 29, 2014, 03:25:35 am »
Well, for one, we're not really using open Z-Wave, just some minor parts of it.

We don't actually support many of the devices from Fibaro as yet, but the door sensors should work just fine, so I'm not sure what's going on here. Did you upgrade your Almond+ to the latest firmware? We fixed a couple of Z-Wave related bugs in R066.

We'll get support for the rolling shutter in a future firmware, as we actually have one, it just haven't been a priority. The wallplug on the other hand is working just fine, I tested it as recently as last week as in R066 we added support for power monitoring.

The problem is that the Fibaro sensors are a bit awkward to add and remove, as they're way to precise when it comes to pressing the button in sequence. I've had problems with this as well. You need to go into Add sensor in the LCD UI, then Remove and simply just keep pressing the button three times quickly until they're removed. Resetting the Almond+ will not remove sensors and you should not use the remove all option for Z-Wave sensors, as they have to be reset by the gateway/coordinator or you won't be able to pair them again since there's no way to reset a Z-Wave sensors unless it's done from a gateway/coordinator. ZigBee is much better for this, as you can reset a sensor on its own.

As for your other questions, I'm afraid I'm not going to be of much help.

Offline dsponz

  • Backer
  • *
  • Posts: 2
  • Thanks: 0
  • Registered : 04/08/2013
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: Status after somes tests. => Zwave doesn't works
« Reply #2 on: October 19, 2014, 11:51:28 am »
Hi,

I can't use zwave feature on Almond+.

The zwcfg_home.xml file show some modules but nothing in my cloud account or on "Connected Sensors" in the menu.

How I can reset the zwcfg configuration ?  because I can't add module, I can't remove module or do anything else. I also tried to restore with a zwcfg edit file without module but after restoration the file contains the modules ...

thank you.
Damien.

 

Page created in 0.033 seconds with 16 queries.

bottleneck