Author Topic: Is there something wrong with LUUP since last firmware upgrade?  (Read 185 times)

Offline konradwalsh

  • Hero Member
  • *****
  • Posts: 560
  • Karma: +18/-6
Hey
I have had a script run for years:
Code: [Select]
local astatus = luup.variable_get("urn:micasaverde‐com:serviceId:AlarmPartition2","DetailedArmMode",53)
Suddenly it stopped working..
So I was testing in luup code test and it returns nil.
Now I assume its that device so I start checking random devices and all return nil, whether I am checking loadlevel or getstatus or any variable.

Next I tested just the http command for the same
Code: [Select]
http://192.168.2.3/port_3480/data_request?id=variableget&output_format=xml&DeviceNum=53&serviceId=urn:micasaverde%E2%80%90com:serviceId:AlarmPartition2&Variable=DetailedArmMode
This returns a blank page.
So I tested from the command line with curl -i to see the headers and sure enough it executes but no data returned

The last thing i checked was whether this had anything to do with 'Secure My Vera' but it doesn't.

All testing was done on a VeraPlus

Is this just me or can someone confirm?

Offline reneboer

  • Hero Member
  • *****
  • Posts: 1011
  • Karma: +52/-30
Re: Is there something wrong with LUUP since last firmware upgrade?
« Reply #1 on: March 10, 2017, 05:10:14 am »
Hi,

Well, if luup.variable_get stopped working or got changed every plugin would crash and burn, so must be something else.

Did the variable or SID maybe disappear in the latest release? I do not have a device using the AlarmPartition2 so cannot check my self.

Cheers Rene

2xVeraLite, VeraEdge, openLuup, ALTUI, 20 switches, 10 dimmers, 20 sensors, 10 scene controllers, 1 Harmony Hub, many plug-ins. Not enough time.

Offline konradwalsh

  • Hero Member
  • *****
  • Posts: 560
  • Karma: +18/-6
Re: Is there something wrong with LUUP since last firmware upgrade?
« Reply #2 on: March 10, 2017, 05:14:20 am »
Hi,

Well, if luup.variable_get stopped working or got changed every plugin would crash and burn, so must be something else.

Yes of course.. .its strange



Did the variable or SID maybe disappear in the latest release? I do not have a device using the AlarmPartition2 so cannot check my self.

Thats why I tried loads of other variables and I am not getting returned data.

I presume you can do a HTTP request then with any of your devices and you are on the latest firmware?


Offline reneboer

  • Hero Member
  • *****
  • Posts: 1011
  • Karma: +52/-30
Re: Is there something wrong with LUUP since last firmware upgrade?
« Reply #3 on: March 10, 2017, 07:43:24 am »
Hi,

Yes it all works as expected with the latest release. Running on Lite and Edge. Have you tried another variable on an other device?

As Vera is adding security stuff, may this be the issue? Scrolling through the forum this file was added in support of several alarm plugins, but not used by an standard device.

Cheers Rene
2xVeraLite, VeraEdge, openLuup, ALTUI, 20 switches, 10 dimmers, 20 sensors, 10 scene controllers, 1 Harmony Hub, many plug-ins. Not enough time.

Offline rafale77

  • Hero Member
  • *****
  • Posts: 611
  • Karma: +30/-20
Re: Is there something wrong with LUUP since last firmware upgrade?
« Reply #4 on: March 10, 2017, 11:57:21 am »
Might be completely unrelated but I am observing some odd behavior with plugins failing communication if the luup engine has not reloaded for more than 36hrs. Have you tried after reloading luup?
112 zwave nodes, 8 zigbee nodes, 231 devices, 17 apps, 100 scenes on a Vera Plus linked with Echo and HomeKit through bridges

Offline shallowearth

  • Hero Member
  • *****
  • Posts: 819
  • Karma: +38/-8
Re: Is there something wrong with LUUP since last firmware upgrade?
« Reply #5 on: March 10, 2017, 12:07:59 pm »
Oh had some weird problem where if I had copied and pasted the LUA from another scene it wouldn't work, but if I typed it fresh or it copied to notepad first then made a copy from note pad back to the browser it was fine.
Probably has to do with some hidden encoding character from the changes they made resently.