openLuup email server

[PerH]

Ok, so i've looked into what happens. This is what is fed into the call_action at line 684 in luup.lua.

Format: e,m,j,a = dev: call_action (service, action, arguments, devNo)

Switching a local device from AltUI (Works):

e,m,j,a = dev: call_action ("urn:micasaverde-com:serviceId:SecuritySensor1", "SetArmed",{DeviceNum = "65", action = "SetArmed", newArmedValue = "1", serviceId = "urn:micasaverde-com:serviceId:SecuritySensor1"}, 65)

Switching a local device from Imperihome device (Works):

e,m,j,a = dev: call_action ("urn:micasaverde-com:serviceId:SecuritySensor1", "SetEnabled", {newArmedValue = "0"}, 65)

Switching a VeraBridge device from AltUI (Works):

e,m,j,a = dev: call_action ("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {DeviceNum = "10308", action = "SetTarget", newTargetValue = "1", serviceId = "urn:upnp-org:serviceId:SwitchPower1"}, 10308)

Switching a VeraBridge device from Imperihome device (Fails):

e,m,j,a = dev: call_action ("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTarget = "0"}, 10308)

No error messages in the luup log, just no end result.. Any ideas?

[akbooer]

So I notice that those requests use different parameter names: newTarget / newTargetValue.

This would certainly explain it.

The question is, where does this difference occur?

[PerH]

That was it.

/cgi/Imperihome.lua: Changed "newTarget" to "newTargetValue" at line 385, 672 and 675. (i would upload the updated lua file, but im missing priveleges)

This was not an issue before, has there been changes on this in openluup?

@mrFarmer - FYI

[akbooer]

Careful here.

Vera/MiOS has an appallingly bad trait of using different names for the same thing in different places. It's worthwhile checking the documentation between the action Luup call and the HTTP request. I'm not aware of a significant change in openLuup in this area, but have vivid recollections of the pains that this put me through in the relatively early stages of development.

I might be wrong, it could be a latent error lain undiscovered for years, but you're perhaps in a better position than I to investigate this (I don't use, or even have, Imperihome.)

[krisztianszabo]

@perh said in Imperihome - missing devices:

That was it.

/cgi/Imperihome.lua: Changed "newTarget" to "newTargetValue" at line 385, 672 and 675. (i would upload the updated lua file, but im missing priveleges)

This was not an issue before, has there been changes on this in openluup?

@mrFarmer - FYI

I modified the right lines, it really works now!
At the same time, I can see the icons on the imperihome flashing as if they are constantly reloading ...

[krisztianszabo]

@PerH, haven't you experienced this?

[PerH]

the icons flashing? No, but i think i turned a setting off somewhere in the app about refresh, not sure where. Mine are set to manual reload only.

I'll see what i can do @akbooer, it works now, but we'll see when i get more device type in..

[PerH]

EDIT: code improved after strict correction.

Finally got all devices into imperihome.

ran this script in "test code":

local oldparent = 198
for i, d in pairs (luup.devices) do
  if d.device_num_parent == oldparent then
    if d.device_type == "urn:schemas-upnp-org:device:BinaryLight:1" then
        if d.category_num == 0 then
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
            luup.attr_set("category_num", 3, i)
            if d.subcategory_num == 0 then
                luup.attr_set("subcategory_num", 1, i)
            end
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
        end
    end

    if d.device_type == "urn:schemas-upnp-org:device:DimmableLight:1" then
        if d.category_num == 0 then
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
            luup.attr_set("category_num", 2, i)
            if d.subcategory_num == 0 then
                luup.attr_set("subcategory_num", 3, i)
            end
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
        end
    end      
    
    if d.device_type == "urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1" then
        if d.category_num == 0 then
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
            luup.attr_set("category_num", 5, i)
            if d.subcategory_num == 0 then
                luup.attr_set("subcategory_num", 1, i)
            end
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
        end
    end    
    
    if d.device_type == "urn:schemas-micasaverde-com:device:SceneController:1" then
        if d.category_num == 0 then
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
            luup.attr_set("category_num", 14, i)
            if d.subcategory_num == 0 then
                luup.attr_set("subcategory_num", 0, i)
            end
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
        end
    end  
    
    if d.device_type == "urn:schemas-micasaverde-com:device:DoorSensor:1" then
        if d.category_num == 0 then
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
            luup.attr_set("category_num", 4, i)
            if d.subcategory_num == 0 then
                luup.attr_set("subcategory_num", 1, i)
            end
            print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
        end
    end  
    
    if d.category_num == 0 then
        print (i, d.name, d.device_type, d.category_num, d.subcategory_num)
    end    
  end
end
return true

It took a while before they actually sticked, and survived luup reloads, and they still arent updated in the openluup or altui gui?

anyway, it works! Still have to rerun this script when i add new/other devices though, but thats how it is.

[akbooer]

@perh

It is quite incorrect to try and change device attributes by writing to them directly. Not sure where this code came from, but it is wrong. The function luup.attr_set() is what you need to use.

[PerH]

hehe, the code comes from an amateur just trying shit out.

I'll look that up and modify the previous post.

[mrFarmer]

The newTargetValue for BinarySwitch is correct and my current code is wrong. I am making updates and expect to publish them one of these days. I never noticed it to be wrong as I control all standard devices on the Veras rather than through openLuup. I might change this so in imperihome I only need the openLuup device setup and no longer the Vera's. The latter loose their connection frequently so I would solve that too.

Cheers Rene

[PerH]

Sound good, Any chance of getting it into altAppStore? nice to have the automatic updates.

One thing the code I mentioned does not to is to update categories of the children of combodevices. You can however just rerun the code with the combodeviceID as parent.

[akbooer]

@mrfarmer said in Imperihome - missing devices:

From what I could see is that the z-way devices are not having a category or subcategory number set.

Latest development release of the ZWay plugin (v20.11.24) sets category_num...

https://smarthome.community/topic/71/openluup-z-way-bridge-version-log?_=1606232724236

[mrFarmer]

@PerH , as this is a CGI file and not a plugin it cannot go into the app store.

AK, nice to hear of your update to set de device types as I am struggling with the last few. If you only look at the device type then you cannot distinguish some devices like HVAC vs Heater. Means I need to do a little more work on it.

Cheers Rene

[akbooer]

@mrfarmer said in Imperihome - missing devices:

If you only look at the device type then you cannot distinguish some devices like HVAC vs Heater.

Perfectly true, but I had to leave something for you to do.