Announcement

Collapse
No announcement yet.

HSZigbee Now In Beta

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Crashless
    replied
    I've been getting a (501) Not Implemented error lately with my Osram lights - is anyone else having issues? Already got new keys, etc...

    Leave a comment:


  • slbuck
    replied
    I've moved on to the mcsMQTT plugin and it works flawlessly. I'm running mosquitto and zigbee2mqtt on a raspberry pi zero w that has a $10 zigbee dongle attached and can now controll my sylvania lightify gardenspot lights locally with no internet required. I'm checking to see if I can run any of the color lighting effects that are available via the mobile app, but other than that, things are working very well.

    Leave a comment:


  • logman
    replied
    Originally posted by slbuck View Post

    Yes, I forgot to include that I can control them with no issues via the app. The gateway shows connected both locally and with the cloud.
    That makes me wonder if Lightify has made a change to their API again. Or HS may need to refresh their developer's credentials. You should drop HS support an email and some screenshots. Odd that nobody else has complained. But then again I don't think too many people are using the plugin and most have migrated to JowiHue plugin.

    --Barry

    Leave a comment:


  • slbuck
    replied
    Originally posted by logman View Post

    Can you control them direct from the Lightify app?

    --Barry
    Yes, I forgot to include that I can control them with no issues via the app. The gateway shows connected both locally and with the cloud.

    Leave a comment:


  • logman
    replied
    Originally posted by slbuck View Post
    Anyone else having any issues controlling their lights via this plugin? I started getting this error when controlling the lights starting a couple of days ago. I regenerated new access and refresh tokens, but this did not help.
    ZigBee Error: Command returned an error: The remote server returned an error: (401) Unauthorized.
    Can you control them direct from the Lightify app?

    --Barry

    Leave a comment:


  • slbuck
    replied
    Anyone else having any issues controlling their lights via this plugin? I started getting this error when controlling the lights starting a couple of days ago. I regenerated new access and refresh tokens, but this did not help.
    ZigBee Error: Command returned an error: The remote server returned an error: (401) Unauthorized.

    Leave a comment:


  • tenholde
    replied
    I have 10 Keen Vents working perfectly, directly interfaced to HS3 with no cloud involvement, using an inexpensive ConBee (Zigbee) USB stick and the JowiHue HS plugin. Be glad to share details.

    Leave a comment:


  • Michael McSharry
    replied
    A low cost non-cloud solution is at https://forums.homeseer.com/forum/li...ailable-for-10

    Leave a comment:


  • logman
    replied
    Originally posted by Michael McSharry View Post
    Is this still a could-based solution via the OSRAM gateway?
    Yes, the HS plugin is still cloud-based via Osram API... But I wouldn't call it a solution.

    Leave a comment:


  • Michael McSharry
    replied
    Is this still a could-based solution via the OSRAM gateway?

    Leave a comment:


  • logman
    replied
    Yep, I'm a dummy. I somehow had in my mind that you needed a HS3 virtual device in ST for EACH sensor. But nope. The one HS3 virtual device does the routing for multiple ST devices. You just deploy a new instance of the appropriate app for each sensor you want to monitor. I got it now, and it works!

    This is an awesome solution for Zigbee sensors (motion, contact, leak detectors, switches, etc.). Actually HS could probably spend a little time working on this and have it import all your devices in from ST and take care of the scripting in the background to update ST devices with HS3 changes. Or somebody could develop a plugin without too much effort to do the same thing.

    Thanks again!

    --Barry

    Leave a comment:


  • fuzzysb
    replied
    logman I don't understand why you need another device with the same dni? You only have one HS3 api device. Any virtual switches etc don't need the same dni, you can give them anything. I usually put in the same as the device name.

    It's only the HS3 device that needs the hex IPort combo

    Leave a comment:


  • logman
    replied
    Hey fuzzysb,

    I've been working with this today to get Zigbee to Homeseer functioning for a few NYCE sensors. Worked great on the first device, but I hit a wall on getting the second device to report back to Homeseer. Looking at your device handler code (and thanks for providing this!), I noticed this at the bottom:

    Code:
    }
    
    def ipSetup() {
        log.debug "In IPSetup Area"
        def hosthex
        def porthex
        if (settings.ip) {
            hosthex = convertIPtoHex(settings.ip).toUpperCase()
        }
        if (settings.port) {
            porthex = convertPortToHex(settings.port).toUpperCase()
        }
        if (settings.ip && settings.port) {
            log.debug "updating Network ID to ${hosthex}:${porthex}"
            device.deviceNetworkId = "${hosthex}:${porthex}"
        }
    }
    
    private String convertIPtoHex(ip) { 
        String hexip = ip.tokenize( '.' ).collect {  String.format( '%02x', it.toInteger() ) }.join()
        return hexip
    }
    private String convertPortToHex(port) {
        String hexport = port.toString().format( '%04x', port.toInteger() )
        return hexport
    }

    That converts the destination IP and port (of the host HS3 machine) to hex and then uses the result to update the Device Network ID of the virtual device created in SmartThings. I'm assuming the ST API requires the local LAN IP:PORT address to be converted to hex value for some reason and looks to the NetworkID for the result.

    The problem is that SmartThings requires the NetworkID to be unique to each device. So when you try to add a second device the Network ID will not get updated because it would be a duplicate. In return the API never sends the command to HS3 because it doesn't have an address to send to.

    Any ideas or know of a workaround?

    --Barry


    Originally posted by fuzzysb View Post
    ok if anyone is interested and i apologise hijacking the thread a bit. i have uploaded my Smartthings connectivity code to github.

    first add the following device handler available here to smartthings.

    then create a new device and select this device handler. in the device settings specify the internal IP address of your homeseer server and the web port.

    next add all the 5 smartapps available here

    at the moment you can send Contact/Motion/Presence & Switch Statuses to Homeseer devices.

    so to do this create a new device in homeseer and for Status ensure that the homeseer device has these values

    Switch
    0 = Off
    100 = On

    Contact & Motion
    0=Closed/NoMotion
    1=Open/Motion

    Presence
    0=Away
    1=Home

    Then take note of the Homeseer Reference Id

    then just go into the smartthings app for example and install an instance of the Contact Sensor to HS3 App and select the Contact sensor which you want to send the status of, select the Homeseer HS3 device and specify the Homeseer Device ID.

    then just open/close the sensor and you will see that the status of the virtual device is updated.

    The Homeseer device handler can be updated to subscribe to more types etc.. quite easily. then you just need a smartapp to initiate the send of the status.

    and lastly i have another which will synchronize the switch state between HS3 virtual device and ST, so you can turn on the switch on either platform and the status will be reflected in another.

    much the same as the other smartapps however you need to enable oAuth in the smartapp settings. then find the app id and token from the smartapp settings once you have installed it and selected the switch device and specified the HS3 Device Id.

    then i create an event in Homeseer where i specify if the homeseer device switch changes off i then run a script or script command and specify and select to execute an immediate script command the following

    &hs.URLAction("https://graph-eu01-euwest1.api.smartthings.com/api/smartapps/installations/<AppID>/ST/off?access_token=<Access Token>", "GET", "", "")

    and then i create one that triggers when the device turns on and specify

    &hs.URLAction("https://graph-eu01-euwest1.api.smartthings.com/api/smartapps/installations/<AppID>/ST/on?access_token=<Access Token>", "GET", "", "")

    then you will see that the switch status is kept in sync between HS3 and Smartthings

    as stated though the solution is very clunky but i had it all up and running in one afternoon and it worked so well i didn't bother improving/expanding on it as i only used it during the migration to Homeseer.

    I have also ported it to Hubitat and i use these purely for my Zigbee contact sensors/motion sensors and switches. again clunky to set up but works very well.

    hope it helps you guys.

    Leave a comment:


  • simplextech
    replied
    Originally posted by logman View Post

    Ha! No, but similar sized towns. (I had a driver stranded at the Inwood Flying J with a mechanical breakdown a few years ago.) At least you guys have an interstate. Our little hick town is definitely off the beaten path. But it is home to Bocephus, Merle Kilgore (RIP) and part-time resident Kid Rock.... Party!!!
    Sounds like a nice quiet area unless the Kid is in town

    Leave a comment:


  • logman
    replied
    Originally posted by Simplex Technology View Post

    Do you live near me???
    Ha! No, but similar sized towns. (I had a driver stranded at the Inwood Flying J with a mechanical breakdown a few years ago.) At least you guys have an interstate. Our little hick town is definitely off the beaten path. But it is home to Bocephus, Merle Kilgore (RIP) and part-time resident Kid Rock.... Party!!!

    Leave a comment:

Working...
X