Recent Posts

Pages: 1 2 [3] 4 5 ... 10
@hugheaves - not sure if this changed in a firmware update I applied to ad2usb, but the regex match in processIncoming() needed to be updated. The first capture is hex, not decimal:

The message from ad2usb:
Code: [Select]
[10000001000000003A--],008,[f70000051008001c08020000000000],"****DISARMED****  Ready to Arm  "

Old regex in trunk rev 83:
Code: [Select]
local sections = {data:match('^%[([%d%-]+)%],(%x+),%[(%x+)%],"(.+)"$')}

Updated regex:
Code: [Select]
local sections = {data:match('^%[([%x%-]+)%],(%x+),%[(%x+)%],"(.+)"$')}

Without modifying the regex I was getting "ERROR: Invalid message.". The only thing it impacted was the system status. Sending commands was still working fine which made me look a little deeper.
Plugins & Plugin Development / Re: PLUGIN: Wifi/UDP Switch Controller
« Last post by cybrmage on November 24, 2017, 04:26:59 pm »
The above lup code actually does not work with yeelight

The ToggleState action definately DOES work with yeelight bulbs, as well as all other supported devices (Except the Broadlink temp sensor).

If you are going to claim that something in the plugin does not work, you had better be posting logs to prove it.
USB RFXtrx Transceiver Plugin / Re: A fix for device auto create an delete
« Last post by halo on November 24, 2017, 04:25:46 pm »
Already tested. Works as expected. We can again manuallly create new devices. Auto adding works are well. Great job.
General / Re: How To Setup Hardware Associations (a.k.a. Groups)
« Last post by kwieto on November 24, 2017, 04:19:07 pm »
You're welcome, and good luck with tracking the problem :)
Plugins & Plugin Development / Re: PLUGIN: Broadlink RM Interface
« Last post by Ben007 on November 24, 2017, 03:42:54 pm »
Broadlink RM2 Interface

Learn (IR only) and send (IR/RF codes) remote codes using your Vera.

No RM-Bridge required!!

Supported Devices

With the latest update  (v 1.13 ) my ancient RM PRO working perfectly. THANK YOU!!!!!!

All Broadlink RM/RM2/RM3 devices.

Automatic detection of Broadlink devices
Management of IR codes from the code management page.
Manual send of codes from the code management page.
Send code using UPNP action, lua call_action or from a scene

Version History:

v1.13   (Version ID: 35006) November 14, 2017
-- fixed - timestamp issue caused plugin crash on certain firmware versions
-- fixed - unsupported devices appear in discovered device list

v1.10   (Version ID: 34952) November 7, 2017
-- added - device discovery through device probing when discovery mechanism fails to discover devices
-- added - device discovery via import of e-Control configuration
-- changed - prevent re-import of IR/RF codes when processing additional e-Control imports
-- changed - plugin excessively chatty when debug mode is disabled

v1.8     (Version ID: 34906) November 3, 2017
-- fixed - json handling caused configuration page to fail to load under certain circumstances
-- added - better device determination - support for more device variants

v1.6     (Version ID: 34892) October 30, 2017
-- fixed - UPnP SendCode action causes plugin crash

v1.5     (Version ID: 34886) October 30, 2017
-- fixed - code corruption when importing Pronto/e-Control codes
-- fixed - code verification regected valid code under certain conditions
-- added - update code name from code management page

v1.4     (Version ID: 34871) October 29, 2017
-- added - Ability to manually import a code in the code management page
-- added - Ability to manually import a PRONTO format code in the code management page
-- added - Ability to import IR Code configuration from the Broadlink e-Controll mobile app (Android or IOS)
NOTE* - To import code from e-Control, you must
  1) know the IP Address of your device
  2) have the e-Control application running and select the "more functions" page (stacked bars icon in upper left corner of the "Control" page
  3) Select "share", then select "Share to other phones in WLAN"
  4) On the plugin code management page, in the "Add code from network connected device running e-Control." box, enter the IP address of the phone and click "Add"

v1.3     (Version ID: 34862) October 29, 2017
-- fixed - typo prevented sending non-RF codes to non-pro devices

v1.2     (Version ID: 34856) October 29, 2017
-- fixed - Broadlink device initial discovery did not occur
-- added - option on device page to rescan for devices

v1.1     (Version ID: 34846) October 28, 2017
-- Initial release.
-- NOTE: This version will display in the UI as "v1.0"

Automatic installation:
You can install the plugin via the App Store from you Vera under the Apps/Install Apps menu.

You can update to the latest approved version in the App Store by going to Apps/My Apps, selecting the plugin and enabling "Auto Update"

You can force your Vera to update to a specific release before it is approved in the App Store by entering the following URL into your browser:
Code: [Select]
http://<your ip>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8996&Version=<Version ID>
Make sure to replace <your ip> with the IP Address of your Vera, and <Version ID> with the Version ID provided in the release post/ revision history.


Once the plugin is installed, allow the LuaUPnP engine to finish loading and REFRESH YOUR BROWSER.

Open the device setup page, and click on the "Device" tab. The plugin will list all the Broadlink devices found on the network. Click on the "select" button next to the device you want to use for sending/learning IR codes.

You can then click on the "Codes" tab. The Codes page will show a summary of the existing learned codes (which will initially be empty). You can the click on the "Learn IR" button. The plugin will ask for the name you wish to give to the learned code. Once you enter the name and click on "ok", the plugin will place the selected Broadlink device into learn mode (an amber led will light on the Broadlink device). You then have 30 seconds to point the remote at the broadlink device and press the button you wish to learn. Once the code is learned, the broadlink device will return to normal mode, and the code page will be updated with the new code. Once a code is learned, you can then test the code by clicking the "Send" button next to the code. Unneeded or unwanted codes can be removed by clicking on the "Remove" button.

To have the Broadlink device send an IR code, you can:

1) Use a UPNP action to cause a stored code to be sent.

Code: [Select]
http://vera.ip.add.ress:3480/data_request?id=action&DeviceNum=<DeviceNumber>&serviceId=urn:micasaverde-com:serviceId:Broadlink1&action=SendCode&CodeData=<stored code identifier>

    vera.ip.add.ress = The IP Address of your Vera
    <DeviceNumber> = The Vera Device ID of the Broadlink RM device
    <stored code identifier> = the unique identifier of the stored code (see below for details)


Code: [Select]
luup.call_action("urn:micasaverde-com:serviceId:Broadlink1", "SendCode", {CodeData = "<stored code identifier>"}, <DeviceNumber>)

    <DeviceNumber> = The Vera Device ID of the Broadlink RM device
    <stored code identifier> = the unique identifier of the stored code (see below for details)

2) Use the Vera Scene Advanced editor, to send a code from a Vera Scene.

In the Vera Scene Editor, to to the advanced editor and select "Add Action", select the Broadlink RM Interface device, Select the "SendCode" action, and enter the stored code identifier into the CodeData text box, and click on "Add".

Stored Code Identifiers

Each learned code must be identified with a unique identifier. The unique identifier can be either the name of the stored code or the ID shown on the code management page.

Please note that, at this time, if you use more that a single word for the name of a code, you *MUST* use the ID to identify the code.

NOTE: Although the plugin identifies the IP address of the device that learned a code, the codes are *NOT* specific to individual Broadlink devices. You *CAN* learn code with one device and send them with another device.

Import IR/RF codes or Devices from e-Control

  1) Determine the IP Address of the IOS/Android device running e-Control.
  2) have the e-Control application running and select the "more functions" page (stacked bars icon in upper left corner of the "Control" page
  3) Select "share", then select "Share to other phones in WLAN"
  4) On the plugin code management page, in the "Add code from network connected device running e-Control." box, enter the IP address of the phone and click "Add"

Note: Devices included in the e-Control data are not directly imported into the plugin. The device identifier is used to locate the device, if the device is located, it is added to the discovered device list. The device(s) are NOT automatically selected.

**** PLEASE NOTE ****

If you have problems, and expect any support.... you MUST post LuaUPnP logs showing the operation of the plugin (with the plugin debug mode enabled).
Google Home/Google Assistant - Vera Concierge / Re: Still cannot talk to Concierge Server
« Last post by Inzax on November 24, 2017, 03:09:40 pm »
Same issue.

I have connectivity according to the web based interface https://localhoast:8989

I have a valid license purchased.

I can see my google devices via the web based interface.

I can send text to speech to all of the devices indicating they are connected.

When I "update vera concierge server cloud info" I am "signed in" with my account.  Associated vera controllers respond and indicate they are connected when selecting "connectivity".

I have tuned off firewall.  I have restarted everything.  Set up firewall rules. 

When talking to my google home, it tells me to use the the home app to link to vera concierge.  I try and stall out every single time.  Just don't know what else to do.
I spotted a new reply on Twitter by Vera and they said support is coming in beta soon. My installation is Stable at the moment, minus scenes that are not triggering in real time. Crossing fingers.
I am still having issues with this. Just to clarify, I created a trigger when the Simple Alarm Plugin is Armed (Away) called tSecuritySystemArmed. I also created another trigger when Simple Alarm Plugin is disarmed called tSecuritySysDisarmed.

When I type in this into my condition:

tSecuritySystemArmed; tSecuritySysDisarmed

this condition becomes true when the plugin goes from armed to issues

However, when I created a schedule from 9am to 9pm called s9amTo9pm (see attachment) and I type in this condition

s9amTo9pm and (tSecuritySystemArmed; tSecuritySysDisarmed)

this condition does not become true at any time between 9am and 9pm

I cant figure out what I am doing wrong here. Is my schedule programmed correctly? Am I programming the condition correctly? Can someone please help me. I've tried various things and I cannot get this to work properly. Any help would be greatly appreciated.
Lock, Motion & Security Control / Re: Garagedoor Sensor - How to create a sinful Scene
« Last post by Jamr on November 24, 2017, 01:44:56 pm »
I just wanted to bring up the dangers of automating your garage door closing.
Make sure you have all of the security measures on the door itself set up so if your car is parked under it it will not hit it.
Also make sure the sensor is not too low that the beam goes under the car when it is parked under the door.
I also recommend a garage door opener sub controller that abides by the UL325 standards.
I also recommend a camera in your garage make sure there is not obstruction under your garage door prior to closing it manually.

Just some thoughts.
Amazon Alexa / Re: Device is not responding
« Last post by myk on November 24, 2017, 01:27:13 pm »
I just upgraded to UI7 and enabled this skill today and no device has "responded" yet to me either

EDIT - I had to switch Alexa to my user - it was under my wife's user.  See,49122.0.html for more info on what my issue was
Pages: 1 2 [3] 4 5 ... 10