Nspanel pro and ewelink addon to homeassistant

NSPanel Pro
,
1

Hi There
Im using nspanel pro and ewelink smart home addon to homeassistant, everything is working fine, the first one og two days. then the nspanel and ewelink app on my phone, is begining to write errors. Nspanel pro is writing “device offline” when im trying to turnon light, and the app is writing “error please try again”

If im reloading the addon everything is working again for a day og two… :frowning:

Im getting some errors in the addon log file:
2023-07-31T17:27:59.699Z [ERROR] getDataSync: disabled.json → abf8001fbc no data
2023-07-31T17:27:59.699Z [ERROR] getDataSync: disabled.json → 10018935e0 no data
2023-07-31T17:27:59.699Z [ERROR] getDataSync: disabled.json → 1000044b7e no data
2023-07-31T17:27:59.700Z [ERROR] getDataSync: disabled.json → 1000044bc2 no data
2023-07-31T17:27:59.700Z [ERROR] getDataSync: disabled.json → 1000805807 no data
2023-07-31T17:27:59.710Z [ERROR] getDataSync: diy.json → no data
2023-07-31T17:28:17.994Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:30:17.996Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:32:05.243Z [INFO] HA emit call_service event: {“domain”:“homeassistant”,“service”:“reload_all”,“service_data”:{}}
2023-07-31T17:32:05.243Z [ERROR] getDataSync: diy.json → no data
2023-07-31T17:32:05.244Z [INFO] SSE closed
2023-07-31T17:32:05.311Z [INFO] HA emit call_service event: {“domain”:“person”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.312Z [INFO] HA emit call_service event: {“domain”:“conversation”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.313Z [INFO] HA emit call_service event: {“domain”:“timer”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.313Z [INFO] HA emit call_service event: {“domain”:“input_datetime”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.314Z [INFO] HA emit call_service event: {“domain”:“input_boolean”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.314Z [INFO] HA emit call_service event: {“domain”:“input_button”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.315Z [INFO] HA emit call_service event: {“domain”:“script”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.315Z [INFO] HA emit call_service event: {“domain”:“input_select”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.315Z [INFO] HA emit call_service event: {“domain”:“schedule”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.316Z [INFO] HA emit call_service event: {“domain”:“input_number”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.316Z [INFO] HA emit call_service event: {“domain”:“scene”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.317Z [INFO] HA emit call_service event: {“domain”:“mqtt”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.317Z [INFO] HA emit call_service event: {“domain”:“input_text”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.318Z [INFO] HA emit call_service event: {“domain”:“zone”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.318Z [INFO] HA emit call_service event: {“domain”:“automation”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.320Z [INFO] HA emit call_service event: {“domain”:“homekit”,“service”:“reload”,“service_data”:{}}
2023-07-31T17:32:05.320Z [INFO] HA emit call_service event: {“domain”:“homeassistant”,“service”:“reload_core_config”,“service_data”:{}}
2023-07-31T17:32:05.320Z [INFO] HA emit call_service event: {“domain”:“frontend”,“service”:“reload_themes”,“service_data”:{}}
2023-07-31T17:32:05.321Z [INFO] HA emit call_service event: {“domain”:“homeassistant”,“service”:“reload_custom_templates”,“service_data”:{}}
2023-07-31T17:32:17.999Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → ac0800683e no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → ac08006689 no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → ac0800668a no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → abf8001fbc no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → 10018935e0 no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → 1000044b7e no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → 1000044bc2 no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: disabled.json → 1000805807 no data
2023-07-31T17:32:18.777Z [ERROR] getDataSync: diy.json → no data
2023-07-31T17:34:15.973Z [ERROR] getDataSync: disabled.json → ac0800683e no data
2023-07-31T17:34:15.973Z [ERROR] getDataSync: disabled.json → ac08006689 no data
2023-07-31T17:34:15.973Z [ERROR] getDataSync: disabled.json → ac0800668a no data
2023-07-31T17:34:15.974Z [ERROR] getDataSync: disabled.json → abf8001fbc no data
2023-07-31T17:34:15.974Z [ERROR] getDataSync: disabled.json → 10018935e0 no data
2023-07-31T17:34:15.974Z [ERROR] getDataSync: disabled.json → 1000044b7e no data
2023-07-31T17:34:15.974Z [ERROR] getDataSync: disabled.json → 1000044bc2 no data
2023-07-31T17:34:15.974Z [ERROR] getDataSync: disabled.json → 1000805807 no data
2023-07-31T17:34:15.974Z [ERROR] getDataSync: diy.json → no data
2023-07-31T17:34:18.000Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:34:19.479Z [INFO] start getHaDeviceList()
2023-07-31T17:34:36.042Z [INFO] HA emit call_service event: {“domain”:“light”,“service”:“turn_on”,“service_data”:{“entity_id”:“light.stue”}}
2023-07-31T17:34:36.043Z [ERROR] getDataSync: diy.json → no data
2023-07-31T17:34:36.043Z [ERROR] getDataSync: diy.json → no data
2023-07-31T17:34:36.045Z [INFO] SSE closed
2023-07-31T17:34:36.046Z [INFO] SSE closed
2023-07-31T17:34:38.628Z [INFO] HA emit call_service event: {“domain”:“light”,“service”:“turn_off”,“service_data”:{“entity_id”:“light.stue”}}
2023-07-31T17:36:18.002Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:38:18.005Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:40:18.008Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:40:49.781Z [INFO] HA emit call_service event: {“domain”:“update”,“service”:“install”,“service_data”:{“entity_id”:“update.studio_code_server_update”,“backup”:true}}
2023-07-31T17:42:18.012Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:44:18.013Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:46:18.019Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:48:18.023Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:50:18.025Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:52:18.026Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:54:18.029Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:56:18.030Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T17:58:18.033Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:00:18.036Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:02:18.038Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:04:18.040Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:06:18.040Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:08:18.042Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:10:18.044Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:12:18.044Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:14:18.046Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:16:18.047Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:18:18.049Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:20:18.051Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:22:18.052Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:24:18.053Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:26:18.054Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:28:18.056Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:30:18.056Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:32:18.058Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:34:18.062Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:36:18.064Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:38:18.065Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:40:18.069Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:42:18.071Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:44:18.074Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:46:18.077Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:48:18.080Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:50:18.083Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:52:18.085Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:54:18.086Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:56:18.089Z [INFO] HA-WS heart beat result: “pong”
2023-07-31T18:58:18.092Z [INFO] HA-WS heart beat result: “pong”

2

I am trying to install it for the first time, already have the repository, when I press on “Install”, I get an error window with this:

Docker build failed for f4f71350/aarch64-addon-ewelink_smart_home_slug:1.4.3 (exit code 1). Build output: #0 building with “default” instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: #1 transferring dockerfile: 403B done #1 DONE 0.4s #2 [internal] load metadata for Docker Hub Container Image Library | App Containerization #2 DONE 0.4s #3 [internal] load .dockerignore #3 transferring context: #3 transferring context: 2B done #3 DONE 0.8s #4 [1/7] FROM Docker Hub Container Image Library | App Containerization #4 CACHED #5 [internal] load build context #5 transferring context: 4.23MB 0.7s done #5 DONE 0.9s #6 [2/7] RUN apt-get update && apt-get install -y python build-essential #6 1.235 Ign:1 Index of /debian buster InRelease #6 1.252 Ign:2 http://deb.debian.org/debian-security buster/updates InRelease #6 1.267 Ign:3 Index of /debian buster-updates InRelease #6 1.281 Err:4 Index of /debian buster Release #6 1.281 404 Not Found [IP: 146.75.118.132 80] #6 1.297 Err:5 http://deb.debian.org/debian-security buster/updates Release #6 1.297 404 Not Found [IP: 146.75.118.132 80] #6 1.312 Err:6 Index of /debian buster-updates Release #6 1.312 404 Not Found [IP: 146.75.118.132 80] #6 1.332 Reading package lists… #6 1.363 E: The repository ‘Index of /debian buster Release’ does not have a Release file. #6 1.363 E: The repository ‘http://deb.debian.org/debian-security buster/updates Release’ does not have a Release file. #6 1.363 E: The repository ‘Index of /debian buster-updates Release’ does not have a Release file. #6 ERROR: process “/bin/sh -c apt-get update && apt-get install -y python build-essential” did not complete successfully: exit code: 100 ------ > [2/7] RUN apt-get update && apt-get install -y python build-essential: 1.281 Err:4 Index of /debian buster Release 1.281 404 Not Found [IP: 146.75.118.132 80] 1.297 Err:5 http://deb.debian.org/debian-security buster/updates Release 1.297 404 Not Found [IP: 146.75.118.132 80] 1.312 Err:6 Index of /debian buster-updates Release 1.312 404 Not Found [IP: 146.75.118.132 80] 1.332 Reading package lists… 1.363 E: The repository ‘Index of /debian buster Release’ does not have a Release file. 1.363 E: The repository ‘http://deb.debian.org/debian-security buster/updates Release’ does not have a Release file. 1.363 E: The repository ‘Index of /debian buster-updates Release’ does not have a Release file. ------ e[33m1 warning found (use docker --debug to expand): e[0m - JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 13) Dockerfile:6 -------------------- 4 | FROM node:14-slim 5 | ENV CK_API_ENV=prod 6 | >>> RUN apt-get update && apt-get install -y python build-essential 7 | RUN mkdir -p /workspace/node_modules 8 | COPY [“./dist”, “./package.json”, “/workspace/”] -------------------- ERROR: failed to build: failed to solve: process “/bin/sh -c apt-get update && apt-get install -y python build-essential” did not complete successfully: exit code: 100

1 Like
3

Thank you very much for using NSPanel Pro and very sorry for the issue.

So you want to use eWeLink Smart Home Add-on to export devices to Home Assistant? And you met issue when installing this Add-on?

Could you please tell us the exact URL you are using for eWeLink Smart Home Add-on?

4
5

today I tried again and it worked

6

Great! I’d also like to tell you that we (iHost Open Source Project) will take over this CoolKit-Technologies/ha-addon in order to add new features and new devices support.

Home Assistant users will have much better eWeLink devices support in the coming months.

By the way, SonoffLAN from AlexxIT is doing a pretty good job in this scenario.

1 Like
7

Why not support SonoffLAN? Invest in developers who can work with AlexxT Alternatively you should consider to develop a proper ITEAD, or Ewelink Integration instead of an add on.

SonoffLAN is iextremely good and deserves support.

8

SonoffLAN is iextremely good and deserves support.

I totally agree. SONOFF even tried to offer a business contract to AlexxIT, but he wasn’t interested.

Alternatively you should consider to develop a proper ITEAD, or Ewelink Integration instead of an add on.

In most cases, Integration is better than Add-on, there is no doubt about it. The reason that we are developing Add-on instead of Integration is simply because I only have a small team, and my developers are pretty good at JavaScript, not Python. You know, we have to do with what we have, not what we desire.

I am hoping the future success of NSPanel Pro, ZBBridge-U, and iHost will make my boss willing to give my team more resources, then I can hire Python developers.

Note: we are definitely not anti-Integration.

1 Like
9

This is great! The add-on is still quite limited in functionality at the moment..

SonoffLAN - and AlexxIT himself - are absolutely fantastic. He even added the NSPanel Pro support in a single evening by remotely testing on one of my devices.. :slight_smile: However, some of us (myself included) have started encountering strange issues recently. It might be related to the new v4.x.x release, I’m not sure, but unfortunately AlexxIT seems to be currently busy with other projects.

Does this mean we’ll eventually be able to expose all Sonoff devices to Home Assistant through the Matter Bridge, without needing the SonoffLAN integration or the official eWeLink add-on?

10

Does this mean we’ll eventually be able to expose all Sonoff devices to Home Assistant through the Matter Bridge, without needing the SonoffLAN integration or the official eWeLink add-on?

Matter Bridge is for other Matter ecosystems except Home Assistant. For Home Assistant, we’ll export Zigbee devices and NSPanel Pro itself using Home Assistant’s MQTT Discovery protocol which provides even better experience.

NSPanel Pro firmware v4.1.0 already supports Export Zigbee devices to Home Assistant, and v4.3.0 will support Export NSPanel Pro itself to Home Assistant. You can refer to NSPanel Pro Roadmap and Co-Created Future for the details.

1 Like
11

I’m not a technical professional, so I may not fully understand all the technologies involved and could be missing something - but why exclude Home Assistant? Wouldn’t it be even easier to expose all devices through the NSPanel directly, instead of developing add-ons or relying on third-party integrations?

Yes, I successfully exposed my Zigbee devices via MQTT Discovery and it worked great. I then disabled it because I still need SonoffLAN (or the upcoming updated eWeLink add-on) to expose all my Wi-Fi and eWeLink-Remote devices to HA. Or am I misunderstanding something or doing something wrong?

12

Wouldn’t it be even easier to expose all devices through the NSPanel directly, instead of developing add-ons or relying on third-party integrations?

For exporting devices to Home Assistant, MQTT Discovery protocol is much better than Matter Bridge.

I then disabled it because I still need SonoffLAN (or the upcoming updated eWeLink add-on) to expose all my Wi-Fi and eWeLink-Remote devices to HA. Or am I misunderstanding something or doing something wrong?

There is nothing wrong with your setup. You can continue using SonoffLAN if it works for you.

In our plans, NSPanel Pro works better compared to SonoffLAN or eWeLink Smart Home Add-on in following use cases:

  • Fully local: you don’t relay on eWeLink cloud to export/control NSPanel Pro and its Zigbee devices (and eWeLink-Remote devices, BT-Home devices in the future).
  • Full capability: thanks to Home Assistant’s MQTT Discovery protocol, we could export all of the capabilities of NSPanel Pro itself and its Zigbee devices to HA.

However, NSPanel Pro will not export eWeLink Wi-Fi devices and Zigbee devices from other eWeLink Hubs, such as ZBBridge-U, to Home Assistant. So for your usage scenario, NSPanel Pro alone may not be enough. But I think you could use NSPanel Pro and eWeLink Smart Home Add-on simultaneously to get the best of both methods.

1 Like