Ok…done quite a few more updates…including a re release of the groovy files…I did have some organically grown bugs on discovering bulbs in the smart app. I have reduced the logging in the server, hope I don’t regret that.
Could you reinstall and try again.
Ah…The ‘Scene’ Setting on the Smart App (which does nothing yet) is mandatory…Ill fix that now, but if you set it to anything it should allow the bulbs to be created
Ok…I changed that problem with the scene setting…just the smartapp needs to be changed…
Just pushed another set of changes…Mainly allowing the Transition effects supported by Yeelights to be supported. There are two settings Transition and Transition Speed. Transition can be either smooth or sudden and if smooth…then transition speed should be the number of milliseconds that the relevant action will take.
I am afraid all files changed…so a full release will be needed
Enjoy!!!
Hi @Davec when I try to update the DTH I am given this error:
Org.springframework.dao.DuplicateKeyException: a different object with the same identifier value was already associated with the session: [physicalgraph.device.CapabilityDeviceType#physicalgraph.device.CapabilityDeviceType : (unsaved)]; nested exception is org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [physicalgraph.device.CapabilityDeviceType#physicalgraph.device.CapabilityDeviceType : (unsaved)]
Many thanks
Blimey…never seen anything like that before… At what point did you get that? was that when you were saving the devicehandler? Maybe delete it and recreate?
I think it is because the capablities are duplicated - I commented out the duplicates and was able to publish. I’m still trying to discover devices at this moment as just finished setting up the server on my RPi…how long does it usually take to discover the bulbs?
5 mins…you should see the server (syslog) discover them first (Provided the bulbs are in developer mode)
the syslog should look at bit like this
server.js[24149]: onDevConnected: Creating SSDP Server for did=0x00000000035ac1c1 name= MAC=34CE0080E462 location=http://192.168.1.55:8082/light dev location=192.168.1.66:55443
server.js[24149]: onDevConnected: Creating SSDP Server for did=0x00000000035c3205 name= MAC=34CE008254A6 location=http://192.168.1.55:8082/light dev location=192.168.1.67:55443
This means the server can see the devices
Actually 2 or 3 mins
So I’m starting the server and check status and it looks like it’s active but then checking the status again then shows that it has stopped - any ideas:
All other steps to this point have gone smoothly…
Could you see if there are more useful messages in syslog?
Yes that’s at the point of saving. I actually already tried deleting and recreating the DTH. Same result.
mmmh…do the devices exist? I am a bit stumped with this…Perhaps a smartthings expert could help?
I guess you can try
Ah yes…ok its a node.js version thing I think
can you type node -v and let me know the result
I think this is an IDE/Smartthings eccentricity…I suspect your environment has become a little confused. If this was me I would attempt to remove all trace of the yeelight stuff, first make sure there are no devices present (in the device list) then remove the smartapp then the device handler and then restart the hub
Again, if this was me and I still had problems, I would rename the device handler…but this would put me in uncharted territory from a support perspective.
Sorry, I guess I need to add instructions on how to update the device handler and smart app. When I release a new version (of either dh or smarthandler), I go into edit mode on the ide, clear the current code and paste in the new code.
The version after entering node -v is v0.10.29
Yes the way you described your update process is exactly how I do it. I’ll start again from scratch tonighy and see how it goes.
OK that worked. I was able to add my four bulbs to smartthings. Yay. Unfortunately they don’t turn on. The button just hangs at ‘Turning on’.
Yikes! ok progress is slow sorry…
can you post the output from yeelight-connect and the smartbulb (using livelogging in the ide)
and also the server log from syslog
