profile
viewpoint

LEJOUI/addon-mqtt 0

MQTT Server & Web client - Community Hass.io Add-on for Home Assistant

LEJOUI/addon-nginx-proxy-manager 0

Nginx Proxy Manager - Community Hass.io Add-on for Home Assistant

LEJOUI/ble_monitor 0

Passively monitors BLE messages from Xiaomi Mijia BLE MiBeacon, Qingping, ATC, Xiaomi Scale, Govee, Kegtron, iNode and Thermoplus sensors

LEJOUI/esp8266_milight_hub 0

Replacement for a Milight/LimitlessLED hub hosted on an ESP8266

LEJOUI/light-entity-row 0

Fork: Entity row for lights with sliders for adjusting different values based on features

LEJOUI/Tasmota-Tuya-Helper 0

Bookmarklet for Tasmota to assist configuring Tuya devices

LEJOUI/zigbee-shepherd-converters 0

Collection of device converters to be used with zigbee-shepherd

LEJOUI/zigpy-cc 0

CC2531 handler for zigpy

push eventLEJOUI/Tasmota-Tuya-Helper

Sergio

commit sha 68d0c1fb8d80f459ca68d6c2b7a66d0fe6f3d6fd

Updated fnId

view details

sillyfrog

commit sha dbe22fcf9f7f49991aa82d3244c6c855e0c0ee79

Merge pull request #6 from b0rder/master Updated fnId

view details

chaveiro

commit sha 8bd1259ae1688fd41605ea02311a5f83bf8b790a

Add support for FnId 34 to 37 Fix issue https://github.com/sillyfrog/Tasmota-Tuya-Helper/issues/7

view details

Shell Dev - User

commit sha f4296c11e3f9fd5c4d8a8962cd2c40f23361f814

modified: tuya-bookmarklet.js modified: tuya-helper.js

view details

sillyfrog

commit sha ece92ac384d23bb992107ca4782de5a733273a42

Merge pull request #8 from chaveiro/patch-1 Add support for FnId 34 to 37

view details

push time in 5 days

delete branch LEJOUI/core

delete branch : patch-1

delete time in 5 days

PR opened home-assistant/core

Reviewers
Fix key reference placeholder

Fix missing % for placeholder invalid acces token

<!-- You are amazing! Thanks for contributing to our project! Please, DO NOT DELETE ANY TEXT from this template! (unless instructed). -->

Breaking change

<!-- If your PR contains a breaking change for existing users, it is important to tell them what breaks, how to make it work again and why we did this. This piece of text is published with the release notes, so it helps if you write it towards our users, not us. Note: Remove this section if this PR is NOT a breaking change. -->

Proposed change

<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue in the additional information section. -->

Type of change

<!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multiple PRs. This makes things easier and faster to code review. -->

  • [ ] Dependency upgrade
  • [ ] Bugfix (non-breaking change which fixes an issue)
  • [ ] New integration (thank you!)
  • [ ] New feature (which adds functionality to an existing integration)
  • [ ] Breaking change (fix/feature causing existing functionality to break)
  • [x] Code quality improvements to existing code or addition of tests

Additional information

<!-- Details are important, and help maintainers processing your PR. Please be sure to fill out additional details, if applicable. -->

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

<!-- Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. -->

  • [ ] The code change is tested and works locally.
  • [ ] Local tests pass. Your PR cannot be merged unless tests pass
  • [ ] There is no commented out code in this PR.
  • [ ] I have followed the [development checklist][dev-checklist]
  • [ ] The code has been formatted using Black (black --fast homeassistant tests)
  • [ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

  • [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]

If the code communicates with devices, web services, or third-party tools:

  • [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • [ ] New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • [ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following [Integration Quality Scale][quality-scale]: <!-- The Integration Quality Scale scores an integration on the code quality and user experience. Each level of the quality scale consists of a list of requirements. We highly recommend getting your integration scored! -->

  • [ ] No score or internal
  • [ ] 🥈 Silver
  • [ ] 🥇 Gold
  • [ ] 🏆 Platinum

<!-- This project is very active and we have a high turnover of pull requests.

Unfortunately, the number of incoming pull requests is higher than what our reviewers can review and merge so there is a long backlog of pull requests waiting for review. You can help here!

By reviewing another pull request, you will help raise the code quality of that pull request and the final review will be faster. This way the general pace of pull request reviews will go up and your wait time will go down.

When picking a pull request to review, try to choose one that hasn't yet been reviewed.

Thanks for helping out! -->

To help with the load of incoming pull requests:

<!-- Thank you for contributing <3

Below, some useful links you could explore: --> [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

+1 -1

0 comment

1 changed file

pr created time in 5 days

push eventLEJOUI/core

LJU

commit sha f3e612edb546172a49342b4657ea50255fa49c5e

Fix key reference placeholder Fix typo for placeholder invalid acces token

view details

push time in 5 days

fork LEJOUI/core

:house_with_garden: Open source home automation that puts local control and privacy first.

https://www.home-assistant.io

fork in 5 days

issue commentcustom-components/ble_monitor

Error doing job: Fatal error: protocol.data_received() call failed

Thanks for the update. Unfortunately the issue still persists in the latest beta.

LEJOUI

comment created time in a month

issue commentbasnijholt/adaptive-lighting

User input malformed

Same issue was found in the ble custom component. He found a solution, might be helpfull?

SeLLeRoNe

comment created time in a month

delete branch LEJOUI/hassio-addons

delete branch : patch-1

delete time in a month

Pull request review commentcustom-cards/light-entity-row

Fix for object is not extensible

 class AdjustableLightEntityRow extends Polymer.Element {     param.hs_color = [ev.detail.hs.h, ev.detail.hs.s*100]     this._hass.callService('light', 'turn_on', param);   }-   setConfig(config)   {      const checkServiceRegexp = /^(light|group)\./     if (!checkServiceRegexp.test(config.entity)) {       throw new Error(`invalid entity ${config.entity}`)     }-    +     this._config = JSON.parse(JSON.stringify(config));-    this._config.buttons = config.buttons || []+    this._buttons = JSON.parse(JSON.stringify(config.buttons))

thanks!

LEJOUI

comment created time in 2 months

PullRequestReviewEvent

push eventLEJOUI/light-entity-row

LJU

commit sha 54067bc883e5b8e14a0eca3a875027b6c96082d8

Update light-entity-row.js Co-authored-by: Philip Allgaier <philip.allgaier@gmx.de>

view details

push time in 2 months

created tagLEJOUI/light-entity-row

tagv0.3.1b

Fork: Entity row for lights with sliders for adjusting different values based on features

created time in 2 months

release LEJOUI/light-entity-row

v0.3.1b

released time in 2 months

push eventLEJOUI/light-entity-row

LJU

commit sha 532acafc06bcd2e9d2839e35723c87c3ba121b54

Test change

view details

push time in 2 months

startedhome-assistant/core

started time in 2 months

issue openedbasnijholt/adaptive-lighting

TypeError: '>' not supported between instances of 'int' and 'str'

Version information:

1.0.14 HA 2021.10.2

Description:

<!-- This is where you get to tell us what went wrong. When doing so, please make sure to include all relevant information.

Please try to include:

  • What you were doing when you experienced the bug.
  • Any error messages you saw, where you saw them, and what you believe may have caused them (if you have any ideas).
  • When possible, steps to reliably produce the bug. --> There’s this error popping up in my logs. However I’m not noticing an effect in the performance though.
Deze fout is ontstaan door een aangepaste integratie.

Logger: homeassistant
Source: custom_components/adaptive_lighting/switch.py:1461 
Integration: adaptive_lighting 
First occurred: 9 oktober 2021 23:07:22 (2 occurrences) 
Last logged: 9 oktober 2021 23:11:28

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/adaptive_lighting/switch.py", line 944, in _light_event
    if await self.turn_on_off_listener.maybe_cancel_adjusting(
  File "/config/custom_components/adaptive_lighting/switch.py", line 1461, in maybe_cancel_adjusting
    delay = max(transition, TURNING_OFF_DELAY)
TypeError: '>' not supported between instances of 'int' and 'str'

created time in 2 months

more