NEWS

So I ended up doing a full clean install RPI4 3Gb with Bullseye 64 bit. Restoring worked for adapters and javascript; zigbee and history both came with errors:
{"errno":-1,"code":"EPERM","syscall":"utime","path":"/opt/iobroker/backups/tmpScripts/"}
Still it all worked, so it is just a finding.

@jonnyhk

Please post terminal output in CodeTags.
Thx.

Does it run now?
If not, I can't help, Windows is unknown to me.

Zeig doch bitte mal dwie das Alias objekt aussieht was da rausfällt.. .

@crunchip
🤦‍♂️
Danke

@simplyclever

cd /opt/iobroker sudo -u iobroker npm cache clear --force

@homoran
Habe gefunden wie man den ersten post editiert.
danke nochmal 👏 👏

@thomas-kramer Hello, is there and solution for this ?

@alcalzone said in Adapter Alias - download Inputs:

@homecineplexx sagte in Adapter Alias - download Inputs:

naja wozu sind diese Pfeile, wenn ich da nicht die Info von meinen Alias raus bekomme ??

Etwas technischer Hintergrund:

Adapter-Konfiguration ist im Objekt system.adapter.<adaptername>.<instanz> gespeichert, unter native. Das bekommst du bei diesem Download, der generisch vom Admin für jeden Adapter gleich gehandhabt wird. Die Aliasse selbst existieren als andere, spezielle Objekte, die der Adapter für dich managed. Das ist zwar aus User-Sicht Konfiguration, technisch aber halt nicht. Eine adapterspezifische Erweiterung der obigen Funktion ist so nicht vorgesehen, wäre aber ggf. ein Issue wert.

Deine Aliasse kannst du wie von arteck geschrieben mit einem "normalen" ioBroker-Backup sichern. Das enthält alle Datenpunkte und Objekte, inklusive den Aliassen.

Danke für diese Erklärung!!

@ssond0815 Wordle said in Zigbee Signal Level:

@ap2017 yes, the zigbee connection strenght fluctuates also in my case. Since I have only two devices yet, I suppose this becomes more smooth if I have more devices running that create a tighter mesh network. In some weeks I will have some more devices running, let's see.

Thanks for your answer. It helped me a lot.

@shaarkys

if you have any questions - don't hesitate to ask

@robocop [gelöst] hoffe ich:!
in der Config auf D3 einen Switch_n "1" und unter D7 einen Switch "2" eingerichtet.
SwitchMode3 1
sollte so funktionieren... mal sehen wie lange die Batterien(Akkus) halten bei einem DeepSleepTime 1200 und einer TelePeriod von 20

@mickym Thanks! Update to 0.0.56 worked out with the direct Github install.

@rob-1 sagte in Open Gate:

@homoran sorry i got nothing installed like this atm. I just wonder if i can do it somehow
atm iam using siri and tell her to open or close gate but i would like it fully automated

I do not know what for Apps are available in your area.
Here some user are working with a geofencing app, connected to ioBroker.

With this you can automate it. But be aware what will happen if you`re coming home from pub not really looking clearly 😉 with the phone in your pocket

@ap2017 sagte in Zigbee device availability detection:

@thomas-braun I thought about it first, but switch does not show power when in ON state with no load connected, don't think load needs to be connected for voltage reading. Tried it with load connected, still does not read voltage. Just in case, I filed an issue at Zigbee github regarding not able to read voltage.

272591ea-596d-4e45-84ac-2e7081cfdada-image.png

The load voltage state will also not be usable for connection detection. The reason is simple:

A plug which is connected may update this state once every x minutes, with x usually being within the range of 5 to 300. If you power of the plug, it lacks the power to update the value, hence the state will remain at the last state sent by the plug. This is true for any state published by the plug.

There are very few devices which publish their states in a short interval. Most only post changes to their values, and even then have a minimum time difference between posting different values.

The available state has the same issue. It is generated by the adapter attempting to obtain a response from the device using a "ping request". In theory, all line powered devices should respond to ping requests. Unfortunately, there are line powered devices which report as "end devices" and as such will not report to ping requests, i.e. their status cannot easily be verified.

A.