I have to say that i am no expert in vis or grafana, but the main issue seems to be that the phone cannot seem to reach the grafana server when it is trying to display the visualisation. Can you check the link to the Grafana view in the vis ? and see if it will open on its own when used in the iPad browser ?
If I look at the generated errors (and assuming I translate them correctly) the Skript fails at 3 points:
setcap: either the command does not exist or it cannot be used with sudo
Sudo: setcap: comando non trovato
creating the user iobroker and group iobroker seems to fail
creating the folder /opt/iobroker seems to fail due to lack of permissions.
@Thomas-Braun mentioned the easy way out - use a Debian based Linux as basis.
If you want to keep opensuse, you can try the following steps:
create a user and group iobroker (without password, the user does not need to log on
create a folder /opt/iobroker and „chown“ it to iobroker
ensure that the user iobroker is allowed to use sudo
Run the script again.
@Asgothian Thank you for your help, re-flashing zigbee adapter helped, I no longer have error messages and my zigbee devices are operational. I am wondering what went wrong, adapter flash memory got corrupted?
@Asgothian cc2531 work for me without any issue since January.
I do not doubt that. I had my network running with one for over a year myself before i shifted to a different adapter.
Overall, the CC2531 has the weakest hardware of the compatible adapters and may cause problems when trying to handle large networks, both for covered area as well as number of devices in the network. I am not saying that the CC2531 will not work. But i do advise to read through the descriptions and check the alternatives.
I am trying to add a new node to an existing mySensors configuration, but instead of adding dedicated node (Light Lux Sensor), it renames existing node 10 and adds line 10.1_Light_Level to it. Tried multiple times, same result. All my nodes are based on latest version 2.3.2 mySENSORS software. IoBroker uses latest mySENSORS adapter 2.0.0, controller 3.0.17, node.js 10.20.1
5/30/20. User jangatzke solved this issue and set pull request to fix it in Github, see issue#22
Canyou please set the answers as I'm having the same scenario.
The adapter sees this device (type 0x4e2a) but does not know how to handle it.
I do not know Vortex wifi control AC and this broadlink type number, and therefore broadlink2 lists it as unknown device.
The problem is that nobody know which parameters need to be read or sent to the device to make it working.
This could be found only if you have a network sniffer and record all packages sent/received by the device. and reverse-engeneer the commands.