marco79cgn

// dm Klopapier Widget
//
// Copyright (C) 2020 by marco79 <[email protected]>
//
// Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted.
//
// THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
// IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
// INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER
// IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE

simont77

Elgato Eve HomeKit Services & Characteristics

A work in progress collection of proprietary and as of yet undocumented HomeKit characteristics and their UUIDs used by Elgato Eve.

Based on the work by gomfunkel and 0ff. Characteristics and data dump for Door, Motion and Thermo thanks to @NebzHB.

More infos not yet incorporated in the comment section.

This list is not including all Eve accessories available and some services and characteristics still make no sense to me. If you have anything to contribute, please leave a comment. There is no guarantee that the information listed below is correct.

pburkholder

Original Question:

I had a call this afternoon ... and the question posed was how are we getting around the requirements for Admin level permissions on the Dev Environment to install and run Chef. It was a great question and I am sure we will run into that problem here very shortly. As you may or may not know, the Security requirements don’t allow [our organization's] Developers to have Admin level priv on the computers. Chef requires that to run.

TL;DR:

0. We need to reframe the question from the developer's access to the platform's permissions
1. The chef-client scheduled task on the windows nodes won't be useful unless it runs as an admin user.
2. Your developers will continue to need VMs to effectively do their work.

NickCraver

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="PrepareStaticContent" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <!-- Passed in Parameters -->
        <configuration></configuration>
        <workingDir></workingDir>
        <buildNumber></buildNumber>
        <buildViews>false</buildViews>
        <minifyJs>true</minifyJs>
        <TargetsDirectory></TargetsDirectory>