search

DrozmotiX / ioBroker.esphome

Control your ESP8266/ESP32 with simple yet powerful configuration files created and managed by ESPHome
MIT License
30 stars 23 forks source link

unable to add device manually #174

Closed volkerrichert closed 11 months ago

volkerrichert commented 11 months ago

Wenn i try to add a new device manually, the console logs "Add device button executed", but nothing happens.

DutchmanNL commented 11 months ago

Wenn i try to add a new device manually, the console logs "Add device button executed", but nothing happens.

  • Adapter version: 0.3.1
  • admin 6.12
  • JS-Controller version: 4.0.12
  • Node version: 18.18.2

cannot reproduce, are u sure the ip and password (must be the API password) is correct ?

volkerrichert commented 11 months ago

yes, i'm sure. i tried multiple times. I'll crosscheck logs.

DutchmanNL commented 11 months ago

yes, i'm sure. i tried multiple times. I'll crosscheck logs.

yes please, I will need logging data/debug to see what's going wrong here as on my side all works fine :(

DutchmanNL commented 11 months ago

@volkerrichert are u sure the adapter is running ? I can reproduce this issue only if the adapter instance is not active/running so I thin the issue is somehow related to that ?

volkerrichert commented 11 months ago

ok, the new device seems to be offline, maybe so wifi issues... but when i try to add it, i'll see messages like "ESPHome error handling issue 192.168.120.60 TypeError: Cannot read properties of undefined (reading 'ip')"

DutchmanNL commented 11 months ago

ok, the new device seems to be offline, maybe so wifi issues... but when i try to add it, i'll see messages like "ESPHome error handling issue 192.168.120.60 TypeError: Cannot read properties of undefined (reading 'ip')"

ah thank you, here an error handling is missing will fix that. and indeed an offline device cannot be added device must be online to do that to initialise

volkerrichert commented 11 months ago

ok, i got a message now. But if i type e.g. a wrong IP, i'm not able to delete that entry. It's not displayed but log will be "spammed" with "device unreachable". I have to restart the adapter. Can this be fixed somehow? Maybe a list of "unreachable devices" oder dummy entry ("unknown" values).

DutchmanNL commented 11 months ago

ok, i got a message now. But if i type e.g. a wrong IP, i'm not able to delete that entry. It's not displayed but log will be "spammed" with "device unreachable". I have to restart the adapter. Can this be fixed somehow? Maybe a list of "unreachable devices" oder dummy entry ("unknown" values).

If you Like, a complete new way of managing devices will be introduced soon, currently only wled & enocean have this implemented and it's in alpha state (but we need testing feedback 😅)

You can support us by installing the "device manager" from git & latest version of wled from git (both versions not released to npm/latest yet) and try to manage (add/remove) a device

@Jey-Cee & would appreciate your feedback

DutchmanNL commented 11 months ago

Link to repository https://github.com/Jey-Cee/ioBroker.device-manager

DutchmanNL commented 11 months ago

please try v0.4.1-beto.0 from git

volkerrichert commented 11 months ago

i installed device-manager & 0.4.1 BETA, but i can't see any differences.

log still shows multiple EHOSTUNREACH devices isn't show in adapter setting device manager doesn't show anything. No instance is selectable.

DutchmanNL commented 11 months ago

log still shows multiple EHOSTUNREACH

please share the logs otherwise I cannot help

host unreach means device is not reachable by ip

device manager doesn't show anything. No instance is selectable.

apologies I made a mistake, this comment was for an WLED issue not ESPHome

volkerrichert commented 11 months ago

Yes, i know. That device ist bricked with the last flashing. Sonoff Basics seems to be fragile but it's build in a magic mirror, so not that easy to remove and flash by serial.

All i got in logs is:

esphome.0 | 2023-11-05 18:07:00.424 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:06:51.868 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:06:27.416 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:06:18.860 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:05:54.408 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:05:45.852 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:05:21.400 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:05:12.844 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:04:48.392 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:04:39.836 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:04:15.384 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:04:06.828 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:03:42.378 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:03:33.804 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053 esphome.0 | 2023-11-05 18:03:09.372 | error | ESPHome client 192.168.120.60 Error: connect EHOSTUNREACH 192.168.120.60:6053

volkerrichert commented 11 months ago

and maybe, i'll install the git version of WLED and give DM a try. Maybe I'll add support in my adapers