-
Notifications
You must be signed in to change notification settings - Fork 23
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
Mapping of sensors #60
Comments
The card looks for this unit information in the sensors itself. You can check in Home Assistant > Developer Tools > States if the If some of your sensors lack the unit information, you could add it yourself in Home Assistent. If you didn't make the sensors yourself, you can still add the unit like here. |
Looking at your config in your second comment: you shouldn't use the same sensor for
If you have troubles understanding the readme file, please use the readme file on dev branch. That one is already rewritten and more to the point. |
Hello - (sorry to hijack this but it seems related) I seem to be misunderstanding something too. You can see that
On the power wheel it is showing
|
Obviously after I wrote the above I played around a bit and realised what the problem was. I removed
I know you wrote it down in bold but it still did not hit my brain clearly that only these two are required.. (what are the other two for any way I don't understand?) maybe instead of writing "either A or B+C" be more explicit. "When using B+C do not use A" ? |
My extra problem is the data comes from 2 different devices. Solar production comes directly from the Sunnyboy via modbus integration whilst my power consumption (momentaneous) comes from a DIY device connected to smart metering. In developer tools I see : Device 1: Device 2: Secondary problem : Night and Day consumption and production are different meters (On Device 1) Any hints are more than welcome ! |
@Tokn59 I am new to HomeAssistant but maybe its worth trying to see if you can create two new sensors, that take values from your other sensors based on your criteria.. I'm not sure.. is that going to be a Script maybe? An automation? I can try and look for you because this means I can learn something new too and may need that same thing in the future.. But back to my problem, I thought my problem was solved with using PV input and Grid.. but the values are still very strange. I looks like I am exporting 3kw to the grid for some reason? |
That's a good one. I'll add something to the docs. What these B+C sensors are for: some people have B+C sensors (instead of the usual A sensor). When your A sensor would turn negative, their B becomes 0 and their C gets the absolute value of your A sensor. But please forget, it's very rare. |
You can use a template sensor. I.e. you have to create one. This should help you start with it:
You can do similar things to get a total sensor for you day and night sensors.
|
You have I don't know for sure what your 'Inverter load' and 'Inverter grid' sensor measure, but if you expected a grid import (a.k.a. grid consumption) of 2880, you can try |
Done and working ! Thank You !!! |
@gurbyz - I had a typo in the config
It works now 😄 To answer your question
And that is what I use in the config which looks like this now
Thank you very much for this. I will also explore the money options.. that looks really cool |
Hi, thanks for sharing this great integration !
I have some difficulties mapping the right sensors.
I have the following sensors through DSMR (working om modbus integration)
sensor.energydel -> This is the TOTAL Kwh consumed
sensor.energyret -> This is the TOTAL Kwh produced
sensor.powerdel -> The current power delivery
sensor.powerret -> The current power produced
sensor.powerretl1 -> Same as powerret ???
If more energy is produced than consumed powerdel = 0
If more energy is consumed than produced powerret = 0
My DSMR values are :
For now I did the following :
How would you map this in the card ?
Also I have delivery and return seperate for day/night so actually 4 values.
Many thanks & KInd regards,
Tony
The text was updated successfully, but these errors were encountered: