Skip to content

binary sensor issue #109

Description

@smcneece

To the Author thank you for putting in the time to create this integration, especially since SunStrong is going to start charging what should have been free before the flop of Sunpower.

I've spent a few hours trying to make an automation that detects when an inverter goes "offline". My understanding of inverters is most all of them only work when the sun itself is powering them. So I want to track in notifications when they go offline especially due to just simply being dead.

I have been working with the binary_sensor.inverter_e*_state.

Watching the state in Dev Tools -> State I have seen two values so far: 'working', and 'error'. They were in working state until sun went down, and now they are all in an error state because it's 11:44PM and it's dark.

I've been having weird problems with testing the value of that binary value for an automation to notify me of as panel going offline or online. I roped in ChatGPT for assistance, as well as someone on the official Home Assistant support forums and they tell me Home Assistant expects those values to be be: on, off, unavailable or unknown. (Creating a manual test of that binary,sensor.inverter_ entity and you are given those to test with as seen from screen cap below) .

Image

Looking for guidance or if they are correct that the sensor values be updated to the standard because having odd values are messing with logic of automations?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions