NEWS

@Piatt74568 https://forum.iobroker.net/topic/40706/alexa-iobroker-iot-skill-in-your-country

@alex84
Wenn es nach Video gemacht ist muss es ja gehen.

@Asgothian
Thanks that worked! I was told that the stick was flashed and tested correctly, so after a reflash all now works brilliantly.

@Tomasz-Nowak
No I send IR commands with it to the TV, HIFI, A/C, 433 MHz Signals to the plugs.....

@allacady

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 ?

A.

Wurde gelöst, sollte mal jemand das selbe Problem haben:
Für Infos:
https://www.loxone.com/dede/kb/webservices/

Account hier anlegen und das Loxonedevice anlegen.
https://alexa-node-red.bm.hardill.me.uk/
rednodedevice.JPG

Anschließend
https://alexa.amazon.de
Anmelden und Gerätesuche starten.

Folgende Paletten gehören installiert:
node-red-contrib-alexa-home-skill
node-red-contrib-loxone
installierte nodes.JPG installierte nodes2.JPG

Aufbau im Node Red:
nrlox1.JPG
Account der vorhin angelegt wurde hier eingeben. Wenn das Gerät in bei der Alexa suche gefunden wurde kann man es hier auswählen.

nrlox2.JPG
nrlox3.JPG
nrlox4.JPG
nrlox5.JPG
nrlox6.JPG
Verbindung zu Loxone Miniserver herstellen, dann findet man sämtliche Geräte.

Viel Erfolg!

@jrjong11
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.

A.

@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?

@Sher02 said in JS-Controller Update SOLVED:

@Stabilostick Yes it does change very often. I often feel irritated. https://www.tellthebell.one/

The old server shows controller 2.0.38 available, while the new one is 2.0.34.

@apollon77 Aussitzen hilft anscheinend doch. Datenleiche ist weg. Perfekt! Und der Adapter ist auch in der Cloud auf dem neuen Stand!

@DanielIO I solved this by using ConBee2 and created my own Hub

@Anthon1y sagte in Z-Wave does not work after reboot:

I'm also having the same problem as the others!

please specify!

@Surfer2010 said in Problem iobroker as docker-installation (solved):

wasn't really the permission on the folder but the drive this folder was on has been mounted as "noexec" (fstab).

Can you please elaborate on the change aol mail password solution, please. It would be great for us beginners.

@ap2017 said in Adding node to mySENSORS. SOLVED!:

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
e2441d69-346b-4348-82e0-32bc73e35a1f-image.png

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.

@dragonpas Can you try to find the skill on amazon.com? Today I added 6 other languages, including US, BR, FR, IT and ES.

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.

Thank you. Since mySENSORS adapter is about to be fixed to allow nodes with number >10, see latest GitHub, I will stick with adapter.