Replies: 2 comments
-
It seems a network issue. But a better script would be: {
"c": {
"io": [
[[2, 15, 0, 12], 2],
[[13], 6],
[[5, 4], 1]
],
"l": 0,
"b": [[13, 5]]
},
"a": [
{
"t": 2,
"0": {
"r": [
[15, 0],
[2, 1]
]
},
"1": {
"r": [
[15, 1],
[2, 0]
]
},
"b": [
[13, 1]
],
"es": [
{
"t": 75,
"vf": 0.13334,
"cf": 0.01295,
"pf": 1.5312,
"dt": [5, 4, 12]
}
]
}
]
} |
Beta Was this translation helpful? Give feedback.
0 replies
-
Great! Used your updated MELPHAA config and now it works as it should! Thank you very much. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Detailed steps to reproduce it
I'm trying to get a GHome smart plug (https://www.amazon.se/dp/B09Q5K34NV?ref=ppx_yo2ov_dt_b_fed_asin_title) to work with HAA. I managed to OTA flash it with tuya-convert, and then reflash it to HAA through the Tasmota UI. I created a config based on the Tasmota config found here: https://templates.blakadder.com/ghome_EP2-A.html, and everything seems to work. The relay and status LED are both toggled when pressing the physical button.
The issue I'm having is that it doesn't work properly in the Home app. I can add the device without any issues, but the status in the Home app is reported as "Not responding". When checking the "HomeKit Server" status under Device -> HAA Services -> Settings in the HAA Manager app, it’s reported as Unknown. My other devices reports Ok.
Any tips on how to debug this? I've enabled network logging, but cannot see any errors in the log.
MEPLHAA Script
Used device
https://templates.blakadder.com/ghome_EP2-A.html
HAA version
12.14.5
Logs
Beta Was this translation helpful? Give feedback.
All reactions