search

ngardiner / TWCManager

Control power delivered by a Tesla Wall Charger using two wires screwed into its RS-485 terminals.
The Unlicense
130 stars 55 forks source link

feature request: kWhDelivered/kWhCounter in WebUI, HASS status and MQTT #88

Open nean-and-i opened 4 years ago

nean-and-i commented 4 years ago

I'm working on a solution for a simple view of the consumed/charged kwh, preferably recorded by car/model (M3 and non tesla), just to get an overview of how much kwh each of the cars consumed in a year.

I think this fork is the closest to beginn with and fits quite good, as my idea was to integrate it in HASS anyway and/or make it available via MQTT.

I use TWCManager in a passive way, in fakemaster = 2 mode and like to capture the consumed kwh (on newer fw). As a second step I'm planing to readout part of the VIN to figure out if its a telsa or not to assign from-to charged kwh to the individual car.

is it possible to integrate kWhDelivered/kWhCounter msgpart from debug output in HASS and MQTT the same was as "total_amps_in_use", "totalAmpsInUse" ?

22:23:40 TWCManager 1 TWC Manager starting as fake Master with id 7777 and sign 77
22:23:41 TWCManager 9 Rx@: () FD EB 25 87 00 00 03 9C 00 F6 00 F0 00 F6 00 00 00 00 00 12
22:23:41 TWCManager 1 VRS XXX: 924kWh 246V 240V 246V
ngardiner commented 4 years ago

This is an interesting use-case. I don't see any reason why we couldn't query the Slave TWCs and record the lifetime kWh value, and ultimately make this available through the status interfaces. I'll take a look at this.

ngardiner commented 4 years ago

I have just committed (in commit 83bd6ff) some new code that will:

Let me know if it does what you need in your environment

ngardiner commented 4 years ago

As an update to the above, 8c37568 introduces detection of the polling not running (for fakeMaster = 1 users) and restarts polling if this is the case. This should mean reliable reporting of lifetime kWh and voltage per phase values for TWCs in both fakeMaster = 1 and fakeMaster = 2 modes, as long as they have the newer firmware that supports it. If not, it will just be reported as 0.

nean-and-i commented 4 years ago

hi,

awesome, thanks for picking up and implementing that rocket fast! I think there is great potential behind this idea.

I switched to 1.20 brunch and will help with testing. The first thing that popped up on my end is that the http UI won't run, pls. see below the exception, but need to dig a bit deeper for more details.

Apr 26 12:55:49 TWCManager python3[1050]: 12:55:49 TeslaAPI   6 Car API disabled for 569 more seconds due to recent error.
Apr 26 12:55:49 TWCManager python3[1050]: ----------------------------------------
Apr 26 12:55:49 TWCManager python3[1050]: Exception happened during processing of request from ('192.168.1.51', 65338)
Apr 26 12:55:49 TWCManager python3[1050]: Traceback (most recent call last):
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/socketserver.py", line 650, in process_request_thread
Apr 26 12:55:49 TWCManager python3[1050]:     self.finish_request(request, client_address)
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/socketserver.py", line 360, in finish_request
Apr 26 12:55:49 TWCManager python3[1050]:     self.RequestHandlerClass(request, client_address, self)
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/socketserver.py", line 720, in __init__
Apr 26 12:55:49 TWCManager python3[1050]:     self.handle()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/http/server.py", line 426, in handle
Apr 26 12:55:49 TWCManager python3[1050]:     self.handle_one_request()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/http/server.py", line 414, in handle_one_request
Apr 26 12:55:49 TWCManager python3[1050]:     method()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/home/pi/TWCManager/lib/TWCManager/Control/HTTPControl.py", line 337, in do_GET
Apr 26 12:55:49 TWCManager python3[1050]:     page += self.show_status()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/home/pi/TWCManager/lib/TWCManager/Control/HTTPControl.py", line 525, in show_status
Apr 26 12:55:49 TWCManager python3[1050]:     if (self.server.master.getModuleByName("Policy").policyIsGreen()):
Apr 26 12:55:49 TWCManager python3[1050]:   File "/home/pi/TWCManager/lib/TWCManager/Policy/Policy.py", line 260, in policyIsGreen
Apr 26 12:55:49 TWCManager python3[1050]:     for policy in self.charge_policy
Apr 26 12:55:49 TWCManager python3[1050]: StopIteration
Apr 26 12:55:49 TWCManager python3[1050]: ----------------------------------------
MikeBishop commented 4 years ago

IIRC, there's code to handle the report from the slave of the car's VIN, but nothing is done with it and we never ask the slave for this data.

nean-and-i commented 4 years ago

ad. kwh counter I've running with switch => 5 and fakemaster = 2 and see the counter in debug output every x seconds so it might not need to be requested. When charging the car this counter is increasing, so the info should be available.

22:23:41 TWCManager 1 VRS XXX: 924kWh 246V 240V 246V

Regarding the VIN, only available above certain FW version: I tested this with original TWCManager and in debug mode I was able to request info about the VIN, in parts, which was working in fakemaster =2 Theoretically one might only need the last 7 characters to distinguish between cars.

source: https://teslamotorsclub.com/tmc/threads/new-wall-connector-load-sharing-protocol.72830/page-20#post-3225600

Potentially useful commands in firmware 4.5.3 are: Remember, these commands won't work in TWCs containing firmware with a lower number than 4.5.3. 4.5.3 was included in TWCs manufactured around March 2018 and later.

FB EE SS SS RR RR

FB EF SS SS RR RR

FB F1 SS SS RR RR

ngardiner commented 4 years ago

Yes, we could certainly add this functionality alongside the lifetime kWh,

@MikeBishop, is the output above regarding the green policy check anything obvious to you? From a cursory examination it seems it iterates through all policies and does not find one which matches the active policy name. I've been unable to replicate it, but it seems a potential code path if that is what has happened.

ngardiner commented 4 years ago

I've running with switch => 5 and fakemaster = 2 and see the counter in debug output every x seconds so it might not need to be requested.

Yes that's as expected. Only fakeMaster = 1 requires it to be requested (and it should only happen in that case also) - we as a TWC should not send out any requests for this when fakeMaster = 2.

For the VIN however I'm not sure if you see requests for VIN parts in fakeMaster = 2? Given this is actual TWC driven, if it doesn't request it, you wouldn't see it.

nean-and-i commented 4 years ago

Are there recommended policy settings for config.json I should use for passive mode power-measure / always-charge-with-full-speed as default and maybe stop via interaction or after a timer (eg. 8h) run out (second for EV that can't be controlled via app/api like Tesla , eg. Zoe )

nean-and-i commented 4 years ago

hi,

awesome, thanks for picking up and implementing that rocket fast! I think there is great potential behind this idea.

I switched to 1.20 brunch and will help with testing. The first thing that popped up on my end is that the http UI won't run, pls. see below the exception, but need to dig a bit deeper for more details.

Apr 26 12:55:49 TWCManager python3[1050]: 12:55:49 TeslaAPI   6 Car API disabled for 569 more seconds due to recent error.
Apr 26 12:55:49 TWCManager python3[1050]: ----------------------------------------
Apr 26 12:55:49 TWCManager python3[1050]: Exception happened during processing of request from ('192.168.1.51', 65338)
Apr 26 12:55:49 TWCManager python3[1050]: Traceback (most recent call last):
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/socketserver.py", line 650, in process_request_thread
Apr 26 12:55:49 TWCManager python3[1050]:     self.finish_request(request, client_address)
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/socketserver.py", line 360, in finish_request
Apr 26 12:55:49 TWCManager python3[1050]:     self.RequestHandlerClass(request, client_address, self)
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/socketserver.py", line 720, in __init__
Apr 26 12:55:49 TWCManager python3[1050]:     self.handle()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/http/server.py", line 426, in handle
Apr 26 12:55:49 TWCManager python3[1050]:     self.handle_one_request()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/usr/lib/python3.7/http/server.py", line 414, in handle_one_request
Apr 26 12:55:49 TWCManager python3[1050]:     method()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/home/pi/TWCManager/lib/TWCManager/Control/HTTPControl.py", line 337, in do_GET
Apr 26 12:55:49 TWCManager python3[1050]:     page += self.show_status()
Apr 26 12:55:49 TWCManager python3[1050]:   File "/home/pi/TWCManager/lib/TWCManager/Control/HTTPControl.py", line 525, in show_status
Apr 26 12:55:49 TWCManager python3[1050]:     if (self.server.master.getModuleByName("Policy").policyIsGreen()):
Apr 26 12:55:49 TWCManager python3[1050]:   File "/home/pi/TWCManager/lib/TWCManager/Policy/Policy.py", line 260, in policyIsGreen
Apr 26 12:55:49 TWCManager python3[1050]:     for policy in self.charge_policy
Apr 26 12:55:49 TWCManager python3[1050]: StopIteration
Apr 26 12:55:49 TWCManager python3[1050]: ----------------------------------------

found the issue , provided temp. fix in #91 b842fe9

nean-and-i commented 4 years ago

I have just committed (in commit 83bd6ff) some new code that will:

  • Record the Lifetime kWh and Voltage per phase for each Slave TWC
  • In the standard master mode (fakeMaster = 1) we emulate the polling that the real TWC does of this value by polling it regularly. Note that there is a fairly significant issue in the first set of code I have committed in that if a TWC is offline for any period of time, we will stop polling it. I will keep this issue open until I've implemented a fix for this.
  • In the mode you're using (fakeMaster = 2), we don't need to worry about polling for this as the real TWC Master does that for us, so we are merely observing the response and recording it per Slave TWC.

  • The values collected are now available via the built-in TWCManager web interface, or via MQTT/HASS:

    • lifetimekWh/lifetime_kwh
    • voltagePhase[A/B/C] / voltagephase[A/B/C]

Let me know if it does what you need in your environment

doesn't seem to work, don't see meaningful values either in the webUI nor in HASS nor in MQTT broker. 

HASSStatus 8 Sending POST request to HomeAssistant for sensor sensor.twcmanager_all_total_amps_in_use (value 0)

Homeassistant States

Entity State
sensor.twcmanager_xxxx_amps_in_use 0  
sensor.twcmanager_xxxx_amps_max 6.0  
sensor.twcmanager_xxxx_cars_charging 0  
sensor.twcmanager_xxxx_power 0.0  
sensor.twcmanager_xxxx_state 0  
sensor.twcmanager_all_total_amps_in_use 0
ngardiner commented 4 years ago

@nean-and-i: Could you please grab the following entry from the log for me:

23:45:42 Policy 1 New policy selected; changing to Non Scheduled Charging (yours may differ)

Also, with the above, we do not publish the value to HASS or MQTT until we see it from the Slaves. Are you seeing the lifetime kWh and volts per phase in the log? If not, given you're in fakeMaster = 2 mode, it means the real TWC master has not yet probed the Slave TWCs for their lifetime kWh and volts per phase data.

nean-and-i commented 4 years ago

@nean-and-i: Could you please grab the following entry from the log for me:

23:45:42 Policy 1 New policy selected; changing to Non Scheduled Charging (yours may differ)

Also, with the above, we do not publish the value to HASS or MQTT until we see it from the Slaves. Are you seeing the lifetime kWh and volts per phase in the log? If not, given you're in fakeMaster = 2 mode, it means the real TWC master has not yet probed the Slave TWCs for their lifetime kWh and volts per phase data.

ad policy: no , can't find policy selected line in the log (maybe something missing in my config.json or settings.json ?)

ad lifetime kWh : yes, I do see it regularly in the logs, even in fakemaster =2 :

Apr 27 15:48:09 TWCManager python3[1463]: 15:48:09 TWCManager 1 VRS 2587: 937kWh 243V 242V 239V
ngardiner commented 4 years ago

Great, thank you for that. I can now see the cause of the exception you were getting (no policy selection for fakeMaster = 2). I'll keep that in mind going forward.

I'm investigating the missing HASS/MQTT/Web values now.

ngardiner commented 4 years ago

Unfortunately I was missing a rather important line for fakeMaster = 2 logging of the lifetime kWh value @nean-and-i. My apologies. I have updated this in 4749212.

ngardiner commented 4 years ago

With 6365098 we add VIN polling for TWCs which support this in their firmware. When a vehicle is detected charging on a Slave TWC, we will send the command to prompt the TWC to send the first 7 bytes of the attached vehicle. If it responds, we then go on to request the next 7 bytes and finally the last 3 bytes.

This is stored as current VIN and last VIN for each Slave TWC. This is now visible in the built-in web interface, and is published via MQTT and HASS:

I am going to use this opportunity to do some work on the two Status module docs pages now to reflect all of the various published values. They are:

nean-and-i commented 4 years ago

thanks a lot!

Shall I already see lifetimekwh on the webui (as with the current last commit it doesn't) or do I miss something, it shows up in the logs but nowhere else?

looks like master.updateSlaveLifetime need some love ?

Apr 28 17:27:09 TWCManager python3[11455]: Traceback (most recent call last):
Apr 28 17:27:09 TWCManager python3[11455]:   File "/home/pi/TWCManager/TWCManager.py", line 1290, in <module>
Apr 28 17:27:09 TWCManager python3[11455]:     master.updateSlaveLifetime(senderID[0], senderID[1], kWhCounter, voltsPhaseA, voltsPhaseB, voltsPhaseC)
Apr 28 17:27:09 TWCManager python3[11455]: TypeError: updateSlaveLifetime() takes 6 positional arguments but 7 were given

When a vehicle is detected charging on a Slave TWC, we will send the command to prompt the TWC to send the first 7 bytes of the attached vehicle. If it responds, we then go on to request the next 7 bytes and finally the last 3 bytes

Do you think we'd need it that perfect, wouldn't be just the last 7 bytes sufficient? What if charging is detected but there is no response to the polling like for a non Tesla car ?

ngardiner commented 4 years ago

Thanks @nean-and-i - I changed the function arguments between 1.1.8 and 1.2.0 so while it should have been working for 1.1.8, it wasn't for 1.2.0 which I have fixed with e8d3780.

The main problem with partial VIN is that none of the segments of the VIN alone seem very useful. You can get the first 7 bytes, the middle 7 bytes or the last 3 bytes. Arguably the last 3 are most significant in identifying any individual vehicle however you could have a situation where 2 vehicles with the last 3 VIN digits existed.

That said, we could make this an option - users could select full or partial VIN collection and skip the two extra VIN steps. The way this is implemented now it would just be a matter of skipping the first 2 VIN requests. It's hard to say whether this would be useful, I'm not entirely clear of the likely use cases for VIN details (outside of perhaps logging charge sessions or matching up vehicles to the API details) at this point.

MikeBishop commented 4 years ago

@nean-and-i, to your last question, if a non-Tesla car is charging the result will be all zeros.

nean-and-i commented 4 years ago

thanks, pls. let me know when I can/should test the lifetimekwh to be in webUI/mqtt/hass. I'm constantly pull the 1.2.0 branch and test but until now luck that the kwh shows up (except in the log) I'm on switch -> 5 (16A) and fakemaster=2

nean-and-i commented 4 years ago

Hi, can someone pls. let me know if lifetimekwh and vin actually works in fakemaster=2 ? it is not working on my end, no vin, no lifetimekwh in webui, no lifetimekwh in HASS. only logline like below:

22:23:41 TWCManager 1 VRS XXX: 924kWh 246V 240V 246V
nean-and-i commented 4 years ago

sorry guys, I can't get that to work even with the latest commits and reinstall, but maybe there is a misunderstanding or a config issue on my end, can someone pls. comment on my findings?

thanks, nean

tests

Passive Mode:

FakeMaster: 2 DIP: 5 (16A)

Active Mode:

FakeMaster: 1 DIP: F (slave mode)

config.json

One thing with the json file, can someone please remove the # comments, as there are no comments available in json specification and the validators are not happy with it either. (alternatively pls. use commenting according specs eg.: https://www.freecodecamp.org/news/json-comment-example-how-to-comment-in-json-files/ )

{
    "config": {
        "settingsPath": "/etc/twcmanager",
        "wiringMaxAmpsAllTWCs": 16,
        "wiringMaxAmpsPerTWC": 16,
        "minAmpsPerTWC": 12,
        "onlyChargeMultiCarsAtHome": true,
        "greenEnergyAmpsOffset": 0,
        "greenEnergyFlexAmps": 0,
        "subtractChargerLoad": false,
        "cloudUpdateInterval": 1800,
        "nonScheduledAmpsMax": 16,
        "nonScheduledLimit": -1,
        "chargeNowLimit": -1,
        "debugLevel": 10,
        "displayMilliseconds": false,
        "fakeMaster": 2
    },
    "interface": {
        "Dummy": {
            "enabled": false,
            "twcID": 1234
        },
        "RS485": {
            "enabled": true,
            "baud": 9600,
            "port": "/dev/ttyS0"
        },
        "TCP": {
            "enabled": false
        }
    },
    "control": {
        "HTTP": {
            "enabled": true,
            "listenPort": 8080
        },
        "MQTT": {
            "enabled": false,
            "brokerIP": "192.168.1.XX",
            "topicPrefix": "TWC",
            "username": "mqtt",
            "password": "XXXXXXXXXX"
        }
    },
    "policy":{
        "engine":{
            "policyCheckInterval": 30
        },
        "extend":{
            "emergency":[
            ],
            "before":[
            ],
            "after":[
            ],
            "restrictions":{
            }
        },
        "override": [
            { "name": "Non Scheduled Charging",
                "match": [ "none" ],
                "condition": [ "none" ],
                "value": [ 16 ],
                "charge_amps": "config.nonScheduledAmpsMax",
                "charge_limit": "config.nonScheduledLimit" }
            ]
    },
    "logging":{
        "Console": {
            "enabled": true
        },
        "CSV": {
            "enabled": true,
            "path": "/home/pi/csv",
            "mute":{
                "ChargeSessions": false,
                "GreenEnergy": false,
                "SlavePower": true,
                "SlaveStatus": true
            }
        },
        "MySQL": {
            "enabled": false,
            "host": "1.2.3.4",
            "database": "twcmanager",
            "username": "twcmanager",
            "password": "twcmanager"
        },
        "SQLite": {
            "enabled": true,
            "path": "/home/pi/twcmanager.sqlite"
        }
    },
    "sources":{
        "Fronius": {
            "enabled": false,
            "serverIP": "192.168.1.XX"
        },
        "HASS": {
            "enabled": false,
            "serverIP": "192.168.1.XX",
            "serverPort": "8123",
            "apiKey": "XXXXXXXXXXXXXXXXXXX",
            "hassEntityConsumption": "sensor.meter_power_live",
            "hassEntityGeneration":  "sensor.inverter_power_live"
        },
        "MQTT": {
            "enabled": false,
            "debugLevel": 11,
            "brokerIP": "192.168.1.XX",
            "topicPrefix": "TWC",
            "username": "mqtt",
            "password": "XXXXXXXXXX"
        },
        "Powerwall2": {
            "enabled": false,
            "serverIP": "192.168.1.XX",
            "password": "test123",
            "minBatteryLevel": 90
        },
        "TED": {
            "enabled": false,
            "serverIP": "192.168.1.XX",
            "serverPort": "8080"
        }
    },
    "status": {
        "HASS": {
            "enabled": true,
            "serverIP": "192.168.1.XX",
            "serverPort": "8123",
            "apiKey": "XXXXXXXXXXXXXXXXXXX"
        },
        "MQTT": {
            "enabled": true,
            "debugLevel": 11,
            "brokerIP": "192.168.1.XX",
            "topicPrefix": "TWC",
            "username": "mqtt",
            "password": "XXXXXXXXXX"
        }
    }
}
MikeBishop commented 4 years ago

FWIW, the commentjson module does allow comments, though I know they're non-standard. What I do is use a Find/Replace to remove the comments temporarily, see what the validation complains about, then undo the deletion and go fix the spot it said was broken.

Charge Now is probably your best bet to test. Alternatively, set Scheduled Charging to run all day using the web interface.

nean-and-i commented 4 years ago

@MikeBishop , thanks for your reply. hmmm, so, there is no way in "fakemaster=2", even if lifetimekwh is shown on the console output? Then I have to go via slave mode and figure out hoe to built a profile that allows charges all day ?

reg. commenting, I think this is not a major thing, it only gets a bit ugly on my end when using an editor that does linter and syntax checks (sublimetext2/VSC/,...) but feel free to ignore! maybe a short workaround without huge effort could be to have the json and comment/documentation separately?

my attempt putting it manually in pseudo object is a bit time consuming:

{
    "config": {
        "_comment_settingsPath" : [
            " The settings path will store the dynamic settings which are defined via the web interface"
        ],
        "settingsPath": "/etc/twcmanager",

        "_comment_wiringMaxAmpsAllTWCs" : [
            " Set wiringMaxAmpsAllTWCs to the maximum number of amps your charger wiring can handle.",
            " I default this to a low 6A which should be safe with the minimum ",
            " standard of wiring in the areas of the world that I'm aware of. ",
            " Most U.S. chargers will be wired to handle at least 40A and sometimes 80A,",
            " whereas EU chargers will handle at most 32A (using 3 AC lines instead of 2 so",
            " the total power they deliver is similar).",
            " Setting wiringMaxAmpsAllTWCs too high will trip the circuit breaker on your",
            " charger at best or START A FIRE if the circuit breaker malfunctions.",
            " Keep in mind that circuit breakers are designed to handle only 80% of their",
            " max power rating continuously, so if your charger has a 50A circuit breaker,",
            " put 50 * 0.8 = 40 here.",
            " 40 amp breaker * 0.8 = 32 here.",
            " 30 amp breaker * 0.8 = 24 here.",
            " 100 amp breaker * 0.8 = 80 here.",
            " IF YOU'RE NOT SURE WHAT TO PUT HERE, ASK THE ELECTRICIAN WHO INSTALLED YOUR CHARGER."
        ],
        "wiringMaxAmpsAllTWCs": 6,

        "_comment_wiringMaxAmpsPerTWC" : [
            " If all your chargers share a single circuit breaker, set wiringMaxAmpsPerTWC",
            " to the same value as wiringMaxAmpsAllTWCs.",
            " Rarely, each TWC will be wired to its own circuit breaker. If you're",
            " absolutely sure your chargers each have a separate breaker, put the value of",
            " that breaker * 0.8 here, and put the sum of all breakers * 0.8 as the value of",
            " wiringMaxAmpsAllTWCs.",
            " For example, if you have two TWCs each with a 50A breaker, set",
            " wiringMaxAmpsPerTWC = 50 * 0.8 = 40 and wiringMaxAmpsAllTWCs = 40 + 40 = 80."
        ],
        "wiringMaxAmpsPerTWC": 6,

        "_comment_minAmpsPerTWC" : [
            " https://teslamotorsclub.com/tmc/threads/model-s-gen2-charger-efficiency-testing.78740/ post-1844789",
            " says you're using 10.85% more power (91.75/82.77=1.1085) charging at 5A vs 40A,",
            " 2.48% more power at 10A vs 40A, and 1.9% more power at 20A vs 40A.  This is",
            " using a car with 2nd generation onboard AC/DC converter (VINs ending in 20000",
            " and higher).",
            " https://teslamotorsclub.com/tmc/threads/higher-amp-charging-is-more-efficient.24972/",
            " says that cars using a 1st generation charger may use up to 30% more power",
            " at 6A vs 40A!  However, the data refers to 120V 12A charging vs 240V 40A",
            " charging. 120V 12A is technically the same power as 240V 6A, but the car",
            " batteries need 400V DC to charge and a lot more power is wasted converting",
            " 120V AC to 400V DC than 240V AC to 400V DC.",
            "",
            " The main point is 6A charging wastes a lot of power, so we default to charging",
            " at a minimum of 12A by setting minAmpsPerTWC to 12. I picked 12A instead of 10A",
            " because there is a theory that multiples of 3A are most efficient, though I",
            " couldn't find any data showing that had been tested.",
            "",
            " Most EU chargers are connected to 230V, single-phase power which means 12A is",
            " about the same power as in US chargers. If you have three-phase power, you can",
            " lower minAmpsPerTWC to 6 and still be charging with more power than 12A on",
            " single-phase.  For example, 12A * 230V * 1 = 2760W for single-phase power, while",
            " 6A * 230V * 3 = 4140W for three-phase power. Consult an electrician if this",
            " doesn't make sense.",
            "",
            " https://forums.tesla.com/forum/forums/charging-lowest-amperage-purposely",
            " says another reason to charge at higher power is to preserve battery life.",
            " The best charge rate is the capacity of the battery pack / 2.  Home chargers",
            " can't reach that rate, so charging as fast as your wiring supports is best",
            " from that standpoint.  It's not clear how much damage charging at slower",
            " rates really does."
        ],
        "minAmpsPerTWC": 12,

        "_comment_onlyChargeMultiCarsAtHome" : [
            " When you have more than one vehicle associated with the Tesla car API and",
            " onlyChargeMultiCarsAtHome = True, cars will only be controlled by the API when",
            " parked at home. For example, when one vehicle is plugged in at home and",
            " another is plugged in at a remote location and you've set TWCManager to stop",
            " charging at the current time, only the one plugged in at home will be stopped",
            " from charging using the car API.",
            " Unfortunately, bugs in the car GPS system may cause a car to not be reported",
            " as at home even if it is, in which case the car might not be charged when you",
            " expect it to be. If you encounter that problem with multiple vehicles, you can",
            " set onlyChargeMultiCarsAtHome = False, but you may encounter the problem of",
            " a car not at home being stopped from charging by the API."
        ],
        "onlyChargeMultiCarsAtHome": true,

        "_commen_defaultVoltage" : [
            " Newer TWCs can report actual voltages. ",
            " For older TWCs, you can specify what voltage should be assumed and",
            " whether the power is single (1) or 3-phase."
        ],
        "defaultVoltage": 240,
        "numberOfPhases": 1,
        "_comment_greenEnergyAmpsOffset" : [
            " When determining how much green energy is available for charging, we count",
            " greenEnergyAmpsOffset as consumption. This is most often given a value",
            " equal to the average amount of power consumed by everything other than car",
            " charging. For example, if your house uses an average of 2.8A to power",
            " computers, lights, etc while you expect the car to be charging, set",
            " greenEnergyAmpsOffset = 2.8.",
            "",
            " If you have solar panels, look at your utility meter while your car charges.",
            " If it says you're using 0.67kW, that means you should set",
            " greenEnergyAmpsOffset = 0.67kW * 1000 / 240V = 2.79A assuming you're on the",
            " North American 240V grid. In other words, during car charging, you want your",
            " utility meter to show a value close to 0kW meaning no energy is being sent to",
            " or from the grid.",
            "",
            " If you are able to obtain consumption details from an energy management system,",
            " this value can be set to 0 unless you wish to manually adjust what it returns."
        ],
        "greenEnergyAmpsOffset": 0,

        "_comment_greenEnergyFlexAmps" : [
            " If green energy dips below the target charge amount while already charging,",
            " how much extra current should be drawn to keep charging?  This avoids frequently",
            " stopping and starting charging on a day with variable solar output, at the cost],",
            " of drawing energy from sources other than solar."
        ],
        "greenEnergyFlexAmps": 0,

etc,...

thanks!

MikeBishop commented 4 years ago

I haven't tried a setup with fakemaster=2, so I'll need to defer to @ngardiner on that. And it's entirely possibly one of my contributions broke something there, because that's not the setup I have to work with.

nean-and-i commented 2 years ago

Hi,

long time no see, after I while I'm back to the project and glad to see all the good progress. for this issue I guess I found the correct/working place for pushing status update to MQTT/HASS in passiv scenario.

please check PR https://github.com/ngardiner/TWCManager/pull/469 "Status updates for MQTT/HASS in fakeMaster=2 mode ", it works now, but maybe some cleanup is required

thanks