ALTHue : Feature Requests

Plugins & Plugin Development ALTHue
81

[quote=“cybrmage, post:80, topic:199107”]Also note:

In ALTUI (under both UI7 and openLuup), the warm white/cool white selections sliders (for color temperature selection) are not displayed in the control panel… This appears to be an issue with processing the D_DimmableRGBLight1.json file.

Under openLuup, the color selection dropdown on the device page does not display the correct color, the color selection dropdown in the device control panel does display the correct color.[/quote]
What?s the value of currentcolor variable in both case

The display of the file is a bigger pb. Ui7 does not follow the file and hard code a display ( like it does for?most Built in devices). I think a custom panel for altui would be a better option and not care about ui7. This is a simple JS method declared as a Altui plugin in case somebody is interested to contribute to it. Also the upnp setcolor with the syntax Wxxx or Dxxx should work to set the color temp of the light

82

This update works for bulbs in colormode=“xy”, but will not update any bulbs in colormode=“ct” or colormode=“hs”. Any bulb that has been set to a specific color temperature in the hue app(s) will be in ct mode, and selecting certain color values in gamut B (older) bulbs will set them to “hs” mode.[/quote]
v0.97 in github should support all modes

83

Just ordered a hub… can’t wait to give this all a go!

84

This update works for bulbs in colormode=“xy”, but will not update any bulbs in colormode=“ct” or colormode=“hs”. Any bulb that has been set to a specific color temperature in the hue app(s) will be in ct mode, and selecting certain color values in gamut B (older) bulbs will set them to “hs” mode.[/quote]
v0.97 in github should support all modes[/quote]

I can confirm that it is working. Only one more thing: the color control does not appear to work with “Friends of Hue” devices. I have a couple of Hue Iris (LLC010) and Hue Bloom (LLC011) which the vera plugin supports. I am sure other FOH don’t work either.

I suspect changing their implementation and device files from the dimmable to the RGB ones should fix it?

85

What are friend of hue devices ? Are they 3rd party devices ? Could you send me the hue data Json ( settings tab ).

86

They are actually Philips devices but from a series called “friends of hue”.
I have no settings tab because the json used is for the standard dimmable light D_DimmableLight1.xml, D_DimmableLight1.json… It is run through the plugin but does not use the plugin files.

https://www2.meethue.com/en-us/friends-of-hue
https://www2.meethue.com/en-us/p/hue-bloom/729976049
https://www2.meethue.com/en-us/p/hue-white-and-color-ambiance-go-portable-light/714606048

Edit: I verified that changing the device json and xml files in the attributes to D_DimmableRGBLight1.xml and D_DimmableRGBLight1.json works. So I think it is just a matter for the plugin to recognize them and assign the right files for the devices.

87

[quote=“rafale77, post:86, topic:199107”]They are actually Philips devices but from a series called “friends of hue”.
I have no settings tab because the json used is for the standard dimmable light D_DimmableLight1.xml, D_DimmableLight1.json… It is run through the plugin but does not use the plugin files.

https://www2.meethue.com/en-us/friends-of-hue
https://www2.meethue.com/en-us/p/hue-bloom/729976049
https://www2.meethue.com/en-us/p/hue-white-and-color-ambiance-go-portable-light/714606048

Edit: I verified that changing the device json and xml files in the attributes to D_DimmableRGBLight1.xml and D_DimmableRGBLight1.json works. So I think it is just a matter for the plugin to recognize them and assign the right files for the devices.[/quote]

I know it will work but not manually as it will be reset at every reload
the Settings tab I am talking about is a setting tab on the AltHue Plugin itself

88

I see.

This is for the iris:

"11": { "productname": "Hue iris", "capabilities": { "streaming": { "renderer": true, "proxy": false }, "control": { "mindimlevel": 10000, "colorgamuttype": "A", "colorgamut": [ [ 0.704, 0.296 ], [ 0.2151, 0.7106 ], [ 0.138, 0.08 ] ], "maxlumen": 210 }, "certified": true }, "manufacturername": "Philips", "swversion": "5.105.1.21778", "state": { "hue": 64000, "effect": "none", "on": false, "colormode": "hs", "sat": 254, "mode": "homeautomation", "reachable": true, "xy": [ 0.6795, 0.2858 ], "alert": "none", "bri": 1 }, "config": { "function": "decorative", "direction": "upwards", "archetype": "hueiris" }, "swupdate": { "state": "noupdates", "lastinstall": "2017-12-28T19:41:32" }, "name": "Bonus Iris", "type": "Color light", "modelid": "LLC010", "uniqueid": "XXXXXXXXXX" },

And this is for the bloom:

"13": { "productname": "Hue bloom", "capabilities": { "streaming": { "renderer": true, "proxy": false }, "control": { "mindimlevel": 10000, "colorgamuttype": "A", "colorgamut": [ [ 0.704, 0.296 ], [ 0.2151, 0.7106 ], [ 0.138, 0.08 ] ], "maxlumen": 120 }, "certified": true }, "manufacturername": "Philips", "swversion": "5.105.1.21778", "state": { "hue": 41422, "effect": "none", "on": false, "colormode": "xy", "sat": 39, "mode": "homeautomation", "reachable": true, "xy": [ 0.3909, 0.3713 ], "alert": "none", "bri": 1 }, "config": { "function": "decorative", "direction": "upwards", "archetype": "huebloom" }, "swupdate": { "state": "noupdates", "lastinstall": "2017-12-28T19:39:59" }, "name": "Bloom 3", "type": "Color light", "modelid": "LLC011", "uniqueid": "XXXXXXXX" } },

89

Also strangely, it has not reset after the last luup reload…

90

ok, I have put 0.98 in github with the (hopeful) fix

91

I ran the upgrade and it seems to work though I cannot be 100% sure since I made it work by manually changing the device files before the upgrade. It just did not revert to the default dimmer files.

92

My Hue has just arrived, so I can now join in the fun!

93

Absolute magic!

The install process couldn’t possibly be easier:

[ul][li]plugin hub[/li]
[li]plugin bulbs[/li]
[li]plugin ALTHue plugin, and set IP address[/li]
[li]press the pair buttons on hub and plugin panel[/li]
[li]Shazzam! we are there with functioning devices!![/li][/ul]

Imagine if Z-wave was that easy !!

One gripe: the log file entries…

2018-04-18 17:28:51.971   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068921 now: 1524068931 #hooks:0
2018-04-18 17:28:51.983   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068931 now: 1524068931 #hooks:0
2018-04-18 17:29:02.502   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068931 now: 1524068942 #hooks:0
2018-04-18 17:29:02.514   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068942 now: 1524068942 #hooks:0
2018-04-18 17:29:13.045   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068942 now: 1524068953 #hooks:0
2018-04-18 17:29:13.057   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068953 now: 1524068953 #hooks:0

Can we cut down on this a bit? … or am I still in debug mode?

94

[quote=“akbooer, post:93, topic:199107”]Absolute magic!

The install process couldn’t possibly be easier:

[ul][li]plugin hub[/li]
[li]plugin bulbs[/li]
[li]plugin ALTHue plugin, and set IP address[/li]
[li]press the pair buttons on hub and plugin panel[/li]
[li]Shazzam! we are there with functioning devices!![/li][/ul]

Imagine if Z-wave was that easy !!

One gripe: the log file entries…

2018-04-18 17:28:51.971   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068921 now: 1524068931 #hooks:0
2018-04-18 17:28:51.983   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068931 now: 1524068931 #hooks:0
2018-04-18 17:29:02.502   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068931 now: 1524068942 #hooks:0
2018-04-18 17:29:02.514   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068942 now: 1524068942 #hooks:0
2018-04-18 17:29:13.045   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068942 now: 1524068953 #hooks:0
2018-04-18 17:29:13.057   luup.variable_set:: 345.urn:upnp-org:serviceId:althue1.LastValidComm was: 1524068953 now: 1524068953 #hooks:0

Can we cut down on this a bit? … or am I still in debug mode?[/quote]
great. I commited a version on github to address that

95

Formidable!

I noticed this when updating the plugin:

are you sure you want to update plugin #d117c862-8caf-4711-b0f8-11cdf457f290

…you’re using a UUID for the plugin id?

96

[quote=“akbooer, post:95, topic:199107”]Formidable!

I noticed this when updating the plugin:

are you sure you want to update plugin #d117c862-8caf-4711-b0f8-11cdf457f290

…you’re using a UUID for the plugin id?[/quote]

You mean in AltAppStore ? I saw this now and updated it to the true MCV pluginID, but the web interface does not allow that kind of update so I had to update it directly in the database and god knows what kind of side effect this can have… beware!

97

Actually, it was when using the Update button from the Plugins page.

But it’s part of the [tt]InstalledPlugins2[/tt] structure that comes from the App store. If you had put ALTHue in the MiOS app store, it would be a simple number (like AltUI is 8246.)

{
	 AllowMultiple = 0,
	 AutoUpdate = 1,
	 Description = "Alternate plugin for Philips Hue",
	 Devices = {{
	 	 	 DeviceFileName = "D_ALTHUE.xml",
	 	 	 DeviceType = "urn:schemas-upnp-org:device:althue:1",
	 	 	 ImplFile = "I_ALTHUE.xml",
	 	 	 Invisible = "0"
	 	 }},
	 Files = {{SourceName = "L_ALTHUE.lua"},{SourceName = "D_ALTHUE.json"},{SourceName = "D_ALTHUE_UI7.json"},{SourceName = "J_ALTHUE.js"},{SourceName = "I_ALTHUE.xml"},{SourceName = "S_ALTHUE.xml"},{SourceName = "D_ALTHUE.xml"}},
	 Icon = "https://raw.githubusercontent.com/amg0/ALTHue/master/iconALTHUE_100.png",
	 Instructions = "https://github.com/amg0/ALTHue",
	 Repository = {
	 	 folders = {""},
	 	 pattern = "ALTHUE",
	 	 source = "amg0/ALTHue",
	 	 type = "GitHub",
	 	 versions = {master = {release = "master"}}
	 },
	 Title = "ALTHue",
	 VersionMajor = "GitHub",
	 VersionMinor = "master",
	 id = "d117c862-8caf-4711-b0f8-11cdf457f290"
}

I was just trying to understand why.

98

Actually, it was when using the Update button from the Plugins page.

But it’s part of the [tt]InstalledPlugins2[/tt] structure that comes from the App store. If you had put ALTHue in the MiOS app store, it would be a simple number (like AltUI is 8246.)

{
	 AllowMultiple = 0,
	 AutoUpdate = 1,
	 Description = "Alternate plugin for Philips Hue",
	 Devices = {{
	 	 	 DeviceFileName = "D_ALTHUE.xml",
	 	 	 DeviceType = "urn:schemas-upnp-org:device:althue:1",
	 	 	 ImplFile = "I_ALTHUE.xml",
	 	 	 Invisible = "0"
	 	 }},
	 Files = {{SourceName = "L_ALTHUE.lua"},{SourceName = "D_ALTHUE.json"},{SourceName = "D_ALTHUE_UI7.json"},{SourceName = "J_ALTHUE.js"},{SourceName = "I_ALTHUE.xml"},{SourceName = "S_ALTHUE.xml"},{SourceName = "D_ALTHUE.xml"}},
	 Icon = "https://raw.githubusercontent.com/amg0/ALTHue/master/iconALTHUE_100.png",
	 Instructions = "https://github.com/amg0/ALTHue",
	 Repository = {
	 	 folders = {""},
	 	 pattern = "ALTHUE",
	 	 source = "amg0/ALTHue",
	 	 type = "GitHub",
	 	 versions = {master = {release = "master"}}
	 },
	 Title = "ALTHue",
	 VersionMajor = "GitHub",
	 VersionMinor = "master",
	 id = "d117c862-8caf-4711-b0f8-11cdf457f290"
}

I was just trying to understand why.[/quote]

yes I do not know how it happened, It is in MCV store so I do have a normal integer ID which I have also put now in the AltAppStore DB.

99

OK, understood (at last!)

It means that any openLuup installation with the wrong plugin ID will have to update ALTHue from the AltAppStore before being able to update directly from the Plugin page once more.

No problem, if this procedure followed.

100

@amg0:

Here are the proposed changes.

<changes received by amg0, attachment removed>