The device is the ecobee thermostat and it is working properly. I cannot access directly the device, it goes through their API.
Here is the Host URL https://api.ecobee.com/
I can access the device using their android phone app.
The bOS server is running on a Windows 7 machine, but even when I load it to a Windws 10 machine I am getting the same errors for the the HTTP device.
As I mentioned before the http device stopped after few months working without any issues.
Basic command gets executed when it is launched from google chome browser or internet explorer from the same windows machine where the bOS is installed.
I have tried adding another http device and add only one command and still doesn't work with this API.
Could you please check as well the coding for ServicePointManager.SecurityProtocol = SecurityProtocolType.xxxx and see if it has to be redefined in bOS.
Thanks for your feedback. I just uninstalled/installed the latest version 4.4.2. the server -bOS Service Monitor and also the bOS Configurator. I tried to exclude and include again the water sensor and I am having the same issue, the device is not properly integrated and cannot associate to the Group 1. I can share the project configuration if needed for further investigation. Would you be able please to share the screen shots with the device included in the network? I have the server installed on a Windows 7 64-bit, don't know if this makes a difference. Regarding the CO detector, if the issue gets solved with the water sensor I think the other one is the same so don't bother ordering it.
Hi guys, do you have any updates on this?
Yes, these are the sensors.
There is no traffic seen under debug tab when trying to wake up the device.
I think the issue is related on how the device is integrated into bOS.
When I include the device in bOS , the only value which updates is the battery even though the Controller 1 cannot be set to Association Group 1. The z-wave USB dongle used is the Z-stick Gen5. As I mentioned before, I have tried several times to restore the sensor to the factory default settings, include, exclude, delete then click discovery, soft reset the controller, wake up the device, run Refresh Configuration from the Functions tab in order to set Controller 1 to Association Group 1.
1) After including the water sensor using bOS:
that's how the configuration looks when opening the z-wave network using the zVirtualScene(used for comparison).
2) If I include first the device in zVirtualScene, here are the class commands and values available:
The value changes when alarm is triggered:
Opening now the z-wave network in bOS after including the device using zVirtualScene, there are no class commands available:
BUT, using the debug tab the sensor value gets detected, it doesn't recognize the node:
Also, waking-up the device:
If this gets fixed into bOS then I guess it will solve the other ticket that I open regarding the z-wave ZCOMBO (CO & smoke detector) https://support.comfortclick.com/communities/4/topics/1493-z-wave-alarm-command-class-not-available
Please find attached the debug logs. I tried excluding/including other z-wave devices(switches) and they work fine.
2018_04_18_Water Sensor_Exclusion_Log Debug.txt
2018_04_18_Water Sensor_Inclusion_Log Debug_1.txt
2018_04_18_Water Sensor_Inclusion_Log Debug_2.txt
Yes, I tried also waking up the device.
If you install bOS Server BETA you will get the latest ComfortClick.Zwave.dll
The integration of the ZCOMBO from First Alert hasn't been solved yet. Are you experiencing issues with the same device?
Initially I excluded the device, then update the server version to 4.4.2 and include the device.
Please send the new .dll file along with the instructions to firstname.lastname@example.org
Could you please advise if the device was supposed to be supported in server revision 4.4.2? I tried it but still doesn't work with the device.
Customer support service by UserEcho