Test Adapter enigma2 v1.2.x

[tritor]

@glasfaser
prefect, habs hinbekommen.
http:// 192.168.xx.xxx:80/picon/{enigma2.0.enigma2.CHANNEL_SERVICEREFERENCE_NAME}.png als Bild unter Symbol.

[Smart81]

Hallo Leute,

Bekommt man den Adapter noch irgendwie auf aktuelle Iobroker Versionen installiert?

Habe den Link: https://github.com/Matten-Matten/ioBroker.enigma2 ausprobiert , aber der bleibt hier hängen:

$ iobroker url https://github.com/Matten-Matten/ioBroker.enigma2 --host iobroker

install Matten-Matten/ioBroker.enigma2#4198fa2049f66bb5eb274a24ae64f4fa3149065f

NPM version: 6.14.16

Installing Matten-Matten/ioBroker.enigma2#4198fa2049f66bb5eb274a24ae64f4fa3149065f... (System call)

Jemand eine Idee?

[Glasfaser]

@smart81 sagte in Test Adapter enigma2 v1.2.x:

Hallo Leute,
Bekommt man den Adapter noch irgendwie auf aktuelle Iobroker Versionen installiert?

Ja bekommt man ... liegt aber daran .....

siehe hier :
https://forum.iobroker.net/topic/55050/adapter-update-über-github-funktioniert-nicht/21?_=1653495678402

[Smart81]

@glasfaser

Habe den Workarround probiert:

https://github.com/ioBroker/ioBroker.admin/issues/1471

Hat aber leider nicht funktioniert

Hängt immer noch an genannter Stelle

Diginix created this issue in ioBroker/ioBroker.admin

closed Adapter installation from git starts first after manually kill of "git ls-remote -h -t git://github.com/iobroker-community-adapters/..." process #1471

[Glasfaser]

@smart81 sagte in Test Adapter enigma2 v1.2.x:

bleibt hier hängen:

wie lange hast du gewartet !?

[Smart81]

@glasfaser

Ich habe jetzt ca. 20min gewartet , tatsächlich hat er dann installiert

Der Adapter tauch aber nicht auf , er sagt er wäre installiert aber ich sehe Ihn leider nicht.

[Thomas Braun]

@smart81 sagte in Test Adapter enigma2 v1.2.x:

Der Adapter tauch aber nicht auf , er sagt er wäre installiert aber ich sehe Ihn leider nicht.

Bei Installationen über github müssen Instanzen manuell angelegt werden.

[Smart81]

@thomas-braun oh ! Das wusste ich nicht

Edit: hat geklappt

[oberfragger]

@smart81 Ich hab da mit den 4er JS-Controller ständig solche Fehlermeldungen im Log.

Read-only state "enigma2.0.enigma2.XXX" has been written without ack-flag with value ""

Bei dir auch?

[Glasfaser]

@oberfragger

4er JS-Controller

das liegt aber nicht am Controller 4

Welcher Datenpunkt ist das genau !?

Denn

Read-only state

Hast du ein Script was den Datenpunkt beschreiben will !?

[oberfragger]

@glasfaser Nein. Kein script. Diverse Datenpunkte!

[Glasfaser]

@oberfragger sagte in Test Adapter enigma2 v1.2.x:

Diverse Datenpunkte!

...... warum immer Screenshots davon !??

Welche Adapter Version ... !?
Wenn alte Version , Adapter anhalten , alle Datenpunkte löschen , neue Version installieren , , Adapter einschalten

[1Topf]

@oberfragger Wenn ich solche Meldungen habe, ist der Receiver einfach nur ausgeschalten. Also richtig AUS, kein Standby.

2022-05-30 22:18:48.813 - info: enigma2.1 (2786405) enigma2: 192.168.178.59:80 ist nicht erreichbar!
2022-05-30 22:18:48.989 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.BOX_IP" has been written without ack-flag with value ""
2022-05-30 22:18:49.010 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.CHANNEL" has been written without ack-flag with value ""
2022-05-30 22:18:49.017 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.CHANNEL_PICON" has been written without ack-flag with value ""
2022-05-30 22:18:49.038 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.CHANNEL_SERVICEREFERENCE" has been written without ack-flag with value ""
2022-05-30 22:18:49.040 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.EVENTDESCRIPTION" has been written without ack-flag with value ""
2022-05-30 22:18:49.066 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.EVENTDURATION" has been written without ack-flag with value ""
2022-05-30 22:18:49.068 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.EVENTREMAINING" has been written without ack-flag with value ""
2022-05-30 22:18:49.070 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.MESSAGE_ANSWER" has been written without ack-flag with value ""
2022-05-30 22:18:49.072 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.MODEL" has been written without ack-flag with value ""
2022-05-30 22:18:49.074 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.MUTED" has been written without ack-flag with value ""
2022-05-30 22:18:49.104 - info: enigma2.1 (2786405) State value to set for "enigma2.1.enigma2.MUTED" has to be type "boolean" but received type "string"
2022-05-30 22:18:49.105 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.NETWORK" has been written without ack-flag with value ""
2022-05-30 22:18:49.115 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.PROGRAMM" has been written without ack-flag with value ""
2022-05-30 22:18:49.117 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.PROGRAMM_AFTER" has been written without ack-flag with value ""
2022-05-30 22:18:49.134 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.PROGRAMM_AFTER_INFO" has been written without ack-flag with value ""
2022-05-30 22:18:49.136 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.PROGRAMM_INFO" has been written without ack-flag with value ""
2022-05-30 22:18:49.138 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.VOLUME" has been written without ack-flag with value ""
2022-05-30 22:18:49.139 - info: enigma2.1 (2786405) State value to set for "enigma2.1.enigma2.VOLUME" has to be type "number" but received type "string"
2022-05-30 22:18:49.141 - warn: enigma2.1 (2786405) Read-only state "enigma2.1.enigma2.WEB_IF_VERSION" has been written without ack-flag with value ""
2022-05-30 22:18:49.151 - warn: enigma2.1 (2786405) State "enigma2.1.Message.MESSAGE_ANSWER" has no existing object, this might lead to an error in future versions

[Negalein]

Servus

Ich habe meine Box auf einen Gigablue gewechselt.
Man kommt bei dem mit History zu den aufgenommenen Filmen.

Im Adapter unter enigma2.0.command gibt es keinen Button dafür.
Gibts eine andere Lösung, da ich die Fernbedienung in VIS bauen möchte?

[IOMax]

Hallo,
hat sich eigentlich jemand für die Weiterentwicklung gefunden ? Wäre toll, wenn dieser weiter gepflegt werden würde.
Gruß
Max

[el_malto]

@negalein auch wenn es schon länger her ist. Du kannst dir vom OpenWebIF GitHub die richtigen commands für die remotes raus suchen.
https://github.com/E2OpenPlugins/e2openplugin-OpenWebif/tree/master/plugin/public/static/remotes
Hier mal für die Quad Plus:
https://github.com/E2OpenPlugins/e2openplugin-OpenWebif/blob/master/plugin/public/static/remotes/gbquadplus.html
Wenn du da History suchst, siehst du das "361" der Key History ist. Somit müsste, wenn du im Datenpunkt enigma2.0.command.REMOTE-CONTROL "361" schreibst, die History Taste betätigt werden.
Ansonsten könntest du http://<IPvonReceiver>/web/remotecontrol?command=361 benutzen, dass müsste auch gehen.

@IOMax ich glaube nicht. Aber was funktioniert denn z.B. nicht?
Ansonsten bei Interesse hier melden:
https://github.com/Matten-Matten/ioBroker.enigma2/issues/44

Matten-Matten created this issue in Matten-Matten/ioBroker.enigma2

closed Work on adapter enigma2 canceled. Project taker wanted #44

[Negalein]

@el_malto sagte in Test Adapter enigma2 v1.2.x:

Wenn du da History suchst, siehst du das "361" der Key History ist. Somit müsste, wenn du im Datenpunkt enigma2.0.command.REMOTE-CONTROL "361" schreibst, die History Taste betätigt werden.

Danke, das funktioniert super!

[biker1602]

@negalein

Ich habe mal eine Frage. Ich habe gestern ein Update auf meiner Ultimo 4k mit Openatv 6.4 gemacht und seitdem spinnt der Adapter komplett.

Bei meinen anderen Boxen wo ich kein Update gemacht habe, ist alle OK

Hat das Phänomen noch jemand?
Ich hatte dann ein Backup zurück auf die Box gespielt, da geht dann alles wieder.
Hat jemand eine Idee?

[Negalein]

@biker1602 sagte in Test Adapter enigma2 v1.2.x:

Hat jemand eine Idee?

stell den Log nicht als Screenshot rein.

Kopier den Text und füge ihn bitte als Code rein.

[biker1602]

@negalein

	2022-08-24 08:56:58.025	error	instance system.adapter.enigma2.3 terminated with code 6 (UNCAUGHT_EXCEPTION)
enigma2.3
	2022-08-24 08:56:57.220	error	Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:57.220	error	TypeError: Cannot read property 'e2eventlist' of undefined at evaluateCommandResponse (/opt/iobroker/node_modules/iobroker.enigma2/main.js:521:40) at /opt/iobroker/node_modules/iobroker.enigma2/main.js:407:8 at Parser.<anonymous> (/opt/iobroker/node_modules/xml2js/lib/parser.js:304:18) at Parser.emit (events.js:376:20) at SAXParser.onclosetag (/opt/iobroker/node_modules/xml2js/lib/parser.js:262:26) at emit (/opt/iobroker/node_modules/sax/lib/sax.js:624:35) at emitNode (/opt/iobroker/node_modules/sax/lib/sax.js:629:5) at closeTag (/opt/iobroker/node_modules/sax/lib/sax.js:889:7) at SAXParser.write (/opt/iobroker/node_modules/sax/lib/sax.js:1436:13) at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/xml2js/lib/parser.js:323:31)
enigma2.3
	2022-08-24 08:56:57.219	error	unhandled promise rejection: Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:57.219	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
enigma2.3
	2022-08-24 08:56:57.179	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
enigma2.3
	2022-08-24 08:56:56.594	error	Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:56.594	error	TypeError: Cannot read property 'e2eventlist' of undefined at evaluateCommandResponse (/opt/iobroker/node_modules/iobroker.enigma2/main.js:521:40) at /opt/iobroker/node_modules/iobroker.enigma2/main.js:407:8 at Parser.<anonymous> (/opt/iobroker/node_modules/xml2js/lib/parser.js:304:18) at Parser.emit (events.js:376:20) at SAXParser.onclosetag (/opt/iobroker/node_modules/xml2js/lib/parser.js:262:26) at emit (/opt/iobroker/node_modules/sax/lib/sax.js:624:35) at emitNode (/opt/iobroker/node_modules/sax/lib/sax.js:629:5) at closeTag (/opt/iobroker/node_modules/sax/lib/sax.js:889:7) at SAXParser.write (/opt/iobroker/node_modules/sax/lib/sax.js:1436:13) at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/xml2js/lib/parser.js:323:31)
enigma2.3
	2022-08-24 08:56:56.592	error	unhandled promise rejection: Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:56.590	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
host.raspberrypi
	2022-08-24 08:56:16.223	error	instance system.adapter.enigma2.3 terminated with code 6 (UNCAUGHT_EXCEPTION)
enigma2.3
	2022-08-24 08:56:15.037	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
enigma2.3
	2022-08-24 08:56:14.752	error	Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:14.752	error	TypeError: Cannot read property 'e2eventlist' of undefined at evaluateCommandResponse (/opt/iobroker/node_modules/iobroker.enigma2/main.js:521:40) at /opt/iobroker/node_modules/iobroker.enigma2/main.js:407:8 at Parser.<anonymous> (/opt/iobroker/node_modules/xml2js/lib/parser.js:304:18) at Parser.emit (events.js:376:20) at SAXParser.onclosetag (/opt/iobroker/node_modules/xml2js/lib/parser.js:262:26) at emit (/opt/iobroker/node_modules/sax/lib/sax.js:624:35) at emitNode (/opt/iobroker/node_modules/sax/lib/sax.js:629:5) at closeTag (/opt/iobroker/node_modules/sax/lib/sax.js:889:7) at SAXParser.write (/opt/iobroker/node_modules/sax/lib/sax.js:1436:13) at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/xml2js/lib/parser.js:323:31)
enigma2.3
	2022-08-24 08:56:14.751	error	unhandled promise rejection: Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:14.750	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
enigma2.3
	2022-08-24 08:56:14.452	error	Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:14.452	error	TypeError: Cannot read property 'e2eventlist' of undefined at evaluateCommandResponse (/opt/iobroker/node_modules/iobroker.enigma2/main.js:521:40) at /opt/iobroker/node_modules/iobroker.enigma2/main.js:407:8 at Parser.<anonymous> (/opt/iobroker/node_modules/xml2js/lib/parser.js:304:18) at Parser.emit (events.js:376:20) at SAXParser.onclosetag (/opt/iobroker/node_modules/xml2js/lib/parser.js:262:26) at emit (/opt/iobroker/node_modules/sax/lib/sax.js:624:35) at emitNode (/opt/iobroker/node_modules/sax/lib/sax.js:629:5) at closeTag (/opt/iobroker/node_modules/sax/lib/sax.js:889:7) at SAXParser.write (/opt/iobroker/node_modules/sax/lib/sax.js:1436:13) at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/xml2js/lib/parser.js:323:31)
enigma2.3
	2022-08-24 08:56:14.450	error	unhandled promise rejection: Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:56:14.447	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
host.raspberrypi
	2022-08-24 08:55:34.969	error	instance system.adapter.enigma2.3 terminated with code 6 (UNCAUGHT_EXCEPTION)
enigma2.3
	2022-08-24 08:55:34.176	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
enigma2.3
	2022-08-24 08:55:33.642	error	Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:55:33.641	error	TypeError: Cannot read property 'e2eventlist' of undefined at evaluateCommandResponse (/opt/iobroker/node_modules/iobroker.enigma2/main.js:521:40) at /opt/iobroker/node_modules/iobroker.enigma2/main.js:407:8 at Parser.<anonymous> (/opt/iobroker/node_modules/xml2js/lib/parser.js:304:18) at Parser.emit (events.js:376:20) at SAXParser.onclosetag (/opt/iobroker/node_modules/xml2js/lib/parser.js:262:26) at emit (/opt/iobroker/node_modules/sax/lib/sax.js:624:35) at emitNode (/opt/iobroker/node_modules/sax/lib/sax.js:629:5) at closeTag (/opt/iobroker/node_modules/sax/lib/sax.js:889:7) at SAXParser.write (/opt/iobroker/node_modules/sax/lib/sax.js:1436:13) at Parser.exports.Parser.Parser.parseString (/opt/iobroker/node_modules/xml2js/lib/parser.js:323:31)
enigma2.3
	2022-08-24 08:55:33.639	error	unhandled promise rejection: Cannot read property 'e2eventlist' of undefined
enigma2.3
	2022-08-24 08:55:33.637	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, o