Announcement

Collapse
No announcement yet.

HSZigbee Now In Beta

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

  • fuzzysb
    replied
    Any news on the EU version. According to the API it requires 0 changes other than the URL. So as you already have the selection this should be easy to implement.

    I just don't this losing focus as it's really important to my setup

    Sent from my SM-G950F using Tapatalk

    Leave a comment:


  • Chewbucka
    replied
    I've sent the database file to you and also the password via PM. The model of the lights that I have is "OSRAM Lightify Gardenspot RGB". Here are the versions from my gateway.
    Attached Files

    Leave a comment:


  • Sgt. Shultz
    replied
    What is the model of the devices?

    Better yet, can I get a copy of your database?

    That way I can see the devices as you have them.

    Leave a comment:


  • Chewbucka
    replied
    Two lightify gardenspots.

    Leave a comment:


  • Sgt. Shultz
    replied
    What do you have for devices?

    Leave a comment:


  • Chewbucka
    replied
    Originally posted by gaf@bluerivernet.com View Post
    After deleting original plugin and reinstalling new, I get this when trying to create a device.

    May-03 5:55:09 PM ZigBee Error: There was an exception in the 'Send' function: Invalid JSON primitive: The.
    May-03 5:53:27 PM Starting Plug-In Plugin HSZigBee started successfully in 16 milliseconds

    clues?
    GAF
    I'm seeing the same error. I upgraded the 3.0.0.6 plugin to 3.0.1.0, deleted all the old devices and then retrieved the new tokens. When I tried to create the devices, I received the error "Device creation failed, please check the log for more information." I then uninstalled the plugin and reinstalled, but still the same error. Here is what was in the logs.


    Code:
    May-03 21:10:17	 	ZigBee Error:	There was an exception in the 'Send' function: Invalid JSON primitive: The.
    May-03 21:09:51	 	ZigBee Error:	There was an exception in the 'Send' function: Invalid JSON primitive: The.
    May-03 21:09:21	 	Starting Plug-In	Plugin HSZigBee started successfully in 19 milliseconds
    May-03 21:09:21	 	Starting Plug-In	Initializing plugin HSZigBee ...
    May-03 21:09:20	 	Info	Plugin HSZigBee has connected. IP:127.0.0.1:52518
    May-03 21:09:20	 	Plug-In	Finished initializing plug-in HSZigBee
    May-03 21:09:09	 	Updater	Install/Update of package HomeSeer ZigBee was successful.
    May-03 21:09:09	 	Updater	Copying file: D:\Program Files (x86)\HomeSeer HS3\HSPI_ZIGBEE.exe
    May-03 21:09:09	 	Updater	Installing package HomeSeer ZigBee
    May-03 21:09:09	 	Updater	Update HSPI_ZIGBEE.exe downloaded successfully
    May-03 21:09:09	 	Updater	Downloading update: HomeSeer ZigBee

    Leave a comment:


  • Jobee
    replied
    I updated

    I had to delete the old devices

    After I did the token and the refresh token, I had to delete all the old devices and have it create new ones.

    Once complete, I had to update all my events to replace the deleted devices with the new devices.

    All control seems to be working.

    I did find the following in the log:

    May-03 19:48:43 ZigBee Error: Command returned an error: The remote server returned an error: (400) Bad Request.
    May-03 19:48:41 ZigBee Error: Command returned an error: The remote server returned an error: (400) Bad Request.
    May-03 19:48:37 ZigBee Error: Command returned an error: The remote server returned an error: (400) Bad Request.
    May-03 19:48:35 ZigBee Error: Command returned an error: The remote server returned an error: (400) Bad Request.
    May-03 19:46:31 ZigBee Error: Command returned an error: The remote server returned an error: (400) Bad Request.
    May-03 19:46:29 ZigBee Error: Command returned an error: The remote server returned an error: (400) Bad Request.
    May-03 19:46:21 ZigBee Error: Command returned an error: The remote server returned an error: (400) Bad Request.
    May-03 19:30:33 ZigBee Error: Command returned an error: The remote server returned an error: (403) Forbidden.
    May-03 19:30:18 ZigBee Error: Command returned an error: The remote server returned an error: (403) Forbidden.
    May-03 19:30:17 ZigBee Error: Command returned an error: The remote server returned an error: (403) Forbidden.
    May-03 19:30:16 ZigBee Error: Command returned an error: The remote server returned an error: (403) Forbidden.
    May-03 19:30:15 ZigBee Error: Command returned an error: The remote server returned an error: (403) Forbidden.

    But there is no ZigBee logging, only error logging and it seems to be tied to when I activated the plugin but the token was not corrected yet.

    Will keep an eye out on the log and more events.

    Leave a comment:


  • gaf@bluerivernet.com
    replied
    errors creating device

    After deleting original plugin and reinstalling new, I get this when trying to create a device.

    May-03 5:55:09 PM ZigBee Error: There was an exception in the 'Send' function: Invalid JSON primitive: The.
    May-03 5:53:27 PM Starting Plug-In Plugin HSZigBee started successfully in 16 milliseconds

    clues?
    GAF

    Leave a comment:


  • cowinger
    replied
    I am getting these 2 errors in the log. The plug does not show on when manually turned on no matter what polling time you set.

    JowiHue Unknown model sensor found Plug model Plug 01 type ZHAPower. Default values will be used
    Warning: sensor device Plug was removed, cleaning related devices

    Also these are still happening for the plug.
    1. changing device on/off in UI does control device but device on/off status does not change in UI
    2. selecting 'on' in UI does not change time but selecting 'off' does

    These things are still there for the osram color bulb.
    1. selecting 'on' from the UI turns on bulb to different percent values and then after 30 sec or so it goes to on. I seen 100, 8, 93, etc.
    Last edited by cowinger; May 3, 2018, 05:53 PM.

    Leave a comment:


  • rjh
    replied
    We posted version 3.0.1.0 to the plugins page Beta section. Reported issues fixed. This plugin supports on/off/dim, and color bulbs.

    We think everything should be working, please post any issue you find.

    Note that only US systems can connect at this time, EU will be enabled next.
    Last edited by rjh; May 3, 2018, 04:01 PM.

    Leave a comment:


  • jnarva@cobaltsphere.com
    replied
    Same problem

    I have exact same issue, multiple instances of the exact same device being created. I have a dozen Zigbee devices in operations and after installing alpha version ended up with about 30 devices.

    Leave a comment:


  • cowinger
    replied
    I am the same as slbuck.

    1. turning on/off device from app does not change device status in the UI
    2. changing device on/off in UI does control device but device on/off status does not change in UI
    3. selecting 'on' in UI does not change time but selecting 'off' does

    Possible additions:
    1. Change polling time. 60 seconds is ridiculous
    2. Add device for Hub (so we know it is connected or not)
    3. Add device for Hub Update Available

    EDIT:
    I wanted to add in my UI devices as well. As you can see there are duplicates just as slbuck reported. Also the ones with the 'red delete' cannot be deleted.
    Attached Files
    Last edited by cowinger; May 3, 2018, 11:14 AM.

    Leave a comment:


  • fuzzysb
    replied
    I have larger problems than the cosmetic etc... I'm based in the UK and I cannot authenticate to get my refresh key etc... I am presuming that is because they now have different endpoints for the different regions now. The plugin will need to support the different regions and not just North America. Maybe something as simple as a drop-down in the plugin config with the the region selectable?

    Sent from my SM-G950F using Tapatalk

    Leave a comment:


  • Chewbucka
    replied
    Also, I noticed that if an external schedule turns on/off the lights, once the device is polled, the last change time doesn't update when turning off or on.

    If I manually turn on the device, the last change time never updates. If I manually turn off the device, the last change time does update. If I set any dim value, the last change time does update. It seems that when you set the device to On, the last change time doesn't update.

    Leave a comment:


  • Chewbucka
    replied
    Device creation

    Rich,

    After shutting down HS3, replacing the HSPI_HSZigbee.exe, and starting back up, I went to the plugin config page to and retrieved my auth and refresh tokens and entered them in. I then created the devices and it completed successfully.

    I only have 2 gardenspot lights associated with my account and a single group that contains both of the lights. Below is what was created. I can control the lights, but something is weird with the grouping and their are duplicate devices. Not sure how the new API works, but I would have thought that there would have been one device group for each light containing two devices: on/off/dim and color. And then another device group containing a on/off/dim and color device in order to control the lightify group.

    Also, saw this error in the logs and didn't know if it just meant that I tried turning the lights off and on too quickly, but figured I'd include it.

    May-02 22:32:38 ZigBee Error: Command returned an error: The remote server returned an error: (403) Forbidden.
    Attached Files

    Leave a comment:

Working...
X