![]() There are also two entities that can be used to enable/disable the sensor. The light level to trigger switching on a light can also be set. Different brightness and colour settings can be used for between 22:00 and 07:00, so if you get up to take leak in the middle of the night you are not blinded by bright lights as you walk out onto the landing The Blueprint takes a number of parameters to use the occupancy sensor to control a light or group of lights. The attributes are set whenever Home Assistant starts allowing your SML001 to behave as an occupancy sensor and not a bad motion sensor (as it does when using the defaults). I have reviewed two other in this repository.If you are using ZHA to control your Philips Hue SML001 Motion Sensor then this Blueprint can be used to configure the Occupied to Unoccupied Delay & Sensitivity ZigBee Cluster attributes. The integration reached or maintains the following : Add hue scene event on button events for V2 implementation Documentation probably needs some updating Untested files have been added to `.coveragerc`. Tests have been added to verify that the new code works. The code has been formatted using Black (`black -fast homeassistant tests`) There is no commented out code in this PR. **Your PR cannot be merged unless tests pass** The code change is tested and works locally. Read status of and control entertainment areas ![]() Possible Future update(s) in follow-up PR's - library support already there A few more sensors are detected because of the simple fact that the new API provides more states. Import of scenes (optional toggle), including support for Hue's new "dynamic" scenes. This is now fixed.Īlthough the scope for this PR is to (only) implement all current integration platforms/features with the V2 api/library, a few new features are available: The current implementation is still hammering the bridge with requests even if events are streamed. In "V2 mode" the bridge will no longer be polled for state, all state changes come in instantly. ![]() Code quality improvements to existing code or addition of tests Breaking change (fix/feature causing existing functionality to break) ![]() New feature (which adds functionality to an existing integration) Bugfix (non-breaking change which fixes an issue) The Home Assistant integration needs to adopt the new V2 implementation with auto switching to the correct version. The aiohue library has been rewritten to the full V2 api, while still supporting V1 style for older bridges. Hue is phasing out the current V1 api in favor of their new V2 Clip API, including events being pushed instead of hammering the bridge to poll changes. There should be None as I've made sure all is backwards comp … atible but it needs real proper testing. “The effects will play directly on the lamps, so the dynamic scenes will run independently of the rest of the network.” “We will solve the problem like no one else can,” promises George Yianni. But both solutions are particularly performance-hungry: each colour change is sent as a single command from the Hue Bridge into the ZigBee network to the lamps. In Hue Labs you can already activate a colour loop for a long time and third-party apps like iConnectHue offer freely configurable animations. anyway lets see I think some geek friends can solve it What is the difference to animation from Hue Labs or apps like iConnectHue? i try to catch commands with Wireshark but couldn’t succeed. In official Philips hue software each scene has dynamic option with same name, it should be different parameter to start this dynamic option. I am not familiar this type of data sniffing maybe some one can sniff network between bridge and software and catch parameters how to start dynamic scene. I saw similar information about hue dynamic scenes, it says scenes managed by lambs or bridge not by program. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |