R069 Firmware disappointment

[KT]

I want to know why there is two separate posts for Firmware releases. You are doubling the work of yourself and end users having to check multiple posts to see if the firmware is even compatible.

Features pulled from this thread.
http://forum.securifi.com/index.php/topic,2233.0.html
Features
5GHz Wi-Fi disconnects on some devices
Wi-Fi performance is still not optimized
AP mode has been disabled in this release.
SAMBA doesn't work properly with OS X and Linux

I currently use the almond+ in AP mode and almost updated without reading the other post. Anyone with AP mode is forced to wait... how long?
How can the new Wi-Fi drivers not be applied to these new releases?
End users have been complaining and struggling since they have started using the device. Why would you be adding new devices like the Philips Hue bulb when there are major problems or features that should have been ready like the full z-wave library or home automation?

I would strongly recommend that you publish a Feature/Bug-Fix road map with dates.
Fix major problems 1 have it tested and published before adding new code/devices/modifications.

[LGNilsson]

This is the last firmware, or at least, I'm expecting to be, based on the old drivers.
It's taken longer for us to integrate the new drivers than we expected based on a wide range of issues, most of them outside of our control, since we don't actually write the drivers.
I can only apologise for the continued delays here.

Please don't expect support for every single Z-Wave device out there, it's not going to happen. We're going to do our best to offer broad support, but there's going to be a limit.

As for the Hue, it was finished of by one of our new guys who's learning how to get to grips with the platform, so why not let him do something like this, rather than do nothing? We've actually had quite a lot of interest in Hue support, so even if you don't use it, plenty of our other backers have asked for it.

The two threads are two different things, but yes, I should've added the missing access point feature in the known issues list, is was my bad and I've added it now.

[mmalluck]

Please don't expect support for every single Z-Wave device out there, it's not going to happen. We're going to do our best to offer broad support, but there's going to be a limit.

Yeah, I can't see Securifi supporting the addition of devices forever. This stuff keeps changing.
Far off in the future, after this product gets built out, do you think there's a chance the source for some of these modules might be made available for the community to support?

The open source community has had a lot of success supporting routers in the past.

[LGNilsson]

What we need to do is to create something similar to Vera's UI for this so people can add support for sensors where we already have a UI in place.
We're also considering a more generic UI for "unsupported" device, but this is going to take some time.
The biggest challenge with this is that we have to create a UI for the LCD, the mobile apps, the cloud and the local web interface.
All of this takes time to do, but it's something we want to do long term, but as it requires some quite fundamental changes, it's not going to happen over night.

[superbilou]

I use the AP mode also and of course i can't use this firmware.

If you remove a feature when you add another feature , the final release will be a very long time.

For me, the "AP mode" work fine and i don't understand why you remove a feature (i know temporarily) which works when you add another feature ...

[LGNilsson]

It's still possible to enable it via the web UI if need be, but as it was causing problems for some users, we decided to remove it for the time being.

[avenger]

It's still possible to enable it via the web UI if need be, but as it was causing problems for some users, we decided to remove it for the time being.

So if I'm using AP mode at the moment and it works, I can upgrade without any problem?

[LGNilsson]

Yes, the AP mode won't be turned off if it's already in AP mode when you flash.

[fr0gpil0t]

Has anyone confirmed that installing R069 with AP already enabled keeps AP enabled. I'm struggling with the corruption issue - every Mac upgrade fails when connected to the AP (I assume as data is being corrupted).


Robert

[Roger]

I am lost here. I am using Almond+ as an AP.

Can I or can't I upgrade to this version ?

Another subject. I already posted about the creation of dummy directories when using Sambda in Windows. Is this corrected in this version ? I want to connect my disks to teh router instead of to a PC in the network.

[sorphin]

As it says in the release notes that AP mode was temporarily disabled/removed/whatever in R069 release, which means, you can't use R069 if you use AP mode (like I do), and have to wait till the next release.

[Roger]

But Lars says: "Yes, the AP mode won't be turned off if it's already in AP mode when you flash" so it should work, right ?

Better not take any chance.

[fr0gpil0t]

  - want someone else to try this first before me !!!

[Shark69]

I'm no expert so details are vague but I use AP mode so I can access my printer. I upgraded and everything still works!
Scott

[LGNilsson]

You can still turn it on/off in the web UI, but due to some people seeing garbled packets, we decided to remove it for now from the LCD UI, but it'll be added back, no worries, we just need to address the issue first and we have a fix. The issue is that it's quite complex and time consuming to fix this issue, so we're going to release it alongside the new Wi-Fi drivers, as the two are sort of connected.