Excellent! The trick to this ever expanding ‘hobby’ of ours is remembering what our old pistons are doing when programming new pistons. (so they do not conflict)
Great detective work!
Volume adjuster doesn't work
joelw135
#42
I agree, but I do believe that there is a problem between WebCoRE Pistons and volume and SmartThings. I say this is because if you have another SmartApp that has volume set at 45% and a Piston set at 45% some how they interfere with each other. I removed the volume from a SmartApp and now the Piston works. I also setup a alert in FING if the IP of my Speaker changes.
WCmore
#43
It has been awhile, but if memory serves me right, the speaker that I worked on in the past showed 0-60 volume when in webCoRE, but using a ST routine it had showed 0-100. (using your example, 45 in one app was not the same when viewed in another)
I do not remember which speaker it was, but the solution (for me) was simply to let webCoRE handle all the requests.
StevenJonSmith
#44
If your router supports it you could give the speaker a host name, then if the IP changes the router will still recognise the name and route the requests correctly. Then in the URL just replace the IP address with the hostname, just don’t set two things to have the same host name or it will likely fail (though I would expect the router to stop you doing so).
joelw135
#45
Yes I am well aware of that but I have FIOS. Now FIOS router is pure junk and I have a Airport Extreme Base-station plugged into the FIOS router in Bridge Mode. That prevents me from using any advanced networking. I then have another Airport Extreme Base-Station to extend the network. So some devices and one of the speakers is connected to the last Base-Station. So again no advanced networking. I wish FIOS would come up with a better router. Even their newest is pure junk but better than the last. I could have trid to setup the first Base-Station in other than Bridge mode, but then you get the double nat errors.