Tuya integrated EV-charger (single phase, 32A 85-264v, 7,4 kwh) #1149
Comments
Striiter
changed the title
make-all
added
the
log provided
|
Have a very similar charger (feyree 32A 240V) and the datapoints are identical. 2023-10-09 00:12:14.879 WARNING (MainThread) [custom_components.tuya_local.config_flow] Device matches loratap_zigbee_six_switch with quality of 8%. DPS: {"updated_at": 1696770732.7265275, "10": 0, "101": "charing", "102": 32, "104": 0, "106": 12, "107": 221, "108": 307, "109": 67, "110": 301, "112": false, "113": 1, "114": 0} |
|
@ve1koz111, if you have access to the iot.tuya.com developer portal, perhaps you can get the results of the Query Things Data Model API call (in API Explorer) for your device, as it will help with clarifying some of the details of the data points. |
|
Idk if this helps. This is the official "Tuya" app, It tells me "AC Charging Box (unsupported) by Tuya" In the textfile it gives me through the diagnostic is this: }, |
|
Thanks, yes this helps, the only thing missing is dp ids, which can be correlated from above, but that also indicates that it is likely cloud API docs, so if any of the enum values differ between cloud and local protocol it won't quite work (but probably 90% chance it will be OK). |
make-all
added
full_info
make-all
added
awaiting confirmation
|
I have added support for the dps that are showing in the logs. There are others which seem to be for setting different charging modes - I don't know if they are missing from the log because the charger does not support them, or because they are mode dependant. They have been added as optional attributes, mostly of the Status entity, so they are available for monitoring, if you can confirm that the device does send them in some modes, I can separate them into separate entities, particularly the config options that you want to be able to change rather than just monitor. |
|
Thank you @make-all This was very quick! I will await release so i can test and give a comprehensive repport if i find bugs or such. Thank you again. Kind regards! |
|
Hello, I have the same issue than ve1koz111. When I try to configure, my device is seen as a lora tap 6 switches. ===== EDIT : I tried to take your feyree.yaml file and rewrite it in order to map the DPS and make their different types to match to the what is in the file below but it still does not work (still 6% match with Loratap zigbee switch). I'm very bad at this... My understanding of your code is that there is a comparison of the DPS from the "devices".yaml file to something that must be coming from tuya or the device when you try to connect. Then if there is a 100% match, it's fine, if not, it gives you the best match with the one of the devices that are in the devices directory. I don't get the distinction between primary entity and secondary entities and how to define it. Maybe it is not well defined in the yaml that I'm trying to edit and does not work, I don't know.... ===== { Does it help ? Kind regards ! |
make-all
removed
new device
|
I found this thread while looking for ideas on how to setup user selectable kw.hr charge sessions. just dropping these notes in the hope someone else finds it useful. (issue closed before I found this thread) I bought this one on aliexpress, paid extra to have an Australian 5 pin 3 phase plug wired on prior to delivery. Has worked well for a couple of months now. Similar charger on ebay |
|
Hello. I have this wallbox: https://www.aliexpress.com/item/1005007333648233.html?spm=a2g0o.order_list.order_list_main.11.210d1802w109Jv The Tuya app works, the iot account too, I have all the keys and ids, but I can't add the device to the home assistant. It shows: feyree (unsupported) (xiptqjoa8q9ltqhr) I can't add the device via local integration either, the message appears: Find the device's IP address Please help, I've spent many hours on this without any results. |
|
If you have attempted to add this device via this integration, then you need to check in Settings / System / Logs, and paste any Warning messages related to this integration with your report here. We can't help if all we have is a vague description of things not working, much of which does not appear to be related to this integration. |
Thank you. After trying to add a device, this entry appears in the logs. Rejestrator: aiohttp.server Error handling request |
|
You are getting an error in unreleased code. It may be better if you stick to the released version rather than pulling directly from the development head. |
It looks like productKey is not always supported. Comment on #1149
|
Thank you. I used version 2024.11.4. This time the error did not pop up immediately, but something was happening. After trying to integrate using the application, a message appeared saying that the application does not provide IP and automatically went to manual configuration. Unfortunately, after entering the data, a login error. Register: custom_components.tuya_local.device Test protocol error 901: Network Error: Unable to Connect I checked the keys many times, but I am not sure about the node_id, it is not available anywhere in the portal, so I entered the uuid. |
|
You should leave the node_id blank if you are connecting directly to a WiFi device. node_id is only for subdevices that are connected via hubs. |
|
I also tried with empty node_id field, with local and external IP, it always ends with this error. This error comes from custom integration. Logger: custom_components.tuya_local.device Test protocol error 901: Network Error: Unable to Connect |
|
Device parameters downloaded from the portal. Maybe I'm doing something wrong, but I'm a fairly informed user. And this is what it looks like in HA. |
|
The only thing I can see is that you have left the protocol as auto, which might not always work. It would be better to find out what protocol version your device is. Also, your IP address is 192.168.2.x. If this is a different /24 than your Home Assistant server, then check that there is not a routing issue between the subnets. |
|
I have tried all protocol versions. :( |
|
You could try pairing it with the app again to get another local key issued. I see there is a # character in the current local key. There have been multiple reports from users suspecting "special characters in local keys", a specific problem has never been found, but if any character is likely to cause problems, the Python comment character would be high on the list. |
|
I've done this before, but I don't have any other ideas, so I'll try again. Maybe I could do it with the smart-life app instead of tuya smart? Would I have to connect the smart-life app to the developer portal then? It's also very strange that the standard tuya cloud integration shows feyree as unavailable and there are no entities. |
|
I created a new project, connected the device via the smart-life app and the error didn't pop up, but now I have these warnings:
I feel like I'm close. Can you support me a little more? :) Should device be in standard instruction set and device permision should be coverted to controllable device? I changed the product code in feyree_3phase_ev_charger.yaml but nothing changed.
Same warning occur: Logger: custom_components.tuya_local.config_flow Device matches None with quality of 0%. DPS: {"updated_at": 1733661198.971791, "102": 2268, "103": 2274, "104": 2296, "105": 0, "106": 0, "107": 0, "109": 0, "110": 121, "112": 0, "113": "Max32A", "114": 14, "115": 14, "116": 14, "117": 14, "118": 0, "119": 0, "120": "00:00:00", "121": "T:00H", "122": "D:00H", "123": false, "124": "WaitOperation", "125": 14} |
|
Now you are getting some log messages, showing that the basic communication is working. However your device appears to be incompatible with any of the implemented devices so far. |
|
So we need to add a completely new device to the integration? Do I have to do it myself or can I generate a set of commands from the tuya portal and you will be able to implement it? |
|
File a New Device request under Issues, giving the logs at the end of your comment above, and QueryThingsDataModel API result from the tuya developer portal. |
|
Done. Thank You. #2628 |
This is a Tuya EV charger, single phase 32a supports 85v to 264v. It uses Smart Life app, but it seems like other Tuya EV chargers use the same API (without confirming it)
link: https://www.aliexpress.com/item/1005005504929776.html?spm=a2g0o.order_list.order_list_main.48.4dbb1802z6vKSl
Log:
DPS:
{"updated_at": 1695764174.6401825,
"10": 0,
"101": "no_connect",
Amps: "102": 32,
"103": true,
"104": 0,
"106": 0,
Voltage "107": 229,
"108": 0,
"109": 0,
"110": 413,
"112": false,
"113": 0,
"114": 0}
https://github.com/make-all/tuya-local/issues/new?assignees=&labels=new+device&projects=&template=new-device.md&title=Request+support+for+%5Bdevice+description%5D
API:
{
"code": 28841002,
"msg": "No permissions. Your subscription to cloud development plan has expired.",
"success": false,
"t": 1695764750849,
"tid": "0f72c7925cb611ee8665fe445e07f2df"
}
DP’S:
Work State
Code 3
Type: Enum
{
"range": [
"charger_free",
"charger_insert",
"charger_free_fault",
"charger_wait",
"charger_charging",
"charger_pause",
"charger_end",
"charger_fault"
]
}
Fault
Code 10
Type: Bitmap.
{
"label": [
"ERR_UVP",
"ERR_OVP",
"ERR_OCP",
"ERR_PE",
"ERR_TEMP",
"ERR_CP",
"ERR_LEAK",
"ERR_RE_SCK",
"ERR_PE2",
"TEMP_PLUG",
"TEMP_PCB",
"TEMP_CORE",
"ESB",
"PE_SCK",
"LEAK_SCK",
"TEMP_SCK"
],
"maxlen": 16
}
Alarm Set 1
Code 11
Type: Raw
Unknown function
Alarm Set 2
Code 12
Type: Raw
Unkonwn function
Work Mode
Code 14
Type: Enum
{
"range": [
"charge_now",
"charge_pct",
"charge_energy",
"charge_schedule"
]
}
Balance Energy
Code 15
Type: Integer
{
"unit": "kW·h",
"min": 0,
"max": 99999999,
"scale": 3,
"step": 1
}
Clear Energy
Code 16
This will clear registered kwh displayed by the charger.
Type: Boolean
"{true,false}"
Switch:
Code 18
Type: Boolean
"{true,false}"
System Version
Code 23
Type: Boolean
"{true,false}"
Once Charge Energy
Code 25
Type: Integer
{
"unit": "kW·h",
"min": 1,
"max": 999999,
"scale": 2,
"step": 1
}
Online State
Code 27
Unknown - does not output value in tuya cloud
Equipment Status
Code 101
Connect/No Connect - meaning, if the charger detects and locks with the EV.
Set Charging Current
Code 102
8A/10A/13A/16A/25A/32Amp is what the manual says, but I’ve been able to change it in intervals of 1a from 8a to 32a
充电电流确认
Code 103
I think this is a confirmation of what selected Amp you’re currently using, or wish to set from listed above.
Delayed Charging
Code 104
In hours (devided by 10) - This is the option you set if you ie. want to delay charging by x hours.
VerificationSet
Code 105
Unknown function - My guess is that its a swhich you can enable if you want the charger to "learn" an RFID card, which have to be closed once done.
Energy
Code 106
In kwh. Ie. 0.00 kwh or 1.70 kwh used by the current charge session
Voltage
Code 107
In volt. Ie. 228V
Current
Code 108
Current current, ie. 0.00A (when not charging) or 15.8A (when charging)
Power
Code 109
In kwh. Ie. 0.00 kw or 5.60 kw
Temperature
Code 110
In Celsius, ie. 37.9 °C. This number needs to be devided by 10 since it spits out “379” for 37.9 degrees c
Set Charging Current
Code 111
8A/10A/13A/16A/25A/32Amp
Charging Selection
Code 112
Manual Stop charging / charging – like a switch
Time
Code 113
Delayed charging remaining (in hours, divided by 10) If you sat it at 4 hours beforehand, this will now show 400 or 399
Timed Charging
Code 114
Unknown
Other DP's with unkown DP_ID
Found these whilst browsing "Control Device with DP".
DeviceState
Type: Enum
{
"range": [
"no_connect",
"connect",
"charing",
"wait_rfid",
"finish",
"wait_charing",
"error"
]
}
Set32A
Type: Intiger
{
"unit": "A",
"min": 8,
"max": 32,
"scale": 0,
"step": 1
}
Set32Or16
Boolean
"{true,false}"
SetDelayTime
Type: Integer
{
"unit": "H",
"min": 0,
"max": 15,
"scale": 0,
"step": 1
}
IDVerificationSet
Type: Boolean
"{true,false}
Set16A
Type: Integer
{
"unit": "",
"min": 8,
"max": 16,
"scale": 0,
"step": 1
}
DeviceKwh
Type: Integer
{
"unit": "Kwh",
"min": 0,
"max": 10000,
"scale": 1,
"step": 1
}
InputVoltage
Type: Integer
{
"unit": "V",
"min": 0,
"max": 500,
"scale": 0,
"step": 1
}
OutCurrent
Type: Integer
{
"unit": "A",
"min": 0,
"max": 600,
"scale": 1,
"step": 1
}
DeviceKw
Type: Integer
{
"unit": "Kw",
"min": 0,
"max": 1000,
"scale": 1,
"step": 1
}
DeviceTemp
Type: Integer
{
"unit": " °C",
"min": -100,
"max": 1500,
"scale": 1,
"step": 1
}
SwipRfid ## note - this EV charger does not have RFID
Type: Boolean
"{true,false}"
SetDefineTime
Type: Integer
{
"unit": "H",
"min": 0,
"max": 15,
"scale": 0,
"step": 1
}
# Product ID
{
"code": 28841002,
"msg": "No permissions. Your subscription to cloud development plan has expired.",
"success": false,
"t": 1695765940186,
"tid": "d45d9d965cb811eebb19ce5fa22f6e19"
}
Link: https://www.aliexpress.com/item/1005005504929776.html?spm=a2g0o.order_list.order_list_main.48.4dbb1802z6vKSl
Extra things i had exported through the LocalKey extraction:
iconUrl https://images.tuyaeu.com/smart/icon/bay16226250696545rLI/35878abfb9cc339489fd3272154de112.png
verSw 2.5.2
MCU: v1.0.0
productid hytatexziwaifxj1
Product "菲尔雷交流充电盒"
It updates voltage and state every 4 seconds
The text was updated successfully, but these errors were encountered: