Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Light config does not work and causes error message #3

Closed
W-Floyd opened this issue Nov 13, 2020 · 3 comments
Closed

Light config does not work and causes error message #3

W-Floyd opened this issue Nov 13, 2020 · 3 comments

Comments

@W-Floyd
Copy link
Owner

W-Floyd commented Nov 13, 2020

The following message keeps appearing, looping

DEBUG[net]      logic waiting for msg on ibound
DEBUG[net]      startIncomingComms: got msg on ibound
DEBUG[net]      startIncomingComms: received publish, msgId: 0
DEBUG[net]      startIncoming Received Message

with a config of:

    "lights": [
        {
            "info": {
                "name": "Desktop Monitor",
                "id": "monitor"
            },
            "command": [
                "./scripts/monitor.sh",
                "command"
            ],
            "command_state": [
                "./scripts/monitor.sh",
                "command-state"
            ],
            "command_color_temp": [
                "./scripts/monitor.sh",
                "color-temp"
            ],
            "command_color_temp_state": [
                "./scripts/monitor.sh",
                "color-temp-state"
            ],
            "command_brightness": [
                "./scripts/monitor.sh",
                "brightness"
            ],
            "command_brightness_state": [
                "./scripts/monitor.sh",
                "brightness-state"
            ],
            "brightness_scale": 100,
            "update_interval": 5
        }
    ],
@W-Floyd
Copy link
Owner Author

W-Floyd commented Nov 13, 2020

It seems that I had a stray retained message on the config topic for this light, which caused issues. Sending a blank message on this topic fixed it. Will close for now, but consider automatically publishing a blank message to clear things out.

@W-Floyd W-Floyd closed this as completed Nov 13, 2020
@W-Floyd W-Floyd reopened this Nov 14, 2020
@W-Floyd
Copy link
Owner Author

W-Floyd commented Nov 14, 2020

The issue returned, need to investigate.

@W-Floyd
Copy link
Owner Author

W-Floyd commented Nov 14, 2020

I believe it was an issue unrelated to this software. I had a state_changed trigger monitoring the automation triggering it, resulting in 100s of automation runs each second as it triggered itself again and again, overloading my HA server. I didn't realise this for a couple days.

@W-Floyd W-Floyd closed this as completed Nov 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant