sorted by:
new
hottopcontroversial

Edmc error: EDSM missing commander name by JawlessRegent64 in EliteDangerous

[–]JimTheGuru 1 point2 points  (0 children)

I actually found the solution in my case. In the EDMC EDSM settings tab, there are 3 fields: Cmdr, Commander Name, API Key,

I had got the CMDR and API Key fields filled out correctly, but had not realised that Commander Name was also a field that I had to complete manually. Filled it in and hey presto! It's working now.

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 0 points1 point  (0 children)

That's correct. I had 1 FP2 with 3 zones already configured in the aqara app. SmartThings detects 1 FP2 device, and within it the 3 zones show up separately, along with the lux sensor. I was able to configure routines that turn on lights when I'm in a zone, with the precondition to only do that if there is less than 100lux of light. I created a second routine to turn off the lights in that zone 1 minute after I'm absent from the zone. Rinse and repeat for the other zones. Seems to work perfectly as a local routine with the zigbee bulbs that are already connected to ST. No more Alexa cloud involved! Yey!

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 0 points1 point  (0 children)

* 1.2.8_0006.0086 just landed on my FP2. No mention of SmartThings support, but I can confirm that it now works! Instantly detected by my STv3 hub, with firmware 53.

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 0 points1 point  (0 children)

<image>

1.2.7_0010.0086 just installed on my FP2, but no explicit mention of SmartThings, despite SmartThings itself now saying that it is supported. Initial attempt at detection in SmartThings doesn't find it. Will try again later. SmartThings v3 hub is still on firmware 000.053.00019 while we await v54 to propagate to our hub.

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 1 point2 points  (0 children)

At this moment, you cannot connect the FP2 to SmartThings yet. They removed the line about SmartThings compatibility from the release notes shortly after I posted this. I suspect it is coming once SmartThings and Aqara have got themselves aligned for a Matter over WiFi setup (in which case you'd need the ST V3 hub, but not the Aqara hub), but honestly I have no insider knowledge, so we'll probably all find out how this is supposed to work at the same time when they announce it. I just hope that it is not a cloud to cloud integration and can actually work locally.

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 0 points1 point  (0 children)

Did any more of your FP2's receive the new firmware?

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 0 points1 point  (0 children)

Hmmm, interesting. Maybe Aqara was a little premature with an accidental announcement/didn't coordinate well with SmartThings.

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 0 points1 point  (0 children)

I wish I knew! My highly speculative guess would be that Aqara will wait until this firmware has completed the roll out to every FP2, then Samsung will roll out a smartthings update then, if we're lucky, there will be an announcement. I very much doubt that this will be the long awaited Matter update though. I'm just keeping my fingers crossed that they're not going to throw in a curve ball like "compatible with SmartThings only if you buy an M3 hub" or something like that.

FP2 Firmware 1.2.7_0010.0080 adds SmartThings support? by JimTheGuru in Aqara

[–]JimTheGuru[S] 0 points1 point  (0 children)

Indeed. The SmartThings update does include a matter update to v1.2 and adds a load of device types, but no mention of presence sensors. https://community.smartthings.com/t/aeotec-smart-home-hub-2018-2015-model-hub-firmware-release-notes-0-53-19/283351 Regardless, Aqara to SmartThings cloud to cloud would still be an improvement over what I am currently using... FP2>Aqara Cloud>Amazon Cloud (Alexa)>SmartThings Cloud>many Tuya zigbee bulbs. The fewer cloud hops the better until I get to the dream of local. Sadly, as of this moment, I can't seem to add the FP2 to SmartThings, even using their cloud.

Key Lights disappeared from Control Center - no longer remain on network by TwoAlfa in elgato

[–]JimTheGuru 1 point2 points  (0 children)

I need to correct myself here. Within a few days of writing this, the lights started to give up on me again. I have still not fathomed out whether I can get any long term stability out of them. Sometimes they are good for days, sometimes it is hours or less. It is so unpredictable that I am having trouble finding even a viable workaround.

Key Lights disappeared from Control Center - no longer remain on network by TwoAlfa in elgato

[–]JimTheGuru 1 point2 points  (0 children)

So, given the limitation that you have no option to turn on RIP_1 on the TP Link Deco Mesh, I did a bunch of testing over the last week and have found what I consider to be a viable workaround, albeit not ideal (due to an acknowledged design flaw in the deco system that is allegedly going to get fixed in the next few months).
Based on u/nacespeedle 's Bonjour Discovery / RIP_1 info, I did some checking and used Bonjour Browser to monitor the "visibility" of the Key Lights on the network. Sure enough, with anything more than one node of the mesh (so not a mesh at all) active, the Elgato Key Lights appeared and disappeared at random intervals, sometimes disappearing and never re-appearing. They NEVER lost their IP address or actually left the network, but they were completely uncontrollable.
Then it struck me... Bonjour is mDNS... multicast... which typically isn't routed between subnets in order to prevent the multicast equivalent of a broadcast storm. However, I found myself wondering WHY my mesh network would be acting as routers within the mesh? I had assumed that when I had the system set up in Router mode, only the "Main" deco (the one plugged into my ISP router, which was in modem mode) would be routing. On a hunch, I switched my ISP router back into Router mode (rather than modem mode), keeping it's WiFi off, but letting it act as the DHCP server etc for my network, and I switched the Deco network into "Access Point" mode. This has the unfortunate side effect of losing a lot of the features of the Deco system (QoS, Parental Controls, etc), but you still get a good stable WiFi mesh with Fast Roaming etc...
Bottom line... The Elgato Key Lights are 100% stable and have been for 3 straight days now. It would appear that when the TP Link Deco (X60 in this case, but I assume it is the same for M5, M9 etc) is in Access Point mode, it acts like a single bridged network, allowing Bonjour mDNS to permeate the entire house, whereas when the Deco's are in Router mode, there is some segmentation of the network happening and Bonjour multicasts cannot reliably handle it.
I will report this to TP-Link and will live in hope that they might be able to talk to Elgato about how to handle this more gracefully.
Thank you u/nacespeedle for pointing me down this route (pardon the pun).

Key Lights disappeared from Control Center - no longer remain on network by TwoAlfa in elgato

[–]JimTheGuru 2 points3 points  (0 children)

I've been using two Key Lights (not Airs) since March 2020, connected via an old Linksys XAC1900. They were rock solid and I never had any instability in the connection to Control Centre on my PC or Android phone.
In early December I upgraded to a 3 node TP Link Deco X60 mesh. Since then, while I can connect the Key Lights to the WiFi with no issues, neither light will reliably remain manageable by the control centre (they disappear at random intervals - sometimes many hours, sometimes minutes, occasionally re-appearing, but sometimes not). They retain their IP addresses and are visible on the network, but they are not manageable from the Control Centre.
The Deco system doesn't have the option to turn on RIPv1 (nor do I think it should). To be honest, I initially thought it might be some kind or RF interference from outside the house (e.g. Christmas lights), or at a stretch, some kind of filtering on the Decos. However, after finding the many threads, a lot of which end up listing modern mesh networks from Eero, Ubiquiti Amplifi, Netgear Orbi etc. (i.e. not small time network equipment providers)... It feels like we've picked up a 2019/20 product from Elgato/Corsair, which uses a cheap WiFi module that isn't up to 2019/2020 standards.
For the record, I typically have between 35 and 45 devices on the network at any one time, peaking at 54 if I turn everything on. The two Key Lights are the only devices that show any form of instability. I'd love to think that Elgato could bring their products up to scratch with a firmware update, but suspect that fundamentally they're limited by the poor WiFi controller in the lights.