SmartHome Community

ronluna

Sharing what I believe is a great way to add support to devices that used to work but since existing plugin haven't been maintain by the original authors (or any other developer in the community) have stopped working as they've abandon or moved to other platform...

Homebridge has a large and very active community and I think this type of plugin will a good way to benefit from it.

It will bring any device that have been configured in homebridge into openluup.

Currently it support, thermostat (Nest and others), Switches (Specially MyQ), Dimmers, Switches, Motion Sensors, Door Lock (Open/close) Support to other type of device can easily be added.

Homebridge2Openluup
Installation:

upload the files to /you_openluup_directory/files/
create a new device with D_Homebridge2openluup1.xml

Set your hombredige IP, username, password to the deivce's attributes

Capture the uuid of the device you would like to bring from Homebridge into openluup by looking at your openluup logs when starting

based on the device type, set DeviceList Variable

T for thermostat
D for dimmers
S for switches
G for garage doors
L for Locks
A for motion sensors

and build a string device type are delimited by a ; (semicolong) and device's uui by a , (comma) like this:
T:homebridge_thermostat1_uuid,homebridge_thermostat2_uuid;D:homebridge_dimmer1_uuid,homebridge_dimmer2_uuid etc

This still in beta, would love to add async next and support to shades and other sensors.

ronluna

@therealdb could use homebridge 2 openluup also...

ronluna

I'm trying to monitor the indicator command class of a 5 button scene controller in Z-Way so openluup can properly create and track it.

seems like Z-Way COMMAND_CLASS_INDICATOR (0x87 or 135) are not being monitored by the ZWave module as I couldn't find anything for this command class in (/z-way-server-path/automation/modules/ZWave/index.js)

When a Get or Set Indicator command class request is sent to the controller. ZSniffer picks up the request and response just fine although this packets are not being monitored by the zwave module
Example:

ZWayIP:8083/ZWaveAPI/Run/SendData(NodeID,[ Command_Class, Instance, Value ])
ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 0x87, 0x01, 0x01 ]) (Hexa)
ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 135, 1, 1 ]) (Decimal)

the answer looks like:

[2020-04-24 19:59:36.261] [I] [zway] Waiting for job reply: Indicator Get
[2020-04-24 19:59:36.281] [D] [zway] RECEIVED: ( 01 0B 00 04 00 02 03 87 03 01 B6 00 C2 )
[2020-04-24 19:59:36.281] [D] [zway] SENT ACK

I’d like to store the Indicator response “RECEIVED” correctly. I believe by modifying the index.js of the zwave module could do the trick and once the module start tracking the indicator command class values as a metric then openluup's z-way plugin would properly track any changes as well.

I'm wondering if anyone around here could share any thoughts or comments that could make it easier...

ronluna

@akbooer That's right... and just like that... apple is taking over then entire home automation industry.... too bad there is no Home app for Android. Well Front end and first layer voice control related...

ronluna

thanks @akbooer . I'll be adding the installation instructions to the readme file... By the way, this plugin also works for ecobee thermostat, the native ecobee lua plugin by @rafale77 works ok when there is only one thermostat in the ecobee account but when more than one, ecobee server keeps deauthorizing the plugin...

@rafale77 I also use homebridge the other way (openluup to homebridge) and is great.

I'm currently using it for:

Nest thermostats with google accounts.
Ecobee accounts with multiple thermostats
AUX Mini split with built-in wifi modules

Planning on adding control for AppleTV , Ring devices, Doorbird motion detection and many more...

It will allow us to finally include many of the popular cloud based devices that own into the openluup environment...

Something really cool about homebridge is that the manual and basic automation can be done from within homekit by the end-user, but deeper logic can be done from within openluup. Thinking about bringing node-red into the mix also... anyhow... I hope it can be useful for everyone here...

ronluna

@crille pushed new fix for celsius. the plugin is now available on the altappstore.

ronluna

@Crille I was using an older version. I have pushed a fixed to make device's name persistent after engine reload. please update the plugin and share the results when you get a chance.

Thanks @akbooer for the pointing this out.

ronluna

I was unable to get MQTT to work correctly in openluup... I had to give up... It's a real shame ... as ZwaveJS is by far the best thing I've seen to manage zwave networks.

ronluna

If there is something I can do to help, please let me know.

ronluna

I had to disable the MQTT Handler from the startup as it was crashing the entire engine.

ronluna

@akbooer with DEBUG enabled the logs show:

2022-03-20 15:54:54.501   openLuup.mqtt:: CONNECT tcp{client}: 0x55ae0e8b8318
2022-03-20 15:54:54.501   openLuup.mqtt:: ClientId: ZWAVE_GATEWAY-Zwavejs2Mqtt
2022-03-20 15:54:54.501   openLuup.mqtt:: WillTopic: zwave/_CLIENTS/ZWAVE_GATEWAY-Zwavejs2Mqtt/status
2022-03-20 15:54:54.501   openLuup.mqtt:: WillMessage: {"value":false}
2022-03-20 15:54:54.502   openLuup.mqtt:: UserName: ********
2022-03-20 15:54:54.502   openLuup.mqtt:: Password: ********
2022-03-20 15:54:54.502   openLuup.io.server:: MQTT:1829 connection closed  tcp{client}: 0x55ae0a5f7e78
2022-03-20 15:54:54.502   openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55ae0a5f7e78
2022-03-20 15:54:54.519   openLuup.server:: request completed (16415 bytes, 2 chunks, 1068 ms) tcp{client}: 0x55ae0c39f788
2022-03-20 15:54:54.587   openLuup.server:: error 'closed' sending 6 bytes to tcp{client}: 0x55ae0dfce198
2022-03-20 15:54:54.587   openLuup.server:: ...only 0 bytes sent
2022-03-20 15:54:54.587   openLuup.server:: error 'closed' sending 94946 bytes to tcp{client}: 0x55ae0dfce198
2022-03-20 15:54:54.587   openLuup.server:: ...only 0 bytes sent
2022-03-20 15:54:54.587   openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55ae0dfce198

Seems like is related to what @toggledbits has shared a couple weeks ago. clues?

ronluna

I'm currently having a problem where the only way to get openluup to start processing messages from subscribed topics is by restarting the ZWaveJS service. When the ZWaveJS MQTT service is restarted the ZWaveJS Clients send the subscribe messages to openluup and only then is when messages start to get processed.

Testing with the following inserted in the startup:

local json = require "openLuup.json"

function MyMQTThandler (topic, message)
  local info = json.decode (message)
  local currentLevel = info.value
  luup.variable_set ("urn:upnp-org:serviceId:Dimming1", "LoadLevelStatus",  currentLevel, 68)
  luup.log("Processed")
end
 
luup.register_handler ("MyMQTThandler", "mqtt:zwave/Hallway_2/DImmer_1/38/0/currentValue")

I Couldn't find anything on ZWaveJS nor in openluup that might explain this behavior and my short mqtt knowledge is not helpful either.

Any ideas?

ronluna

Based out L_ShellyBridge.lua I've created initial L_ZWaveBridge.lua made changes in virtualfilesystem.lua to create D_ZWaveBridge.xml, D_ZWaveBridge.json and subcribed to zwave topic. which is how the MQTT messages are sent from ZWaveJS2MQTT by default.

my startup lua looks like:

luup.attr_set ("openLuup.MQTT.Username", "*********")
luup.attr_set ("openLuup.MQTT.Password", "*********")
luup.attr_set ("openLuup.MQTT.Port", 1811)
luup.attr_set ("openLuup.MQTT.PublishVariableUpdates", true)
luup.attr_set ("openLuup.MQTT.DEBUG", true)

With my short mqtt understanding ZWaveJS is connecting and authenticating just fine to openluup although I've been unable to properly modify L_ZWaveBridge.lua to capture and parse the messages that ZWaveJS is sending.

ronluna

Would be awesome to get ZWaveJS2Mqtt added to openluup. As much as ZWay has proven to be faster and much more reliable than Vera... ZWaveJS has a bright future...

ronluna

Maybe adding sockproxyd natively into openluup and modifying io.lua to optionally use sockproxyd could be a real winner to finally solve the limitations/problems in the I/O module.

ronluna

There is a little issue I'm currently facing with openluup and plugins that relies on io module.

If openluup is watching a variable that belongs to a devices that relies on io module and there is an action attached that also relies on io module, when that watcher gets triggered, the action in question will get processed in openluup (it will show in the logs) but the parent device won't process it.

I have a feeling that this could be due to io packets crossing between each others somehow modifying the final message received by the parent device. it's feels like the io communication is happening in the same room for all plugins and sometimes they get crossed. Wondering if anyone has experienced something of that sort and if there is a way to prevent it?

ronluna

@akbooer That's right... and just like that... apple is taking over then entire home automation industry.... too bad there is no Home app for Android. Well Front end and first layer voice control related...

[Solved] Expressions - predefining a variable type

Trying to add second Hubitat controller

Reactor (Multi-System/Multi-Hub) Announcements

Home assistant addon: Import Vera/Openluup backup

Logic Programming

MQTT Controller and extended capabilities

localization settings

Separate switching bulb in one ceiling light

Installing MQTTController on Home Assistant Core when Reactor is installed as an Add-In (VirtualBox)

Home Assistant add-on

When turning off the dimmer, set the LoadLevelLast to 100%

Console view: - No Live refreshes via :3480/console?page=devices

Does order matter in Reactions Set/Reset

Reactor: How to call Hass service for noob

Razberry firmware upgrade from 5.04 to 5.27

Netatmo – Oath2 login

Reactor Ex Machina

No drop-down list on Entity Attribute in "Creation Rule Sets" interface

chine version of homeypro to convert 433 to IR,wifi,Bluetooth,866,..?/

ronluna

@ronluna

Best posts made by ronluna

Latest posts made by ronluna