Firmware R80 is out

[Ashok]

You can now upgrade the Almond+ to firmware R080. This is a minor release based on R076, which has fixes regarding GE Link bulbs and Multi level switch.

Note: Please note that we can upgrade this firmware via LCD only from R70 and beyond, anything less than that has to be done manually. Any user who has R69 and below version could  download and update the software manually via Web UI by going to (http://www.securifi.com/software-update) and select Almond+.
 
Router Features:
N/A

Rules UI:
N/A

Firmware ZigBee:
Multilevelonoff index issues.
Peanut plug updating values issue

Firmware Z-Wave:
Fixed xml issue for Heatit setpoint thermostat.
Fixed xml issue Aeotec flood sensor (DSB45-ZWUS).

LCD UI:
Fixed bug with unlink button in Almond Account lcd app.
Fixed issue in adding Hue bulbs.

Local Web UI:
N/A

Web App/Mobile Apps:
N/A

Other:
Changed launch script to launch language app before wizard.

[Fire69]

Should I upgrade from the pre-release R080? Or are they basically the same firmware?
Their seem to have been extra changes to Zigbee and Z-Wave.

[Ashok]

@ Fire69,

It is the same, the release notes has the changes of R79 also.

[obmd1]

No change in:

Flood sensor reporting inversion (iOS only, not on connect site, or web UI)
Multi sensor now "unsupported" (first in R076)

[SecureComp]

No change in:

Flood sensor reporting inversion (iOS only, not on connect site, or web UI)
Multi sensor now "unsupported" (first in R076)

I feel an IOS App update coming on. Several sensor have inverted status reporting.

[Ohiomedic]

No change in:

Flood sensor reporting inversion (iOS only, not on connect site, or web UI)
Multi sensor now "unsupported" (first in R076)

Its an iOS app issue, which has been stated to be fixed in the next release.

[aurel]

Hi,

When will we have a wifi which is working well ?

[obmd1]

Come home today to a random loss of wifi connectivity. LCD status states all normal, but all connected devices were offline. LAN connectivity was intact.

Please take note. This instability is new in R80, as I have not ever had a loss of connectivity with previous firmware.

[praeluceo]

A quick note that I just retested my CT30e thermostat under R80 and the device still fails to pair successfully. The thermostat transitions into the "LINK" state, the Almond+ says it's pairing, the Almond+ gets to the "Getting sensor info, please wait..." popup, but then after about 20 seconds dies with an "Association Failed" error, just like on previous firmwares. The relevant logs are here:

root@AlmondPlus:/tmp# cat zigbee_server.log:

[2015-6-15 22:58:35.940089447]   {INFO}  Received Command
[2015-6-15 22:58:35.940300189]   {INFO}  option button1
[2015-6-15 22:58:35.946041066]   {INFO}  command started to process
[2015-6-15 22:58:36.207129904]   {INFO}  processed command
[2015-6-15 22:58:36.227923446]   {INFO}  pJoin for 60 sec: 0x0
[2015-6-15 22:58:36.782550887]   {INFO}  emberAfTrustCenterJoinCallback
[2015-6-15 22:58:36.788472398]   {INFO}  pJoin for 0 sec: 0x0
[2015-6-15 22:58:36.803462846]   {INFO}  Sent ASSOC_DEVICE_JOINED Packet Successfully to association
[2015-6-15 22:58:36.803722956]   {INFO}  Device status = UNsecured join shortid 0x3671
[2015-6-15 22:58:36.832518634]   {INFO}  emberAfPreMessageReceivedCallback 3671  and cluster 0x13
[2015-6-15 22:58:37.217871621]   {INFO}  emberAfPreMessageReceivedCallback 3671  and cluster 0x500
[2015-6-15 22:58:37.245293732]   {INFO}  emberAfPreMessageReceivedCallback 3671  and cluster 0x500
[2015-6-15 22:58:38.262442156]   {INFO}  emberAfTrustCenterJoinCallback
[2015-6-15 22:58:38.262785302]   {INFO}  Sent ASSOC_DEVICE_LEFT Packet Successfully to haserver
[2015-6-15 22:58:38.262955228]   {INFO}  Device status = device left shortid 0x3671
[2015-6-15 22:58:38.273428065]   {INFO}  emberAfBasicClusterClientTickCallback
[2015-6-15 22:58:38.273684675]   {WARN}  state ASSOC_FAILURE
[2015-6-15 22:58:38.273965746]   {INFO}  sent ASSOC_FAILURE packet to association
[2015-6-15 22:58:38.274140072]   {INFO}  emberAfBasicClusterServerTickCallback
[2015-6-15 22:58:58.002457475]   {INFO}  Received Command
[2015-6-15 22:58:58.002614440]   {INFO}  option button1
[2015-6-15 22:58:58.005722938]   {INFO}  command started to process
[2015-6-15 22:58:58.005885624]   {INFO}  processed command
[2015-6-15 22:58:58.025676193]   {INFO}  pJoin for 60 sec: 0x0
[2015-6-15 22:58:59.792797851]   {INFO}  emberAfTrustCenterJoinCallback
[2015-6-15 22:58:59.798060930]   {INFO}  pJoin for 0 sec: 0x0
[2015-6-15 22:58:59.813487867]   {INFO}  Sent ASSOC_DEVICE_JOINED Packet Successfully to association
[2015-6-15 22:58:59.814246903]   {INFO}  Device status = UNsecured join shortid 0xc4e
[2015-6-15 22:58:59.822395663]   {INFO}  emberAfPreMessageReceivedCallback c4e  and cluster 0x13
[2015-6-15 22:59:7.892479202]    {INFO}  emberAfPreMessageReceivedCallback  0  and cluster 0x8038
[2015-6-15 22:59:14.202909198]   {INFO}  emberAfPreMessageReceivedCallback  0  and cluster 0x8006
[2015-6-15 22:59:30.304896482]   {INFO}  emberAfBasicClusterClientTickCallback
[2015-6-15 22:59:30.305164152]   {INFO}  state ASSOC_DEVICE_JOINED
[2015-6-15 22:59:30.313667833]   {INFO}  Reading Manufacturer Name
[2015-6-15 22:59:30.313929383]   {INFO}  Sent Packet ASSOC_PROCESSING successfully to associaton
[2015-6-15 22:59:50.784715262]   {INFO}  emberAfBasicClusterClientTickCallback
[2015-6-15 22:59:50.795129708]   {INFO}  emberAfBasicClusterClientTickCallback
[2015-6-15 22:59:50.795288901]   {WARN}  state ASSOC_FAILURE
[2015-6-15 22:59:50.795480461]   {INFO}  sent ASSOC_FAILURE packet to association
[2015-6-15 22:59:50.795607313]   {INFO}  emberAfBasicClusterServerTickCallback

root@AlmondPlus:/almond/log# cat LastFailedZwaveServer.log:

[2015-6-15 22:58:36.257131771]   {PRINT}         Received Operation Code:Code_ControllerCommandOperation
[2015-6-15 22:58:36.257374340]   {PRINT}         Received ControllerCommandOperation:ControllerCommand_AddDevice
[2015-6-15 22:58:36.282395855]   {PRINT}         Driver:sending SoftReset to controller for ADD/REMOVE Device
[2015-6-15 22:58:36.282595549]   {PRINT}         Queuing (Controller) Add Device
[2015-6-15 22:58:36.799090740]   {PRINT}         Received Operation Code:Code_CancelCommandOperation
[2015-6-15 22:58:36.799295308]   {PRINT}         Cancel Add Node
[2015-6-15 22:58:37.324051882]   {WARN}  Driver:Out of frame flow! (0xe0).  Sending NAK.
[2015-6-15 22:58:38.388463311]   {PRINT}         Not Sending Node 255 Type_Notification(26) notification to haserver
[2015-6-15 22:58:38.565805523]   {PRINT}         Node add done status received
[2015-6-15 22:58:57.999654062]   {PRINT}         Received Operation Code:Code_ControllerCommandOperation
[2015-6-15 22:58:57.999808395]   {PRINT}         Received ControllerCommandOperation:ControllerCommand_AddDevice
[2015-6-15 22:58:58.024181817]   {PRINT}         Driver:sending SoftReset to controller for ADD/REMOVE Device
[2015-6-15 22:58:58.024397005]   {PRINT}         Queuing (Controller) Add Device
[2015-6-15 22:58:59.112592660]   {PRINT}         Not Sending Node 255 Type_Notification(26) notification to haserver
[2015-6-15 22:58:59.123210525]   {WARN}  Driver:Out of frame flow! (0xe0).  Sending NAK.
[2015-6-15 22:58:59.812378272]   {PRINT}         Received Operation Code:Code_CancelCommandOperation
[2015-6-15 22:58:59.812594200]   {PRINT}         Cancel Add Node
[2015-6-15 22:59:0.167854057]    {PRINT}         Driver:Removing Msg from Node 255 attempts:3
[2015-6-15 22:59:0.189747211]    {PRINT}         Not Sending Node 255 Type_Notification(26) notification to haserver
[2015-6-15 22:59:0.368518009]    {PRINT}         Driver:Removing Msg from Node 255 attempts:6

Additionally, for the first time I tried hooking up a USB hard drive to the USB port on the Almond+. The network attached drive is available via SMB or FTP (it'd be nice to have the NFS package installed as well) over the Almond+'s own DHCP network (WAN side), but not via the LAN side. It'd be nice if shared drives could be accessible via both sides of the network, as it stands, it looks like in order for me to access my USB hard drive via my wired network, I'll have to disable the Almond+ DHCP server and put everything on the same subnet.

Also, the version of nfsutils on the Almond+ does not support nfs v3 (mount -t nfs -o nfsvers=3), so I can't mount my existing NFS shares on the Almond+, which was going to be my workaround.

[SecureComp]

Moderator should move these "issue" posts to the issue thread and leave this as announcement thread.

[obmd1]

I think worrying about where these posts are is far less important than the fact that there is zero response from software people.

[SecureComp]

I think worrying about where these posts are is far less important than the fact that there is zero response from software people.

Agreed, but not even a moderator working the forums to keep thing organized is unfortunate.

This thread announced a firmware release, there is another thread for tracking issues with the R80 release. In the other threads describing problems, there are responses from Ashok.

[Ashok]

@ All,

Me (Ashok) and my colleague (Amrit) are handling the forums now, we both have Admin rights. Most of the cases I would be posting about the new firmware release.

I am locking this topic now and any user who has issues, please post it here http://forum.securifi.com/index.php/topic,3394.0.html.

@ obmd1 and aurel you two are the only users having issues with wireless, hence, please send an email to our support team support@securifi.com, I would make sure it is taken care off.

@ praeluceo,

I may have to get back to you after checking with our team.