UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Codierknecht]

@scrounger sagte in Test Adapter Unifi Network:

Sollte mit version 1.1.2 behoben sein.

Nicht wirklich

unifi-network.0
2025-10-02 15:12:52.673	error	[login]: Login to the Unifi-Network controller API failed! (host: 192.168.179.13:8443, site: D*****V)
unifi-network.0
2025-10-02 15:12:52.672	error	[NetworkApi.loginController] error: TypeError: selfHostedCookie.find is not a function, stack: TypeError: selfHostedCookie.find is not a function at NetworkApi.loginController (file:///opt/iobroker/node_modules/iobroker.unifi-network/build/lib/api/network-api.js:139:57) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async NetworkApi.login (file:///opt/iobroker/node_modules/iobroker.unifi-network/build/lib/api/network-api.js:74:34) at async UnifiNetwork.login (file:///opt/iobroker/node_modules/iobroker.unifi-network/build/main.js:343:41) at async UnifiNetwork.establishConnection (file:///opt/iobroker/node_modules/iobroker.unifi-network/build/main.js:310:17) at async UnifiNetwork.onReady (file:///opt/iobroker/node_modules/iobroker.unifi-network/build/main.js:85:21)

[Scrounger]

@codierknecht
teste mal die v1.1.3

[emil70]

Teste das gerade auch. Danke für den Adapter

Blöde Frage:

[updateClients]: Discovered 152 disconnected clients (clients: 101, guests: 0, vpn: 0, blacklisted: 0)

Wo finde ich die in der UniFi-OS 4.4.2 Netzwerk 9.4.19
damit ich die mal löschen kann

[crunchip]

@scrounger sagte in Test Adapter Unifi Network:

dass ich nur das intergriere was ich wirklich brauche

ist das auch mit geplant?

[onNetworkEvent]: not implemented event (key: EVT_IPS_IpsAlert,) - Please report this to the developer and creating an issue on github!

[Scrounger]

@crunchip sagte in Test Adapter Unifi Network:

@scrounger sagte in Test Adapter Unifi Network:

dass ich nur das intergriere was ich wirklich brauche

ist das auch mit geplant?

[onNetworkEvent]: not implemented event (key: EVT_IPS_IpsAlert,) - Please report this to the developer and creating an issue on github!

Da jede HW andere events haben kann, kenn ich natürlich nicht alle.
Wie im log beschrieben, ein issue aufmachen mit allen daten aus der meldung, ggf. vertrauliches infos abändern!

Dann schau ich mir an, ob es sinn macht dieses event zu implementieren oder ob es auf die ignore list kommt.

[crunchip]

@scrounger ich brauch dies nicht,wollt eher damit den Hinweis geben, daß dies auftaucht. Kann aber wenn gewünscht, trotzdem eins erstellen

[Scrounger]

@crunchip

@crunchip
Ja wäre super weil sonst komnt halt immer Mal wieder diese warn Meldung im Log.

[Codierknecht]

@scrounger sagte in Test Adapter Unifi Network:

teste mal die v1.1.3

Die gute Nachricht: Die Instanz wird grün.
Die schlechte: Ich erhalte keine Daten

FYI: Es läuft hier nur ein Unifi-AP-Pro. Also ausschließlich WLAN-Clients und kein Unifi-OS.

unifi-network.0
	2025-10-05 17:55:09.066	info	[onReady]: WebSocket listener to realtime API successfully started
unifi-network.0
	2025-10-05 17:55:09.058	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
unifi-network.0
	2025-10-05 17:55:09.047	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
unifi-network.0
	2025-10-05 17:55:09.020	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
unifi-network.0
	2025-10-05 17:55:08.920	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:55:05.886	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:55:02.841	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:54:59.806	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:54:56.772	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:54:53.740	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:54:50.688	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:54:47.654	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.
unifi-network.0
	2025-10-05 17:54:44.610	info	[login]: WebSocket connection to realtime API successfully established
unifi-network.0
	2025-10-05 17:54:44.587	debug	[NetworkApi.loginController] login to self hosted UniFi controller successful.
unifi-network.0
	2025-10-05 17:54:44.263	info	[login]: Logged in successfully to the Unifi-Network controller (host: 192.168.179.13:8443, site: D*****V, isUnifiOs: false)
unifi-network.0
	2025-10-05 17:54:44.262	debug	[NetworkApi.loginController] login to self hosted UniFi controller successful.
unifi-network.0
	2025-10-05 17:54:43.974	debug	[NetworkApi.logout] Logging out and clearing credentials.
unifi-network.0
	2025-10-05 17:54:43.957	info	starting. Version 1.1.3 (non-npm: Scrounger/ioBroker.unifi-network#fab63502974c2b23b621ebc96844f9d5bc0c61ef) in /opt/iobroker/node_modules/iobroker.unifi-network, node: v22.20.0, js-controller: 7.0.7
unifi-network.0
	2025-10-05 17:54:43.896	debug	States connected to redis: 0.0.0.0:9010
unifi-network.0
	2025-10-05 17:54:43.846	debug	States create User PubSub Client
unifi-network.0
	2025-10-05 17:54:43.846	debug	States create System PubSub Client
unifi-network.0
	2025-10-05 17:54:43.841	debug	Redis States: Use Redis connection: 0.0.0.0:9010
unifi-network.0
	2025-10-05 17:54:43.829	debug	Objects connected to redis: 0.0.0.0:9011
unifi-network.0
	2025-10-05 17:54:43.827	debug	Objects client initialize lua scripts
unifi-network.0
	2025-10-05 17:54:43.812	debug	Objects create User PubSub Client
unifi-network.0
	2025-10-05 17:54:43.812	debug	Objects create System PubSub Client
unifi-network.0
	2025-10-05 17:54:43.811	debug	Objects client ready ... initialize now
unifi-network.0
	2025-10-05 17:54:43.798	debug	Redis Objects: Use Redis connection: 0.0.0.0:9011
host.iobroker
	2025-10-05 17:54:43.193	info	instance system.adapter.unifi-network.0 in version "1.1.3" (non-npm: Scrounger/ioBroker.unifi-network#fab63502974c2b23b621ebc96844f9d5bc0c61ef) started with pid 3818642
host.iobroker
	2025-10-05 17:54:42.900	info	"system.adapter.unifi-network.0" enabled

Meine Einstellungen:

Vielleicht korrigierts Du bei Gelegenheit auch den Fauxpas der automatischen Übersetzung

[Rene55]

@scrounger Ist das auch wichtig, weil "Please report this to the developer "?

Spoiler

warn	[onNetworkEvent]: not implemented event (key: EVT_IPS_IpsAlert,) - 
Please report this to the developer and creating an issue on github! 
(
meta: {
   "rc":"ok",
   "message":"events"
   }, 
data: {
   "dest_ip":"192.168.172.110",
   "dest_port":80,
   "dst_mac":"bc:24:11:4f:45:38",
   "event_type":"alert",
   "flow":{
   	"bytes_toclient":0,
   	"bytes_toserver":66,
   	"pkts_toclient":0,
   	"pkts_toserver":1,
   	"start":"2025-10-03T22:07:34.728843 0200"
   	},
   "flow_id":211562254442251,
   "host":"usg-sensor",
   "in_iface":"eth4",
   "metadata":{
   	"flowbits":["ET.Evil","ET.DshieldIP"]
   	},
   "out_iface":"lo",
   "proto":"TCP",
   "src_ip":"204.76.203.212",
   "src_mac":"9e:05:d6:b5:df:28",
   "src_port":35936,
   "timestamp":1759522054,
   "ubnt":{
   	"affected_products":"",
   	"classtype":"",
   	"counterpart_hostnames":[],
   	"cve_reference":"",
   	"description":"",
   	"event_version":"3.1",
   	"reference_url":[],
   	"signature_type":"ET",
   	"ubnt_category":"DSHIELD"
   },
   "usgip":"91.7.160.82",
   "unique_alertid":"7-2025-10-03T22:07:34.728843 0200",
   "srcipGeo":{
   	"address":"204.76.203.212",
   	"asn":51396,
   	"organization":"Pfcloud UG",
   	"isp":"Pfcloud UG",
   	"country_code":"NL",
   	"country_name":"The Netherlands",
   	"continent_code":"EU",
   	"city":"Eygelshoven",
   	"latitude":50.8897,
   	"longitude":6.0563,
   	"accuracy":20,
   	"timezone":"Europe/Amsterdam"
   },
   "dstipGeo":{
   	"address":"192.168.172.110",
   	"asn":0,
   	"organization":"",
   	"isp":"",
   	"country_code":"",
   	"country_name":"",
   	"continent_code":"",
   	"city":"",
   	"latitude":0,
   	"longitude":0,
   	"accuracy":0,
   	"timezone":""
   },
   "usgipGeo":{
   	"address":"91.7.160.82",
   	"asn":3320,
   	"organization":"Deutsche Telekom AG",
   	"isp":"VipNet Telecom",
   	"country_code":"DE",
   	"country_name":"Germany",
   	"continent_code":"EU",
   	"city":"Köln",
   	"latitude":50.9427,
   	"longitude":6.9584,
   	"accuracy":5,
   	"timezone":"Europe/Berlin"
   },
   "srcipCountry":"NL",
   "srcipASN":"51396 Pfcloud UG",
   "usgipCountry":"DE",
   "usgipASN":"3320 Deutsche Telekom AG",
   "catname":"DSHIELD",
   "inner_alert_action":"allowed",
   "inner_alert_category":"Misc Attack",
   "inner_alert_gid":1,
   "inner_alert_metadata":{
   	"affected_product":["Any"],
   	"attack_target":["Any"],
   	"created_at":["2010_12_30"],
   	"deployment":["Perimeter"],
   	"signature_severity":["Major"],
   	"tag":["Dshield"],
   	"ubnt_category":["DSHIELD"],
   	"updated_at":["2025_10_02"]
   },
   "inner_alert_rev":7515,
   "inner_alert_severity":2,
   "inner_alert_signature":"ET DROP Dshield Block Listed Source group 1",
   "inner_alert_signature_id":2402000,"key":"EVT_IPS_IpsAlert",
   "subsystem":"www",
   "is_negative":true,
   "site_id":"667fd2400487b63810d07718",
   "time":1759522054000,
   "datetime":"2025-10-03T20:07:34Z",
   "msg":"IPS Alert 2: Misc Attack. 	
   		Signature ET DROP Dshield Block Listed Source group 1. 
   		From: 204.76.203.212:35936, 
   		to: 192.168.172.110:80, 
   		protocol: TCP",
   "_id":"68e02ddd9c5b50427590ff3d"
   }
)

[crunchip]

@rene55 mach deine privaten Daten raus

[lobomau]

@Scrounger noch habe ich den Adapter nicht am Laufen. Bisher hatte ich den Unifi-Adapter am Laufen.
Ich habe einen "Cloud Gateway Ultra". Ich bin davon ausgegangen, dass dies ein Unifi OS ist. Es läuft Version Network 9.4.19, UniFi OS 4.3.9. Einloggen kann ich mich über 192.168.1.1. Ich gebe da keinen Port zusätzlich an. Der andere Adapter hingegen läuft auf port 8443. Muss ich den hier auch einstellen? Das geht ja nur ohne "ist Unifi OS". Und habe ich "default" controller site? Wie finde ich es heraus?

Edit: nee, der andere Adapter hat auch keinen Port vorgewählt... es erscheint geschwächt 8443 (hatte ich früher mal als container laufen)
Edit2: ist wohl default:

unifi-network.0
2025-10-05 21:11:15.517	info	[onReady]: WebSocket listener to realtime API successfully started

unifi-network.0
2025-10-05 21:11:15.503	error	[login]: Login to the Unifi-Network controller API failed! (host: 192.168.1.1, site: default)

unifi-network.0
2025-10-05 21:11:15.502	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots.

unifi-network.0
2025-10-05 21:11:12.184	info	starting. Version 1.1.3 (non-npm: Scrounger/ioBroker.unifi-network#fab63502974c2b23b621ebc96844f9d5bc0c61ef) in /opt/iobroker/node_modules/iobroker.unifi-network, node: v22.20.0, js-controller: 7.0.7

[Rene55]

@crunchip Thanks, aber die Daten sind schon verfälscht.

[Scrounger]

@codierknecht
also ich hab jetzt extra mal einen self hosted controller in einem proxmox lxc aufgesetzt und auch ne AP dran gehängt.
Läuft bei mir ohne probleme. Evtl. wird da irgendwas geblockt?
Test mal die v1.1.4, hab ein paar debug info mit eingebaut, damit man sieht was er da genau macht. Am besten den Adapter davor komplett mal löschen.
Und bitte info's nach dem test im issue auf github posten!

@lobomau
Test mal die v1.1.4, UniFi OS oder self hosted wird jetzt automatusch erkannt. Am besten den Adapter davor komplett mal löschen.
Wenn noch immer Probleme bestehen, bitte issue auf github erstellen

[lobomau]

Edit. ok... zuerst code eintragen und hinterher den Codeknopf drüber. Hab ich sonst andersrum gemacht...
@scrounger haben die bei Github etwas geändert? Sieht in der Preview nicht nach Code aus:

[Scrounger]

@lobomau
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks

[Codierknecht]

@scrounger sagte in Test Adapter Unifi Network:

Test mal die v1.1.4, hab ein paar debug info mit eingebaut, damit man sieht was er da genau macht

unifi-network.0
2025-10-06 11:25:53.661	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/device?separateUnmanaged=false&includeTrafficUsage=false)
unifi-network.0
2025-10-06 11:25:50.633	info	[login]: WebSocket connection to realtime API successfully established
unifi-network.0
2025-10-06 11:25:50.630	info	[login]: Logged in successfully to the Unifi-Network controller (host: 192.168.179.13:8443, site: D*****V, isUnifiOs: false)
unifi-network.0
2025-10-06 11:25:50.629	debug	[NetworkApi.loginController] login to self hosted UniFi controller successful.
unifi-network.0
2025-10-06 11:25:50.302	debug	[NetworkApi.logout] Logging out and clearing credentials.
unifi-network.0
2025-10-06 11:25:50.292	debug	[NetworkApi.logout] Logging out and clearing credentials.
unifi-network.0
2025-10-06 11:25:50.292	warn	[aliveChecker]: No connection to the Unifi-Network controller -> restart connection (retries: 0, no data since 55s)
unifi-network.0
2025-10-06 11:25:20.281	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
unifi-network.0
2025-10-06 11:25:20.261	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
unifi-network.0
2025-10-06 11:25:20.231	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
unifi-network.0
2025-10-06 11:25:20.120	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/wlan/enriched-configuration)
unifi-network.0
2025-10-06 11:25:17.100	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/wlan/enriched-configuration)
unifi-network.0
2025-10-06 11:25:14.060	debug	[createOrUpdateChannel]: creating channel 'wlan'
unifi-network.0
2025-10-06 11:25:14.053	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/clients/history?includeUnifiDevices=true&withinHours=0)
unifi-network.0
2025-10-06 11:25:11.024	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/clients/history?includeUnifiDevices=true&withinHours=0)
unifi-network.0
2025-10-06 11:25:07.992	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/clients/active?includeTrafficUsage=false&includeUnifiDevices=true)
unifi-network.0
2025-10-06 11:25:04.964	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/clients/active?includeTrafficUsage=false&includeUnifiDevices=true)
unifi-network.0
2025-10-06 11:25:01.941	debug	[createOrUpdateChannel]: creating channel 'clients'
unifi-network.0
2025-10-06 11:25:01.939	debug	[createOrUpdateChannel]: creating channel 'clients.vpn'
unifi-network.0
2025-10-06 11:25:01.937	debug	[createOrUpdateChannel]: creating channel 'clients.guests'
unifi-network.0
2025-10-06 11:25:01.934	debug	[createOrUpdateChannel]: creating channel 'clients.users'
unifi-network.0
2025-10-06 11:25:01.929	debug	[createOrUpdateChannel]: creating channel 'devices'
unifi-network.0
2025-10-06 11:25:01.927	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/device?separateUnmanaged=false&includeTrafficUsage=false)
unifi-network.0
2025-10-06 11:24:58.905	error	[NetworkApi._retrieve] Unable to connect to the Network controller. This is temporary and may occur during device reboots (url: https://192.168.179.13:8443/v2/api/site/D*****V/device?separateUnmanaged=false&includeTrafficUsage=false)
unifi-network.0
2025-10-06 11:24:55.850	info	[login]: WebSocket connection to realtime API successfully established
unifi-network.0
2025-10-06 11:24:55.836	debug	[NetworkApi.loginController] login to self hosted UniFi controller successful.
unifi-network.0
2025-10-06 11:24:55.565	info	[login]: Logged in successfully to the Unifi-Network controller (host: 192.168.179.13:8443, site: D*****V, isUnifiOs: false)
unifi-network.0
2025-10-06 11:24:55.564	debug	[NetworkApi.loginController] login to self hosted UniFi controller successful.
unifi-network.0
2025-10-06 11:24:55.325	debug	[NetworkApi.logout] Logging out and clearing credentials.
unifi-network.0
2025-10-06 11:24:55.325	debug	[NetworkApi.detectUnifiOs] self hosted controller detected
unifi-network.0
2025-10-06 11:24:55.325	debug	[NetworkApi.detectUnifiOs] detect self hosted controller repsonse: {"statusCode":302,"headers":{"location":"/manage","content-length":"0","date":"Mon, 06 Oct 2025 09:24:55 GMT","keep-alive":"timeout=30","connection":"keep-alive"},"trailers":{},"opaque":null,"body":{"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null}}}
unifi-network.0
2025-10-06 11:24:55.282	info	starting. Version 1.1.4 (non-npm: Scrounger/ioBroker.unifi-network) in /opt/iobroker/node_modules/iobroker.unifi-network, node: v22.20.0, js-controller: 7.0.7
unifi-network.0
2025-10-06 11:24:55.193	debug	States connected to redis: 0.0.0.0:9010
unifi-network.0
2025-10-06 11:24:55.137	debug	States create User PubSub Client
unifi-network.0
2025-10-06 11:24:55.136	debug	States create System PubSub Client
unifi-network.0
2025-10-06 11:24:55.131	debug	Redis States: Use Redis connection: 0.0.0.0:9010
unifi-network.0
2025-10-06 11:24:55.118	debug	Objects connected to redis: 0.0.0.0:9011
unifi-network.0
2025-10-06 11:24:55.116	debug	Objects client initialize lua scripts
unifi-network.0
2025-10-06 11:24:55.097	debug	Objects create User PubSub Client
unifi-network.0
2025-10-06 11:24:55.096	debug	Objects create System PubSub Client
unifi-network.0
2025-10-06 11:24:55.095	debug	Objects client ready ... initialize now
unifi-network.0
2025-10-06 11:24:55.082	debug	Redis Objects: Use Redis connection: 0.0.0.0:9011

Geht gleich auch noch an GH

[Codierknecht]

@Scrounger

Mit einer Site "default" klappt's dann auch. Issue habe ich geschlossen.

[Scrounger]

@codierknecht
Hab jetzt noch ne Prüfung eingebaut, die anzeigt welche Sites überhaupt verfügbar sind und bei falscher Eingabe ne Error Meldung wirft

[Codierknecht]

@scrounger

Die automatische Übersetzung hat wieder zugeschlagen

[Scrounger]

@codierknecht sagte in Test Adapter Unifi Network:

@scrounger

Die automatische Übersetzung hat wieder zugeschlagen

Tja da gibt's noch nen paar andere so klöpse drin
Wenn ihr mithelfen wollt dann erstellt nen PR mit korrigierten Übersetzungen.