Author Topic: Assistance with setup...  (Read 1956 times)

Offline Maartenvt

  • Full Member
  • ***
  • Posts: 146
  • Karma: +0/-0
Assistance with setup...
« on: September 26, 2014, 05:10:46 pm »
Hi All,

I still didn't get it to work. I refreshed all the xml file with the new 0.32 version of xslt files.

See attached files. I hope somebody can help me to get it to work.

Vera firmare: 1.1.1245

Vera Edge (Firmware rev. 1.7.2406), 1x Düwi INTERACT³ light switch, 1x  ZIR010 Motion Sensor.

Offline guessed

  • Master Member
  • *******
  • Posts: 5294
  • Karma: +90/-22
  • Release compat is not a bolted-on afterthought
Re: Assistance with setup...
« Reply #1 on: September 26, 2014, 07:27:13 pm »
In the picture "IR device.png" of your IR Device ("UPC"), it looks like you've set the id_parent field to be "29", which is your IR Transmitter (SQBlaster) device.

Not sure how it got that way, but these IR Devices ("UPC") should not be parented to the IR Transmitter.  They're associated, but that's done differently, so the id_parent field should be left blank.


Internally, because the IR Transmitter (D_SQBlaster1.xml) has declared it will "handleChildren", then I suspect the IR Request you've made (against Device 30) is being forwarded to the implementation of the SQBlaster code (Device 29) because of the id_parent field being set.   If you clear the field out, then (Save) and retry then it should work better.

Offline Maartenvt

  • Full Member
  • ***
  • Posts: 146
  • Karma: +0/-0
Re: Assistance with setup...
« Reply #2 on: September 27, 2014, 09:59:33 am »
thnx!! it works

Happy!!!
Vera Edge (Firmware rev. 1.7.2406), 1x Düwi INTERACT³ light switch, 1x  ZIR010 Motion Sensor.

Offline Maartenvt

  • Full Member
  • ***
  • Posts: 146
  • Karma: +0/-0
Vera Edge (Firmware rev. 1.7.2406), 1x Düwi INTERACT³ light switch, 1x  ZIR010 Motion Sensor.


Offline guessed

  • Master Member
  • *******
  • Posts: 5294
  • Karma: +90/-22
  • Release compat is not a bolted-on afterthought
Re: Assistance with setup...
« Reply #5 on: September 27, 2014, 12:50:11 pm »
Yep, exactly - you send them to the [specific] IR Device, and internally they get translated to the codes and delivered to the IR Transmitter (SQBlaster).

You can also do this:

    http://VERA:49451/data_request?id=lu_action&DeviceNum=29&serviceId=urn:micasaverde-com:serviceId:IrTransmitter1&action=SendProntoCode&ProntoCode=<rawProntoCode>

where rawProntoCode is the string inside the <ir>...</ir> block of an IR Device... in case you just want to send a one-off IR command.  The value needs to be URL-escaped, and that's about it....

Offline Maartenvt

  • Full Member
  • ***
  • Posts: 146
  • Karma: +0/-0
Re: Assistance with setup...
« Reply #6 on: September 27, 2014, 01:25:20 pm »
Oke, just tested some commands.

http://VERA_IP:49451/data_request?id=lu_action&DeviceNum=29&serviceId=urn:micasaverde-com:serviceId:IrTransmitter1&action=SendProntoCode&ProntoCode=<L28 12500 dc060052 afef0052 1850052 13100ce 8b0052 de0052 8c9235 25515552 24254550 L28 12500 dc060052 afef0052 1850052 13100ce 8b0052 de0052 8c9235 25515555 24254550>

Above isn't working.

I have a lot of problems getting the ir codes to vera-sqremote. If SQ remote receives the command, its is sometimes 60 sec later. Most of the time it isn't working.

I tested the following posts:

data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:DiscretePower1&action=Off
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=1
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=2
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=3
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=4
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=5
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=6
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=7
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=8
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=9
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:NumericEntry1&action=10
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:Volume1&action=Down
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:Volume1&action=Up
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:Volume1&action=Mute
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Back
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Clear
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Down
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Exit
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Left
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Menu
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=MenuAlt
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=PageDown
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=PageUp
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Right
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Select
data_request?id=lu_action&DeviceNum=30&serviceId=urn:micasaverde-com:serviceId:MenuNavigation1&action=Up


with the following ip / port numbers:

http://10.0.1.8:49451/
http://10.0.1.8:3480/

Any idea?

I also see this log line in vera:
LOG_CHECK_MEMORY_LEAK pMem start 0x9b5000 now 0x9c9000 last 0x9b5000 leaked 81920 <0x803>

thnx
Vera Edge (Firmware rev. 1.7.2406), 1x Düwi INTERACT³ light switch, 1x  ZIR010 Motion Sensor.

Offline guessed

  • Master Member
  • *******
  • Posts: 5294
  • Karma: +90/-22
  • Release compat is not a bolted-on afterthought
Re: Assistance with setup...
« Reply #7 on: September 27, 2014, 01:37:14 pm »
You need to replace <rawProntoCode> with the RAW Pronto code, correctly escaped for use within a URL.

For your example, it'll be something like:

http://VERA_IP:49451/data_request?id=lu_action&DeviceNum=29&serviceId=urn:micasaverde-com:serviceId:IrTransmitter1&action=SendProntoCode&ProntoCode=L28+12500+dc060052+afef0052+1850052+13100ce+8b0052+de0052+8c9235+25515552+24254550+L28+12500+dc060052+afef0052+1850052+13100ce+8b0052+de0052+8c9235+25515555+24254550

using "+" as the URL encoding for space.  It might also be %20, if the + encoding doesn't cut it.

BTW: Your string looks like two learned codes glued together...

Offline guessed

  • Master Member
  • *******
  • Posts: 5294
  • Karma: +90/-22
  • Release compat is not a bolted-on afterthought
Re: Assistance with setup...
« Reply #8 on: September 27, 2014, 01:44:18 pm »
You can check the logs to see when Vera receives the command, and dispatches it to the remote.  If needed, enable Vera's verbose logs to get the extra detail.

Any delay after what's presented in the logs is coming from elsewhere (ie. SQBlaster itself), although I've not seen that.

The SQBlaster plugin itself fires off a HTTP request immediately, so the timing will be in Vera's log files.