R80 Multi Level On/Off Issues - Lights/Dimmable Bulbs

[SecureComp]

R80 is out.
It is an improvement.
There are still a few loose ends to tie up.

GE Link A19 bulbs are working and report correctly both Status (On/Off) and Dimmer % in Web Interface, IOS App. The Android App correctly reports Status (On/Off) and whether the lamp is "Dimmable" but not the %.

CREE Connected bulbs are not reporting to the Apps or Web Interface correctly.

Web App - reports NaN%

IOS App - On/Off status OK - Dim% always reports as 0%
Android App - On/Off status OK - Dim % always reports as 0%

I have powered the lights on and off manually.
I have not re-Paired any of the CREE bulbs.

[SecureComp]

Logs have been sent as "cree bulbs r80"

Will try a router reboot and remove sensor then re-Pairing a CREE bulb to see if it helps

[BFH]

I tried and it still doesn't work. What a joke.

[SecureComp]

I tried and it still doesn't work. What a joke.

What doesn't work exactly? A specific bulb or sensor?

Understand it might be frustrating, but need specific info to move forward.

The Firmware Update worked smoothly, nothing broken so far.
The GE Link bulbs are working well for me, the CREEs not so much.

[BFH]

Cree CRC285 Connected Soft White 60 watt replacement. It actually works worse with the latest update.

[SecureComp]

Yep, I have the Crees as well.
Wouldn't say they work worse imho.

What happens is that they report a 0% dim after every sensor refresh. And there is still the NaN% thing.

I'm not at home, so can't double check stuff right now but will be doing a delete/re-Pair and check stuff out.

It will get straightened out, the GE Link bulbs were fixed, Crees will be too and soon I expect.

All of my Rules with the Crees still work, have set them using Dim percentages instead of straight on/off.

[jnowland]

After updating to R76 and experiencing the issues with my GE bulbs, I had removed them and attempted to re-connect them with my A+.  At that time I did get one to re-connect, albeit with the issues several others reported.  After installing R80, the "issues" seem to be fixed with the GE bulbs however, I can't seem to get my 2nd bulb to connect to my A+.  Is there a known defect with the GE Bulbs, or something else I need to do to pait it with my A+, other then turning on the light?

[Ohiomedic]

After updating to R76 and experiencing the issues with my GE bulbs, I had removed them and attempted to re-connect them with my A+.  At that time I did get one to re-connect, albeit with the issues several others reported.  After installing R80, the "issues" seem to be fixed with the GE bulbs however, I can't seem to get my 2nd bulb to connect to my A+.  Is there a known defect with the GE Bulbs, or something else I need to do to pait it with my A+, other then turning on the light?

You might need to reset the bulb.

Turn off the light
and wait 3 seconds. Turn on the light and wait 3 seconds. Repeat turning the
light off and on (approximately 5 times) until the bulb flashes once. As soon as it
flashes once, it is reset.

[rldreams]

I tried and it still doesn't work. What a joke.

Agreed

 I was optimistically hopeful when I saw and installed 080 last night. I didn't bother playing with it, since it was 2am ,and I was on my way to bed.  I came down this morning thinking all my rules would be working again. I look out the window to see the outside lights that are supposed to shut off at 6 are still shining full brightness, even though they are set by rule to 5% at night and according to the led are off.
 Even though release notes say nothing in WiFi or router was touched. I can connect to 5ghz , but have no internet access. So I had the fun task of going around the house and switching all my devices that have 5g over to the 2.4 side so they are actually online.

[SecureComp]

I have a dozen devices connected to both 2.4 and 5 Ghz, nothing dropped with the upgrade to R80.

Which bulbs were not working for your rule set?

The R80 upgrade does perform a router reboot. Perhaps your devices did not reconnect after reboot?

[Ohiomedic]

All my stuff reconnected, and haven't dropped after upgrading to R80. I did have to reset the day and time though, which was making my night rules fire during the day.

[rldreams]

Did not need to reset the TZ with 080. Looking back, having to reset TZ from UTC after every update was actually a minor inconvenience .
Outside and night lights were off this morning, so I am assuming that those rules are now working. Still no control via app any attempt just hangs on "updating sensor data. Please wait" until it times out. Controlling VIA LCD works, but is still not reporting the proper state. If I hit the slider at 50%, light will come on at 50%, but still show as off or on 0% . LAN web UI still read as NaN% .
 On connect.securifi I can turn lights on/off but slider will not move. After triggering a few on off cycles via connect.securifi it did start showing proper on/off state if not the correct bright/dim level.
 Schlage lock with has been working fine since 070 was stuck showing unlocked on LAN web UI, connect.securifi and app, but showing properly and working with LCD. I triggered a unlock/lock cycle a few times via LCD and it is now reporting properly and working across all.


 I am sitting here now modem is 3 feet to my right and A+ is 3 feet to my left. Everything is green/ blue respectively on modem , yet with the status screen up on A+ I have seen it disconnect /reconnect to internet 3 times in 15 minutes.  So maybe it was not just losing 5G , but completely disconnecting from internet and in the time it took me to switch networks it had reconnected.

 
 Logs show A+ uptime as 1 day 9 hours, which corresponds with when I installed 080. I have watched it cycle through the start up splash screen at least twice since then, but obviously whatever it is doing, it is not doing a full reboot.
 I am no where close to being as smart as I once was, so actually deciphering the logs is beyond my abilities. It looks to me like A+ keeps reassigning/changing LAN IP addresses.

 Jun 10 10:39:07 AlmondPlus user.info sysinit: RECV V2 member report   from 192.168.1.1     to 224.0.0.2
Jun 10 10:39:07 AlmondPlus user.info sysinit: Mebership report was recieved on the upstream interface. Ignoring.
Jun 10 10:39:10 AlmondPlus user.info sysinit: Removing MFC: 192.168.1.1 -> 239.255.255.250, InpVIf: 0
Jun 10 10:39:10 AlmondPlus user.info sysinit: MRT_DEL_MFC; Errno(2): No such file or directory
Jun 10 10:39:20 AlmondPlus user.info sysinit: Inserted route table entry for 239.255.255.250 on VIF #-1
Jun 10 10:39:20 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.111 to 192.168.1.135
Jun 10 10:39:21 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.135 to 192.168.1.136
Jun 10 10:39:23 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.136 to 192.168.1.44
Jun 10 10:39:40 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.44 to 192.168.1.111
Jun 10 10:39:42 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.111 to 192.168.1.135
Jun 10 10:39:42 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.135 to 192.168.1.136
Jun 10 10:39:44 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.136 to 192.168.1.44
Jun 10 10:40:00 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.44 to 192.168.1.111
Jun 10 10:40:02 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Jun 10 10:40:02 AlmondPlus user.info sysinit: Svc Disc: Starting discovery for cluster 0x0019^M
Jun 10 10:40:02 AlmondPlus user.info sysinit: Svc Disc: Waiting 2 sec for discovery to complete^M
Jun 10 10:40:03 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.111 to 192.168.1.135
Jun 10 10:40:03 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.135 to 192.168.1.136
Jun 10 10:40:04 AlmondPlus user.info sysinit: Svc Disc: complete.^M
Jun 10 10:40:04 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Jun 10 10:40:05 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.136 to 192.168.1.44
Jun 10 10:40:20 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.44 to 192.168.1.111
Jun 10 10:40:24 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.111 to 192.168.1.135
Jun 10 10:40:24 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.135 to 192.168.1.136
Jun 10 10:40:26 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.136 to 192.168.1.44


Since a good number of my LAN devices are set with static IPs and I have DHCP set to issue 30 day /720 hour leases  IP addresses should not be changing.
 Just as I was getting ready to hit send it disconnected again, which coincided with the wife turning on the TV ( ?!!!!!)

Jun 10 10:59:52 AlmondPlus user.info sysinit: Mebership report was recieved on the upstream interface. Ignoring.
Jun 10 10:59:52 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.135 to 192.168.1.111
Jun 10 11:00:01 AlmondPlus user.info sysinit: Removing MFC: 192.168.1.111 -> 239.255.255.250, InpVIf: 0
Jun 10 11:00:01 AlmondPlus user.info sysinit: MRT_DEL_MFC; Errno(2): No such file or directory
Jun 10 11:00:01 AlmondPlus user.info sysinit: Inserted route table entry for 239.255.255.250 on VIF #-1
Jun 10 11:00:04 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.136 to 192.168.1.44
Jun 10 11:00:04 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.44 to 192.168.1.135
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:13 AlmondPlus user.info sysinit: Request failed:
Jun 10 11:00:13 AlmondPlus user.info sysinit: Error
Jun 10 11:00:20 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.135 to 192.168.1.111
Jun 10 11:00:22 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.111 to 192.168.1.136
Jun 10 11:00:22 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.136 to 192.168.1.44
Jun 10 11:00:25 AlmondPlus user.info sysinit: The origin for route 239.255.255.250 changed from 192.168.1.44 to 192.168.1.135
Jun 10 11:00:34 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Jun 10 11:00:34 AlmondPlus user.info sysinit: Svc Disc: Starting discovery for cluster 0x0019^M
Jun 10 11:00:34 AlmondPlus user.info sysinit: Svc Disc: Waiting 2 sec for discovery to complete^M

I sent in logs via lcd labeled " losing wan connection"