What’s odd is these are files directly out of my production system and my system is working - no errors. I had some issues last night and I did upload v2 but then pulled it off (discovered another problem) and later re-packaged after extensive testing. I checked and it said no one had downloaded the file. I know it’s a pain but can you re-download the package above and copy all the files over again. I just want to be absolutely sure …
downloaded version 2 still getting message in logfile waiting for end in line 193. added at end of function reloaded getting this message
“2015-11-20 13:33:05.838 luup_log:4: (Hue2 Plugin)::(Startup) : Initiating
2015-11-20 13:33:05.896 openLuup.context_switch:: ERROR: ./L_PhilipsHue2.lua:208: attempt to index global ‘lul_settings’ (a nil value)
2015-11-20 13:33:05.896 openLuup.scheduler:: job aborted : ./L_PhilipsHue2.lua:208: attempt to index global ‘lul_settings’ (a nil value)”
no variables shown again
I take responsibility, it was a case whereby I had many versions lurking on my system. I repackaged last night, loaded on my system and all everything appeared fine. After posting the files, I started to lurk through my logs and noticed errors for Philips. Well my lights appeared to be working but they had issues.
So I pulled the package off and cleaned off all the various versions I had then repackaged, re-tested and was happy with the results.
Glad to hear everything is working, again - I apologize for that. I honestly didn’t think anyone had grabbed those files as the download counter indicated 0.
Seems there’s a new bridge update available. Be mindful that this may or may not break the plugin itself. MCV is looking into an update to the plugin so i’ll wait for that to be released so I can formally test and release a new package.
Bridge API 1.11 (published 09/12/2015)
Changes to the Lights API.
1.1.2, 1.4.2 and 1.4.4, Added a note saying point symbols are no longer used. Deprecated
Changes to the Groups API.
2.1.4. Added new "Room" group description.
2.1.4. Added allowed Room classes.
2.2.2. Added example for creating a Room.
Changes to the Scenes API.
4.1.1 Modified description.
4.1.2 Added descriptions for new fields: owner, locked, picture and version.
4.1.3 Added JSON Example for a scene created with 1.11.
4.1.4 Added note saying active flag is no longer returned from the bridge. Deprecated
4.2 Added description on new way of creating scenes
4.3 Added description on new way of modifying scenes
4.3.2 Added description for new storelightstate field
4.3.3 and 4.3.4 Added JSON examples for modifying scene names/lights and storing the current values.
4.5 Delete scenes description added
4.6 Get scene description added
Changes to the Error messages.
Added 306, 403, 706, 801, 802 and 803 error codes
Have now updated to Hue bridge 2, which worked well with the plugin. However an upgrade to the bridge at the weekend meant that the plugin no longer works on openLuup. As a temporary measure I have reinstalled the MCV App on my Vera edge to give me back some of the automation, this does work.
I’m finally back from vacation… So nice ! I’m curious, how was the transition from Bridge 1.0 to 2.0. I have tons of bulbs and I’ve heard both success stories and horror stories. Have you tried to remove the files off openLuup and copy just the core files for Philips Hue over (from your Vera) to see if it’ll configure off the shelf ? Again I’m curious…
I do know the latest plugin removes support for all non P-Hue bulbs (boo).
@cudanet
Transition from 1.0 to 2.0 was easy, but I only have 9 hue lights. Tried removing openLuup files and replacing with Mios hue files, no success.
By the way according to Philips the new software enables recognition of non P-hue lights just doesn’t guarantee that they will work properly.
Sounds good, I was concerned as I’ve heard stories of people having issues accomplishing the transition. Sounds like they might have it worked out now. I’ve dusted off my rPi2 but right now we’re troubleshooting an issue for the Honeywell plugin. This might take some time as it takes around 48 hours to reach a failure.
After that I’m hoping we can get the Sonos plugin solid (multiple Sonos systems) then move on to the Philips Hue bulbs (latest) then ultimately to the Nest plugin (latest from MCV).
[quote=“dsroberts1945, post:76, topic:189406”]@cudanet
Transition from 1.0 to 2.0 was easy, but I only have 9 hue lights. Tried removing openLuup files and replacing with Mios hue files, no success.
By the way according to Philips the new software enables recognition of non P-hue lights just doesn’t guarantee that they will work properly.[/quote]
Hmm, it looks like the plugin is still being evaluated by MCV for the latest bridge firmware. Hopefully they have this sorted by the time I get around to seeing If I can even load it. It does appear the Nest plugin is stable, I might have a go at that one again if the Hue hasn’t been corrected.
Placed an order for the bridge 2.0, I’ll move 1 bulb over for testing and update this thread…Might be awhile though…
[quote=“dsroberts1945, post:76, topic:189406”]@cudanet
Transition from 1.0 to 2.0 was easy, but I only have 9 hue lights. Tried removing openLuup files and replacing with Mios hue files, no success.
By the way according to Philips the new software enables recognition of non P-hue lights just doesn’t guarantee that they will work properly.[/quote]
Got my bridge last night… Sure wish this thing was POE as my cats love to chew through these cheap power wires. Now to find some decent instructions on moving the bulbs…
[quote=“CudaNet, post:79, topic:189406”]Placed an order for the bridge 2.0, I’ll move 1 bulb over for testing and update this thread…Might be awhile though…
[quote=“dsroberts1945, post:76, topic:189406”]@cudanet
Transition from 1.0 to 2.0 was easy, but I only have 9 hue lights. Tried removing openLuup files and replacing with Mios hue files, no success.
By the way according to Philips the new software enables recognition of non P-hue lights just doesn’t guarantee that they will work properly.[/quote][/quote]
