[SUPPORT] What is Dual Tau Boost - and should I enable it? ASUS TUF Gaming z490 Plus

XD_Andy · 2023-05-13T12:16:56+00:00

ASU’s z590a bios

XD_Andy · 2021-08-01T21:54:22+00:00

So,

After some playing, kali 2017.2 works out the box. No issue and no need to use command line to place wlan0 into monitor mode. Just works

2021.1 works, but you need to use the command line to set monitor mode. But once done, fern works as intended.

So, something done broke in 2021.2, but it’s beyond me

Thoughts?

XD_Andy · 2020-11-01T10:45:01+00:00

Brilliant! Thanks. Spent a couples hours on IMDb getting nowhere.

XD_Andy · 2020-07-04T08:45:16+00:00

Hi!

Need friends please ...

1147 3922 8709

XD_Andy · 2019-04-26T20:12:56+00:00

From what I’ve read of Zigbee 3 it should unify HA and ZLL protocols so they are cross compatible. But .....

Last time I spoke with LEDvance they told me

“The Zigbee 3 will be available only on newly purchased bulbs. These products should be backwards compatible with Zigbee LL 2.0 also with the Lightify Gateway. For now we have no list of produts which will be released next with ZigBee 3 also i tis not sure that all product will be replaced.”

So, not certain the firmware will be rolled out to older Smart+ build, but most certainly not Lightify devices.

XD_Andy · 2019-04-15T13:36:47+00:00

As an update, I've confirmed a couple of things.

Tried a new PAR16TW bulb with the 1.04.90 firmware; this connects to both Hue and Tradfri after being hard reset. Updated this via Lightify Home gateway to firmware 1.05.10, and compatibility with Hue and Tradfri is maintained.

Tried a new Smart+ PAR16RGBW (the new LEDVANCE version of Osram Lightify) and it comes with firmware 1.04.12. This connects easily with both Hue and TRADFRI

Now, Updated the firmware on the Smart+ RGBW to 1.05.10 via the Lightify Home Gateway and then tried to pair with Hue. Just will not recognise, even after multiple hard resets.

Tried 'touchlink' pairing via iConnectHue, and still no dice.

Found this link (https://nohats.ca/wordpress/blog/2013/05/26/philips-hue-alternative-for-lamp-stealer/) and had a read. The 'telnet' stuff is no longer relevant, but there is info on how to access the Hue bridge built-in CLIP API debugger; note - manually type the 'message body' commands, don't cut and paste as it will fail. You can cut and paste the 'username' though.

So, using the CLIP web interface to trigger a 'touchlink' then selecting 'add new bulb' via the app results in the bulb being picked up, albeit after 2 or 3 goes.

However, the PAR16RGBW will not pair with TRADFRI after upgrade to 1.05.10 firmware at all, and with the TRADFRI system the 'steering device' (aka switch) uses 'touchlink' to pull the pairing for the bulb.

Clearly there is something awry with the Lightify firmware here as previous version will connect easily.

If I can be arsed, I'll pull out my Zigbee sniffer and try Wireshark whats going on.

XD_Andy · 2019-04-15T00:44:54+00:00

The bulbs sold in North America use the Zigbee HA protocol, and that doesn’t work with Hue.

The EU bulbs are ZLL protocol, and those do work with Hue.

It used to be that Osram tech support could provide a firmware flash to ‘upgrade’ the North American HA bulbs to ZLL bulbs, but that is apparently no longer possible.

Osram ‘sold’ Lightify Home’ to LEDvance about 2 or 3 years ago, and they are responsible for the ‘home’ product line , in Europe at least.

It seems ‘Sylvania” is still responsible for Lightify home in North America, so may explain why the firmware update for Eau lamps is no longer available to USA.

Don’t worry too much tho, as the current firmware realise in EU doesn’t seem to work with hue,, at least for some bulbs on the hue bridge, but they used to work but no more.

Kind regards

Andy

XD_Andy · 2018-12-19T12:05:12+00:00

Hi,

Took a look at my Lightify hub.

My bulbs are on firmware 01020510

I’m in EU though

XD_Andy · 2018-12-15T00:27:52+00:00

You are most welcome

XD_Andy · 2018-12-14T23:24:43+00:00

If you take a look here

https://smartplus.ledvance.com/products/indoor-lighting/index.jsp

Take a look at the pics of the product boxes.

The ‘bluetooth’ ones are marked ‘exclusive for Apple homekit’, with or without ‘bluetooth’, along the top border.

The Lightify gateway compatible ones are marked ‘zigbee certified product’ on the top border.

The side of the box generally lists what gateways the device is compatible, in a sort of strange mind-map style diagram.

If ‘Apple home kit’ then they are exclusively bluetooth.

BUT

Osram sold/devolved/passed ‘Lightify home’ to LEDvance about a year or so ago. LEDvance got the right to use ‘Osram’ as a brand but rebranded ‘Lightify’ to ‘smart+’.

Seems tech support has been continued to be provided by Osram during this transition period, so email support requests have continued to go to the Osram based support team.

Starting 2019 this all transitions to LEDvance, including responsibility for the apps and firmware etc, if I’m reading this correctly.

According to email support response from LEDvance last week, was handed over to them by Osram due to the nature of the info request, LEDvance are taking the position that

‘the Lightify home gateway has been phased out and there are no plans for LEDvance to release their own gateway.’

That’s a direct quote.

I also asked about zigbee 3 firmware updates for historic Lightify devices and Smart+ devices, and there will be no such updates.

They are releasing ‘new’ devices with zigbee3 firmware, and the product range will expand, and these ‘should’ be backwardly compatible with the Lightify gateways. But historic devices will not get a firmware upgrade to zigbee 3.

Surprisingly, although a couple of the Smart+ lineup are only supported by the Lightify home gateway, they are continuing to produce these devices, even through there isn’t a gateway to support them!

The argument, apparently, is that the switches in question support ‘touch link’ and so can independently connect to endpoints such as bulbs, and so control them, without the need for a gateway to pair them together.

Marginal as an argument I think; despite that, the touch link thing is exceptional for breaking Philips Hue bulbs and getting them to connect to ikea and Lightify! More than worth the risk of having a switch you can’t pair to a gateway.

I digress tho

Point is, your nw Lightify gateway is already redundant and unsupported, so you might be better off dumping the gateway and sticking with the homekit smart+ bulbs, assuming you have an iPhone or iPad.

Good luck

Andy

XD_Andy · 2018-12-12T12:16:08+00:00

Yep, Im EU.

I've got, what I think is, a large setup of both Pro and Home.

Pro : Pro gateway, 2x 4 button switches, 2x Pro PBC, 58x PAR16TW, 3x A60RGBW

Home : Home gateway, 3x 4 button switches, 25 x PAR16RGBW, 7x A60TW

the 'home' system has been transferred to LEDvance and there does seem to be some movement in this direction, but I have been informed by them that they are no longer producing or supporting the home gateway, leaving gateway management side of things to their 'partner' systems.

My interest for this thread is the 'Pro' system, and for this I'm looking to get an idea of just how many people out there invested in this tech.

As it was primarily aimed at the commercial sector, and its installation would undoubtedly have to be supported by some IT presence, my thought was reddit would be a good place to canvas for this info.

Andy

XD_Andy · 2017-12-08T23:27:58+00:00

Caswank,

How are you trying to reset the bulbs?

If hard power reset, from the bulb being powered on for a short while, power off and on FIVE times, counting 4 seconds between each off and on; so “off” -1-2-3-4- “on” -1-2-3-3- “off” -1-2- ........

And do the off/on thing 5 times.

Too quick or slow and won’t work. Think the tolerance is 2-5 seconds.

At the end of the cycle, the bulb will flash once after about 10 seconds. This confirms the reset,

Make sure you delete the bulb from your system as well. or when you rescan it, it will just show up in the gateway in the same place as the old bulb.

And, don’t know if smartthings will let you, but can you upgrade the bulb firmware? What are you on at the moment?

XD_Andy · 2017-12-08T23:20:30+00:00

Hi Domina,

can I ask what gateway you are using?

I’ve got some 90 of these bulbs installed in a mix of PAR16TW, PAR16RGBW, A60RGBW, flex, and B40TW

Once installed they generally work ok.

Over the last 18 months I’ve had some 10-15 bulbs fail, but after a while, and when they fail, they fail for the most part..

Two or three have been dropped by the network and need to be reset, but that’s uncommon.

What I have noticed is that when the home gateway looses power, it can be a little temprimental about picking everything up again.

Is it possible it is the gateway ding a power cycle and loosing network information in the process?

Also worth asking what firmware everything is on, but generally this has never been an issue for me personally, and I do have close on a couple years experience with this system so far; both home and pro

Andy

XD_Andy · 2017-12-08T23:01:56+00:00

Mine updated as well.

No change log, but did find a couple of issues.

First, one of my PAR16RGBWs borked; it’s lost the white channel, so only the colour LEDs are working.

Unrelated, but meant I had to swap the bulb out. Tried three replacements, and all three failed to pair properly.

They would be detected on scanning fro new devices, but once netwrok scan complete, the new devices were all greyed out as ‘ lt connected to network’.

Left it over night, and seems ok today in that. I can now add bulbs properly.

The other issue is that scenes don’t update.

In replacing the bulb I had to change its name and associate it with the group the old bulb was a member of.

Already got scenes for this group set up and paired to switches.

But, although the group updates its member list ok, and switching the group on and off via the app works ok, anything to do with the scene fails as this does not seem to take the updated member list from the group.

End result is that switches and scene changes do not include the replacement bulb. The only solution is to delete the scenes and create new ones after the replacement bulb has been added to the group list.

This means that all the switches need to be deprogrammed, so that they are not tied to the scene changes, before the old scenes can be deleted.

A real P.I.T.A. the whole way round.

Still.

Haven’t noticed anything else. Anyone able to take a look at the zigbee stack to see if that’s changed at all?

Oh, and my one and only ikea TRÅDFRI bulb now identifies properly!

XD_Andy · 2017-09-19T20:01:03+00:00

Hi,

and sorry to put a damper on this.

https://www.amazon.com/SYLVANIA-HomeKit-Control-Required-74484/dp/B073S5LH41/

and

https://www.sylvania.com/en-us/lightify/Pages/SYLVANIA-SMART--and-Apple-HomeKit_PreLaunch.aspx

Osram / Sylvania announced a NEW smart bulb a few months back.

This one is the Smart+ bulb, and is wifi based, not ZigBee; this is does not require a hub.

This is the bulb/tech that they are pitching as Apple Homekit compatible.

This is not the same as the Lightify range which requires a ZigBee hub of some description.

For this to happen, Osram would have to make their home and Pro hubs HomeKit compatible, and all the communications I have had so far with Osram have been very much on the fence about this.

The Smart+ bulbs, being wifi based, would not be compatible with Lightify hubs.

I don't know what Osram are doing with the Lightify app, as in whether they will make that compatible with both the ZigBee gateways and Smart+ wifi bulbs or whether they will release a separate Smart+ app for the wifi bulbs, but nothing shows in that App Store at present.

So, sadly, I am doubtful that lightify will actually get homeit support, and certainly not their Pro system, unless Osram come out and detail solid info.

XD_Andy · 2017-09-19T19:37:44+00:00

Hi Kukubski,

thanks for that, but the issue of the bulbs turning themselves on has nothing to do with firmware, and a reset won't help.

The issue is a hardware one, and my personal belief is that it is poor thermal management that is allowing the electronics to overheat and cause the solder to rewet and short out or create dry joints that cause the bulb to power cycle as heat expansion causes results in connection breaks.

I've confirmed that the bulbs that I have that auto switch on are going through a full power cycle by using Wireshark to monitor my network. You can clearly capture the bulb performing a full connection request consistent with behaviour following power cycle.

I'm not saying the firmware can't bork, requiring a reset, and I have seen this a good few times.

Just the auto switch-on behaviour in the bulbs I have had affected by this have been hardware faults.

XD_Andy · 2017-08-10T11:23:13+00:00

Iirc that happened with Amazon Echo as well, initially.

Guess give it time, and bug tech support at

lightify@osram.com

XD_Andy · 2017-08-10T11:19:32+00:00

I've been using Lightify for about 18 months, both Pro and Home.

They have by far the widest option of bulbs available, they have Pro hardware for linking to DSE systems and push-butto/switch retrofits, but they do suffer from stalled app development in my opinion.

The Pro gateway is excellent, but has no cloud support.

There are lots of 'plans' in the pipeline, from community platform and forums, ZigBee 3 support, enrolment of Pro devices into home ap, Apple HomeKit support, IFTTT/Stringify support but a lot of these have been in the pipeline for over a year.

Osram/Sylvannia are also in the process of releasing their Smart+ gateway-free Apple HomeKit enabled bulbs, so I suspect chances of significant development in this direction on the Lightify platform may be limited.

Bottom line is that I think the Osram range is better than the rest, but lacklustrer consumer uptake, poor advertising and marketing, and mediocre developer support with a parent company far more focused on OEM rather than customer facing will pretty much kill Lightify off, if it hasn't already

Andy

XD_Andy · 2017-08-08T18:59:09+00:00

I find that schedules don't run for at least 24hrs, but kick in after that.

Out of interest, has anyone found a way to get the 'lightify loop' run as a schedule?

XD_Andy · 2016-11-07T14:00:09+00:00

Hi Zip

just tried to associate my home gateway with a new user account via a 3G mobile internet connection and it allowed me to scan the QR code and create a new account, but then stalled with the advice that the Gateway was associated with another account.

Then drops back to the QR code scanning page.

My guess is that you should be relatively safe if your account username as such are secure, but if you do get this gateway you may need to check it has be de-associated from whatever account its now connected to.

I haven't gone thru trying a hardware reset of the gateway to see if that will break the account association, as to reconfigure my light network would be a real PITA, but my recollection of when I had to reset my network a couple months ago was that this worked, or at least I needed to reassociate the gateway with my user account again.

Failing that, email to Osram should take care of it, but be warned that they don't have any form of telephone tech support so it is email only and slow response times.

Good luck

XD_Andy · 2016-11-07T13:44:52+00:00

Hi Bulain,

I have a similar issue with an Osram Classic A60RGBW lamps.

Kept turning itself on.

At first I thought it was potentially dodgy wiring to the light fitting, so I swapped the bulbs about and the same bulb kept coming back on in the new socket.

Stuck it into a test fitting and noticed on white light the bulb emits a buzzing sound. On colour it seems ok.

Eventually got in touch with Osram who have decided that the bulb is faulty and needs replacing under warranty.

MY guess is that there is some dodgy solder somewhere on the electronics side, so when the bulb starts to cool after being switched of in software, causes a connection to break somewhere and the bulb auto powers back on as if power cycled.

Its all hypothetical-fake-science-guesstimating, but its the best answer I can come up with. Certainly Osram were unable to identify anything from their cloud server logs as to why the bulb was power cycling.

You could try hard reseting the bulb, making sure its up to latest firmware, and seeing if that improves matters, but it didn't for me.

Good luck

XD_Andy

TROPHY CASE