Domoticz

Posted: **Friday 09 August 2024 20:40**

DiaDomo wrote: ↑Friday 09 August 2024 20:33 @rron: please post this screenshot:
and 2 from smartevse without detailed information.

Sorry what do you mean?

Posted: **Friday 09 August 2024 21:27**

You said earlier that you also would send a screenshot with the MQTT settings of the SmartEVSE interface, but you didn't send this one yet.

Posted: **Friday 09 August 2024 21:34**

This is the only setting

Posted: **Saturday 10 August 2024 10:51**

rron wrote: ↑Friday 09 August 2024 19:48
FlyingDomotic wrote: ↑Friday 09 August 2024 19:26 Idea is to use a tool (like MQTT Explorer) to extract data from MQTT topic "SmartEVSE-5572" and copy it here.
There ' s no further information in the mqtt explorer. I have made 2 screenshots from the explorer, 1 from zigbee2mqtt with information and 2 from smartevse without detailed information.

thanks!
Let's try with:

Code: Select all

{
    "SmartEVSE charge current": {
        "topic": "[MQTTprefix]/ChargeCurrent",
        "type": "243", "subtype": "23", "switchtype": "0",
        "mapping": {"item": "", "multiplier": 0.1}
    },
    "SmartEVSE max current": {
        "topic": "[MQTTprefix]/MaxCurrent",
        "type": "243", "subtype": "23", "switchtype": "0",
        "mapping": {"item": "", "multiplier": 0.1}
    },
    "SmartEVSE state": {
        "topic": "[MQTTprefix]/State",
        "type": "243", "subtype": "19", "switchtype": "0",
        "mapping": {"item": ""}
    },
    "SmartEVSE error": {
        "topic": "[MQTTprefix]/Error",
        "type": "244", "subtype": "73", "switchtype": "18",
        "options": {"SelectorStyle":"1", "LevelOffHidden": "false", "LevelNames":"None|No Power Available|Communication Error|Temperature High|EV Meter Comm Error|RCM Tripped|Waiting for Solar|Test IO|Flash Error|**Unknown**"},
        "mapping": {"item": "", "default": "90",
            "values": {
                "None": "0",
                "No Power Available": "10",
                "Communication Error": "20",
                "Temperature High": "30",
                "EV Meter Comm Error": "40",
                "RCM Tripped": "50",
                "Waiting for Solar": "60",
                "Test IO": "70",
                "Flash Error": "80",
                "**Unknown**": "90"
                }
            }
    },
    "SmartEVSE charge current override": {
        "topic": "[MQTTprefix]/ChargeCurrentOverride",
        "type": "242", "subtype": "1", "switchtype": "0",
        "options": {"ValueStep": "1", "ValueMin": "0", "ValueMax": "200", "ValueUnit": "A"},
        "initial": {"nvalue": "0", "svalue": "0"},
        "mapping": {"item": "", "multiplier": 0.1},
        "set": {"topic": "[MQTTprefix]/Set/CurrentOverride", "digits": 0}
    }
}

You can use this as an example, should you wish to add other counters/indicators to Domoticz.

Don't hesitate to ask for help if needed.

Posted: **Saturday 10 August 2024 11:43**

Yes, this fully working. Thank you very much. I now can try to add some indicators myself. Again thank you for all the effort.

Posted: **Saturday 10 August 2024 12:22**

Code: Select all

 2024-08-10 11:53:04.258 Error: mapper: No SET parameters for SmartEVSE charge current/SmartEVSE-5572/ChargeCurrent in ('SmartEVSE charge current', {'topic': 'SmartEVSE-5572/ChargeCurrent', 'type': '243', 'subtype': '23', 'switchtype': '0', 'mapping': {'item': '', 'multiplier': 0.1}})
2024-08-10 11:53:27.780 Error: mapper: No SET parameters for SmartEVSE state/SmartEVSE-5572/State in ('SmartEVSE state', {'topic': 'SmartEVSE-5572/State', 'type': '243', 'subtype': '19', 'switchtype': '0', 'mapping': {'item': ''}})
2024-08-10 11:53:37.623 Error: mapper: No SET parameters for SmartEVSE max current/SmartEVSE-5572/MaxCurrent in ('SmartEVSE max current', {'topic': 'SmartEVSE-5572/MaxCurrent', 'type': '243', 'subtype': '23', 'switchtype': '0', 'mapping': {'item': '', 'multiplier': 0.1}})
2024-08-10 11:53:54.493 Error: mapper: No SET parameters for SmartEVSE error/SmartEVSE-5572/Error in ('SmartEVSE error', {'topic': 'SmartEVSE-5572/Error', 'type': '244', 'subtype': '73', 'switchtype': '18', 'options': {'SelectorStyle': '1', 'LevelOffHidden': 'false', 'LevelNames': 'None|No Power Available|Communication Error|Temperature High|EV Meter Comm Error|RCM Tripped|Waiting for Solar|Test IO|Flash Error|**Unknown**'}, 'mapping': {'item': '', 'default': '90', 'values': {'None': '0', 'No Power Available': '10', 'Communication Error': '20', 'Temperature High': '30', 'EV Meter Comm Error': '40', 'RCM Tripped': '50', 'Waiting for Solar': '60', 'Test IO': '70', 'Flash Error': '80', '**Unknown**': '90'}}})

There are some errors in the logging. I will try tomorrow with loading my car and look what going to happen.

Posted: **Saturday 10 August 2024 13:04**

When do you get these errors?

Do you try to manually change the values?

Posted: **Saturday 10 August 2024 13:10**

No I didn’t manual change these values. I will try again tomorrow with my car and see what happens. I let you know.

Posted: **Saturday 10 August 2024 15:06**

Reason of my question is that "No SET parameters" message is displayed only when you try to change value in Domoticz (either by GUI or script), and don't give set params for that.

We must understand who is trying to change value (and perhaps why).

Posted: **Saturday 10 August 2024 15:28**

What about 2 different smart evse topics in the screenshots?
Strange to me.

Posted: **Saturday 10 August 2024 15:34**

Probably a default value somewhere, used 'til properly configured.

Posted: **Sunday 11 August 2024 12:15**

I'm testing it in life situation. Everything looks good but the current values are displaying 1.6 instead of 16. If I change multiplier to 1 it give 160.the rest is made. Everything is made right now.This is the logging:

Code: Select all

2024-08-11 12:26:17.202 mapper: Setting SmartEVSE error to 0/0.0
2024-08-11 12:26:28.183 mapper: Setting SmartEVSE max current to 1/1.6
2024-08-11 12:26:28.191 mapper: Setting SmartEVSE charge current to 1/1.6
2024-08-11 12:26:28.199 mapper: Setting SmartEVSE charge current override to 0/0.0
2024-08-11 12:26:28.207 mapper: Setting SmartEVSE state to >Charging<
2024-08-11 12:26:28.215 mapper: testValue="None" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.215 mapper: testValue="No Power Available" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.216 mapper: testValue="Communication Error" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.216 mapper: testValue="Temperature High" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.217 mapper: testValue="EV Meter Comm Error" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.218 mapper: testValue="RCM Tripped" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.219 mapper: testValue="Waiting for Solar" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.219 mapper: testValue="Test IO" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.220 mapper: testValue="Flash Error" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.220 mapper: testValue="**Unknown**" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:28.221 mapper: Setting SmartEVSE error to 0/0.0
2024-08-11 12:26:39.151 mapper: Setting SmartEVSE max current to 1/1.6
2024-08-11 12:26:39.167 mapper: Setting SmartEVSE charge current to 1/1.6
2024-08-11 12:26:39.180 mapper: Setting SmartEVSE charge current override to 0/0.0
2024-08-11 12:26:39.194 mapper: Setting SmartEVSE state to >Charging<
2024-08-11 12:26:39.208 mapper: testValue="None" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.209 mapper: testValue="No Power Available" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.210 mapper: testValue="Communication Error" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.211 mapper: testValue="Temperature High" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.211 mapper: testValue="EV Meter Comm Error" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.211 mapper: testValue="RCM Tripped" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.212 mapper: testValue="Waiting for Solar" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.212 mapper: testValue="Test IO" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.214 mapper: testValue="Flash Error" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.215 mapper: testValue="**Unknown**" (<class 'str'>), readValue="None" (<class 'str'>)
2024-08-11 12:26:39.216 mapper: Setting SmartEVSE error to 0/0.0
2024-08-11 12:26:50.209 mapper: Setting SmartEVSE max current to 1/1.6
2024-08-11 12:26:50.225 mapper: Setting SmartEVSE charge current to 1/1.6
2024-08-11 12:26:50.240 mapper: Setting SmartEVSE charge current override to 0/0.0
2024-08-11 12:26:50.256 mapper: Setting SmartEVSE state to >Charging<

If have also not seen the error from yesterday.

Posted: **Sunday 11 August 2024 16:58**

Could you try with last version of MqttMqpper plugin, I found a bug?

Posted: **Sunday 11 August 2024 19:15**

Ok, i will try and let you

Posted: **Sunday 11 August 2024 19:43**

Thanks, that was it! The current is now 16A. Thanks again for the effort.

Posted: **Monday 12 August 2024 0:43**

You're welcome!

Posted: **Monday 12 August 2024 19:46**

I have still a question nl the charge current is still at 16A without loading. I think that charge current is the same value as max current.
In the settings from smartevse is max current a fixed value (in my case 16A) and charge current should be a variable value, in the beginning the max (16A) and at the end lower and when full 0A.

Posted: **Monday 12 August 2024 23:37**

Have a check with data in MQTT. As MqttMapper get changes through MQTT, if MQTT is false, MqttMapper has the same default.

Else, it's a MqttMapper bug

Posted: **Tuesday 13 August 2024 19:32**

FlyingDomotic wrote: ↑Monday 12 August 2024 23:37 Have a check with data in MQTT. As MqttMapper get changes through MQTT, if MQTT is false, MqttMapper has the same default.

Else, it's a MqttMapper bug

I think it's a bug, If you look at the mqtt explorer you can see the old topic smartevse (previous MqttMapper)and there was the ChargeCurrent 0 and in the latest release you can see the new topix SmartEVSE-5572 and now is the ChargeCurrent 16. The same is for MainsCurrent L1=-7, that should be -0,7

Posted: **Wednesday 14 August 2024 0:37**

Could I have MqttMapper json configuration file?

Domoticz

SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support

Re: SmartEvse support