@RobertD502 – thank you!! I can’t wait to try this out!
I have a WLED-managed LED on my desk (hooked to an ESP8266). Next to my keyboard is a Zigbee button that I press once to turn the LED red when a call starts, twice to turn it green at the end of the call, and press-and-hold to turn it off at the end of the day.
Last Friday I added a second WLED-driven LED, in a tiny case tucked into a gap behind the living room couch outside my office door. Anyone can see it the whole length of the house. That way they don’t even have to come into my office and suddenly appear in the background of my call!
That would be great, as I was trying to get my wife’s machine to use that except her workplace has locked down devices.
I have the API key set up, and the network is set to be private, but I get an unexpected error trying to connect.
The other issue could be (and possibly the same issue with @Eldudemeister) is I’ve already set up a machine (mine) - so is it possible the integration can’t set up a second machine (which just happens to be the locked down one)?
I managed to set up more than one instance so not sure if that’s the case. I installed on Mac and windows…albeit windows was my personal laptop not work so worked fine…
I was hoping to get the integration by @malkstar working, but like others here I have a very locked down machine and I get an unexpected error when trying to configure. Even if I could get around the firewall issue, I often have to be on a VPN which shuts down any access from my work machine to my LAN, so would be a showstopper.
I think the only way would be from the machine running Teams to call the websocket API locally and push something to Home Assistant (perhaps with a webhook). I can’t install anything or even run any .exe that hasn’t been whitelisted, but maybe something could be done in powershell? I’m not a dev so looking into implementing something is unfortunately beyond my capabilities.
Thanks all for the work. I’ve tried all of these solutions, but it appears that my work laptop is just too locked down as found be others above.
The local websockets looked the most promising as I can’t run any scripts in PowerShell.
Such a shame that something as simple as presence is so restricted by work admin.
I had a thought of trying to use the presence of my work profile via my home profile as I have a desktop running 24/7 anyway, but I wouldn’t know how to implement this.
You don’t need to be an admin to create your own app registrations, and as it uses delegated auth, the scope approval is done at your account level instead.
I used to have my own script to update a sensor, which started via task scheduler but despite trying to take precautions, it ended up being quite unstable, and the task ending without realizing.
Unfortunately I don’t have permissions in my company tenant to create app registrations with GUI. It gives an error message stating it would be possible by PowerShell, but i’m pretty much lost there. Installed the AzureAD module but after that, I honestly don’t know what i’m doing. By any chance someone has an idea on how to create an AppReg for this?
Hey @fbradyirl I’ve just found this PR #44331 which got closed and new one was opened under PR #45213 - Add Webex presence sensor.
I see the new one is also closed but it seemed like it was mostly finished? Any possibility to revive this again?
The GUI makes it really easy to setup.
I’m using the Teams Websockets integration, I have 4 computers (2 Macs and 2 PCs) and it seems to be working great on the macs, but I get the ‘unexpected error’ trying to set up the PCs. This sounds similar to many of the other posts.
Was there any resolution to this? I mostly connect to meetings on my Mac, and join the PC if i need to share my PC screen, but I’d like to get this working on all 4 computers independently if possible.
Hello, just saw something new? I don’t know if it was already posted in this thread but I’ll put it here if anyone is interested
Thanks to the developper Jimmy for his effort (if he is also watching this thread^^)
thanks mate