NEWS

@jey-cee Sorry Du hast Recht, ich drücke mich unklar aus. Ich nutze den Adapter bis jetzt noch gar nicht und wollte wissen, ob ich den guten Gewissens einsetzen kann oder ob der schon jetzt bzw. nach dem nächsten Update auf Fitbit-Seite nicht mehr (oder nicht mehr richtig) funktioniert, weil er nicht mehr aktiv gepflegt wird. Euren Reaktionen entnehme ich jetzt aber mal, das der Adapter zumindest noch genutzt wird...

@iiibroker we have problems with groups at the moment... i know

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

@UncleSam Everything works now. I did not realized that I have to reset the web hook variable after motion is detected.

@Alex-Sunny said in SIMPLE-API no object folder for data points ?..:

Hello,

i created a instance of simple-api and it is running. In instance view, no new "folder" is shown to create new datapoints. Has anybody an idea?
Where can i store my datapoint alternativly?
https://topdatingwebsitesx.com/chatiw
https://topdatingwebsitesx.com/chatki
https://chatrandom.livethanks
alexsunny

thanks my issue has been fixed.

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

@Alex-Sunny said in Z-Wave Installation for Windows ?..:

Hello,

Have brand new ioBroker installation on Windows 7 PC. Windows updated to the latest. All required adapters are https://chatrandom.live https://topdatingwebsitesx.com/chatrandom https://topdatingwebsitesx.com/camsurf installed except Z-Wave, see installation log attached.

thanks
alexsunny

thanks my issue has been fixed.

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

@Alex-Sunny sagte in Questions about the ioBroker installation under Windows?..:

Then you could still use the complete Create ioBroker folder as a backup at file level as a backup and if necessary. restore by simply replacing the current folder?

Well, the installer of course installs the service which is linked to the given folder, so the folder is not completely independent.

But honestly, I don't see any reason for creating a folder level backup. It is much better to simply use the BackItUp Adapter and put backups for example in the cloud (or your NAS). Like this you can not only restore the system on Windows but also other platforms (like Docker on Windows / WSL).

I noticed that a network drive that was connected to a drive letter via the normal system environment of Windows 10 cannot be reached in the ioBroker command console. Eg "z:" + Enter already leads to an error message.
Why is that? And how else can you access it?

I can confirm that this is the case. I can't access my network drives from my NAS neither. Most probably it is because the command line is running as a local administrator and thus doesn't have access to network drives. Nonetheless ioBroker of course has access to those paths (AFAIK).
Question: why do you need access to network drives from the ioBroker command line? This command prompt is only supposed to be used for administering ioBroker (e.g. add/remove adapters, configure core settings like multihost, ...).

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