-
Notifications
You must be signed in to change notification settings - Fork 14
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
Question: How to keep history for external voltage for each phase? #353
Comments
This is of course doable. We have lots of attributes on different entities so maybe we should extract all of them? Thoughts on this @henricm ? |
I've also thought about this actually. I think it's a good idea to extract the values for each phase to be sensors of their own. Or are there other attributes too? I'm thinking about the sensors that have L1, L2, L3 attributes. |
There is a pos/neg somewhere and probably something else but most are L1, L2, L3. I'll see if I can find the time to do something. |
For diagnostics it would be a nice feature. I guess downside is there will be a lot of sensors 🤓 .
Maybe it's a good idea to keep the original the original sensors (including state attrs too). For sensors like |
Think also this feature would be good, i have solved this today by creating templates:
|
Yes, not really a problem I would say.
Yes, I didn't plan on removing the current entities, just add new for each phase. |
Wouldn't it be nice to have a a separate sensor for external voltage for each phase for history purposes?
Correct me if i'm wrong, In the current implementation, per phase values are implemented as state attributes and are not recorded.
Phase history is helpful when trying to understand if SSO/EH fault codes are related to grid voltage.
Im using a workaround is to create a template sensor to grab phase voltage..
The text was updated successfully, but these errors were encountered: