Nodes get disconnected and others are still connected about node-red-contrib-loxone HOT 5 CLOSED

I don't have any problems controlling blinds with Node-RED and Alexa via Loxone.
Please try to create a little Dashboard-button or use a normal inject node to start the specific nodes in that flow and see whether that works in lieu of using Alexa node.

from node-red-contrib-loxone.

It is a Loxone problem - the central blinds elements ( "type":"CentralJalousie" ) cannot be controlled via the api. When i change the webservice node to the dedicated blinds then it works as expected.

I do not understand those design principles of loxone software ...
I gonna update to the latest beta right now and test if there is work still the same. If yes, i gonna open a bug.

from node-red-contrib-loxone.

Hey @mabunixda,

as I have no Alexa I can not test this. Maybe @thmeger can double check if this behavior lies in Alexa or in node-red-contrib-loxone.

The connected/disconnected info is only updated on a full-deploy. That's where #12 ist related as this bit of information in the editor needs to be better.
Nevertheless all nodes are "connected" as long as the single connection to the miniserver is online.

Cheers,
Patrik

from node-red-contrib-loxone.

I'm with you.
I have not tested node-red-contrib-loxone to the latest beta, yet.

Just for my head: Can you control CentralJalousie from the smartphone-app?

from node-red-contrib-loxone.

Yeah you are right ... got it: /FullDown and /FullUp are the correct commands

from node-red-contrib-loxone.