Javi

Great, for reference the numbers 1:1,1 correspond to the module and port (blaster). Depending on your iTach version and number of ports and modules.

"completeir,1:1,1" is a response from the iTach, where "1:1,1" corresponds to the command "sendir,1:1,1....". So the command is reaching the iTach.

Thanks, Fixed open device dashboard for folders in both Android and iOS in next app version.

Have you tried the iTach Node Server? See pinned topin in subforum below. https://forum.universal-devices.com/forum/324-itach-ir/ For Network Resource check port and termination "\r\n" at the end of the command

The Z-Wave device may need to be factory reset. Then add using the QR Code which will automatically configure with security. The device may need to be close to the Z-Wave dongle during commissioning. Also some devices need the longer timeouts, see

Glad you like the charts! Incorrect time is due to a bug in firmware, I think it is now fixed on our side for the next firmware release. So feature is still beta until firmware release.

Node Def: <nodeDef id="MQSW" nls="SWITCH"> <editors/> <sts> <st editor="ONOFF" id="ST"/> </sts> <cmds> <sends> <cmd id="DON"/> <cmd id="DOF"/> </sends> <accepts> <cmd id="QUERY"/> <cmd id="DON"/> <cmd id="DOF"/> </accepts> </cmds> </nodeDef> Editor: <editors> <editor id="BOOL"> <range subset="0,1" uom="2"/> </editor> <editor id="ONOFF"> <range uom="78"/> </editor> <editor id="TEMPF"> <range max="176" min="-40" prec="2" uom="17"/> </editor> <editor id="HUM"> <range max="100" min="0" prec="2" uom="22"/> </editor> ........ </editors> Summary: Editor ID "ONOFF" is missing min/max or subset Added pull request for developer https://github.com/Trilife/udi-mqtt-pg3x/pull/16

Local access should work, however it is highly dependent on the device. Many devices, especially Apple devices, will not route traffic to a WiFi Connection without internet. So even if you force it to connect to WiFi it will not send requests. https://wiki.universal-devices.com/UD_Mobile#WiFi_Connections_without_internet

Perfect, Please post output of these 3 files: NodeDef, needed to get the editor ID from node def ID: http://192.168.XX.XX:8080/rest/profiles/family/10/profile/12/download/nodedef/nodedefs.xml Editor, needed to verify missing min/max or subset values: http://192.168.XX.XX:8080/rest/profiles/family/10/profile/12/download/editor/editors.xml Node: http://192.168.XX.XX:8080/rest/nodes/nodeAddress. where nodeAddress is the node address of any one of the nodes with the issue. Needed to get the Node Def ID

Thanks what slots number is the mqtt plugin?

Looks like the Node Server is missing a value. Please post the output of http://192.168.XX.XX:8080/rest/profiles/family/10/files. where 192.168.XX.XX is the local ip address

I don't recommend this for 5.x. Using scenes, like the fan example, is the recommended way.

I was referring to eisy, sometimes the battery parameter is included in a separate node

Check out the 5.x Keypad and Fan scene example https://wiki.universal-devices.com/ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration#Firmware_5.x Scenes will work better than programs and KPL buttons can not be programmatically controlled, they require a scene (insteon limitation). A scene with the KPL button will need to be created to turn it on/off. Programs should only be used for corrections, like the "Note" section after the main scene in the example, as there are no "Wait" conditions. Sending many Insteon commands rapidly (i.e. from a program) may cause some commands to be dropped by the insteon network, so it may not work as expected without waits in between commands. Although this is even more tricky as "Wait" makes eisy programs act as a "While" instead of "IF" so the program may not finish executing if there is a wait without the main program triggering "Then" on another program.

Not sure, is there sibling node with the battery level? The time is one of the reasons it's still beta, we had a formatting issue in the database. I think it should be fixed in the next firmware release, but not my specialty so I could be wrong . We also still need to implement a database purging as the database could become very large very quickly for some users.