Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

bmercier

Employees
  • Joined

  • Last visited

Everything posted by bmercier

  1. I did not notice the announcement, but I can tell you that at the API level, there is nothing related to rooms or grouping. Grouping can be done, but it will result in multiple independent API calls, just like it is now. This means that every lights will turn on or off in sequence, and it can take a while if there are many. The only difference with V3 regarding groups is that in V2, this triggered alerts as the response to each API calls were taking too long. This is why it was not recommended. In V3, there is a concept of deferred responses which helps handle such use case. There will be no more errors. On the end-user side, the experience will be almost identical, in other words, it will still work. Benoit
  2. Other than using the new Smart Home V3 API, the main features are: 1 - Proactive state update; this will allow to see the state of your devices on the echo mobile app, in real-time. This requires the live update to be active. 2 - A/V Support 3 - Color bulb support (Aeotec, Fibaro) 4 - Thermostat an be turned on (to the previous heat/cool/auto mode) 5 - Slow devices like lock will no longer return an error, unless it's very long. 6 - Locks will tell you if the lock is Jammed, or if the battery is low. Benoit Sent from my iPad using Tapatalk
  3. It will support any A/V device that you can control from ISY. If you look in ISY Portal, Select tool, Amazon Echo, add A/V, you can see how the mapping works. For every Alexa A/V commands, you can map to a network resource, state var, or program. Benoit Sent from my iPad using Tapatalk
  4. The infrastructure is in place to receive subscriptions and dispatch this to push services, but other that proactive state update for smart home skills in V3, there is nothing else in the roadmap for now. Benoit
  5. Thanks for the update. I'm glad to see the problem is resolved!
  6. Exactly. This is developed and we are currently getting into the certification process. If you look carefully, you will also see a new "A/V" Button. This is also a V3 feature. This can give you a good idea of this upcoming feature. Benoit
  7. Ok I found it. I did not realize you were trying to add it for Google Home. I was testing it for Amazon Echo, where it worked. This is now fixed. Benoit
  8. James, Jimbo, After pulling my hair out, I finally resolved the mystery of C/F setting. We could not find it because there are none! The C/F setting is determined when you first enter the device in ISY Portal. Then, when you sync your devices (Unlink/Link), the C/F setting is passed along with the other device parameters. Based on that setting, GH will give you the setpoints or temperatures accordingly. Also, when you speak a setpoint, it has to be in that C/F setting. In other words, you have to talk in the same unit of measure as the thermostat. BUT, if you ever change your thermostat C/F setting, you will have to remove it from ISY Portal, add it again, then sync Google Home. For those who entered your device before it went live, you may have to do it again. I also found some bugs relater to the unit of measure that have been fixed. Please consider thermostat support in Google Home as beta code. Benoit.
  9. I'm not able to reproduce that problem. This node should appear in the lookup. I simulated with the content of that node, and I'm able to lookup. I simulated that spoken, and the UI reacts correctly too. Can you try this: Open your browser console (F12) Open the spoken window. Under the the network tab, you can see a few URLs, one of them will be: https://my.isy.io/api/nodes/lookup?uuid=<youruuid> Look at the response returned. Can you see your TiVo node in there? Based on my testing, it should Based on your screen shot, it should not. Also, please look at the browser console. Are you seeing any error? Thanks, Benoit
  10. Jimbo, Also please let me know what the addresses are for "family room thermostat", "master thermostat" and "outside thermostat". It's really odd! Benoit
  11. If it still works with with Google Assistant, it proves that the device still exists. The problem is the lookup. It seems that it would have worked in the past, but now the devices are no longer appearing in the lookup. It may be due to an ISY Portal update, or perhaps a firmware update. I can investigate further with a sample /rest/nodes with devices not appearing.
  12. Can you check the output of http://<isy>/rest/nodes, and see if your device is in the list? It has to have the same address. If so, and it still does not work, please PM me the output and I will investigate. Some devices are filtered from the lookup. Technically, this node should not. Benoit
  13. Hi Michael, I tried that, but it did not help. It works for when you ask for weather information. But it does not seem to apply to the Google Assistant. Benoit
  14. James, I think you uncovered a new issue. ISY Portal is supposed to detect the UOM of the thermostat, but I think that in your case, it did not do it correctly. Let me look into that. Benoit
  15. James, Google Home thinks you want to work in Celsius. It reports the temp to you in Celsius When you request 72, it us understood as Celsius, and well.. 72 celsius is out of range. Now, I don't know how to change the user setting to Fahrenheit. You are a programmer, here's more info; API Doc: https://developers.google.com/actions/smarthome/thermostat-schema You can see at the API level that all temps are normalized to Celsius. This is the request ISY Portal received: { inputs: [{ intent: 'action.devices.EXECUTE', payload: { commands: [{ devices: [{ customData: { address: '11 93 4F 1', category: 'thermostat', type: '5.3.146.0', uuid: '00:21:b9:02:07:ff' }, id: '5835f0c62dc9c25a649e2e44' }], execution: [{ command: 'action.devices.commands.ThermostatTemperatureSetpoint', params: { thermostatTemperatureSetpoint: 72 } }] }] } }], requestId: '6932436822782406037' } It is not converted from F to C. This is why I think there is a configuration issue. Just to be sure, anyone else got it working in Fahrenheit? Benoit
  16. Google Home and Amazon Echo have a few things in common, but they have their own set of capabilities. Google Home does not support locks yet. Alexa's query capabilities, at least in the V2 API, are limited to thermostat (setpoint, mode, temp), and locks. This is about to change with V3 though. > More importantly, it would be great if in a future version of the ISY skill, you could ask echo/home about variables This should already work with Google Home. This is coming with Amazon Echo V3 soon. If you are like me, you probably talk to your Google Home using "Alexa, ... " and vice-versa! Benoit
  17. James, Can you try again? It should work better now. With the help of the device address on the screen shot, I was able to locate the error in the logs and make a fix. Thanks, Benoit.
  18. @stusview, MWareman FYI, at the API level, there is only one thermostat query, and it returns both the thermostat temperature, the mode and setpoints (2 if in auto). Google Home decides what it will speak. By experimentation, saying "Ok Google, what is <device> set to" can return either the thermostat inside temp, or the mode + setpoint. It seems to alternate between the 2.
  19. I unfortunately do not know. At the API level, everything is always handled in Celsius. Google must translate that to Fahrenheit, or keep it in Celsius, based on user preferences. Anyone knows how to change that? I could not find it. Thanks Michael!
  20. Hello everyone, ISY Portal Google Home now supports thermostats. Here's what you can do with it. Query thermostat: what is <device> set to what is <device> inside temperature what is <device> humidity (If your thermostat supports it) Change mode: Set <device> mode to <off|heat|cool|auto|on> Turn off <device> Turn on <device> Change temperature: Set <device> to <temp> Increase <device> by <tempDelta> Multiple thermostat commands: What is the inside temperature Set heating to <temp> Set cooling to <temp> Set the thermostat modes to <mode> WARNING: - Please note that increase/decrease temperature do now work well IMHO. As an example, if the thermostat is set to cool, and you ask Google to "increase <device> temperature", it may very well set your thermostat to heating. - If you increase/decrease temperature without specifying a delta, it may increase/decrease the setpoint more than you would like. Benoit
  21. Hello everyone, We will have another maintenance this Sunday 10-01-2017 at 5:00 AM PDT which will last 1 hour. During this period, the proxy servers, subscription servers and the web servers will be restarted. Due to the restart of the proxy servers, your ISY will be offline for a few seconds. Changes - Google Home Thermostat support. - New code in preparation for Amazon Echo Smart Home V3 New Amazon Echo Smart Home V3 features are not yet available. We are about to get into the certification phase. With kind regards, Benoit
  22. db2ace2, I just though of another possible cause. Perhaps one of the spoken has a character Alexa does not like? Perhaps processing stops at the 302nd entry? I know it could be tedious, but could you check your spokens, see if you have any special characters in them? There should only be letters and spaces. I may need to enhance spoken validation. Benoit.
  23. db2ace2, I looked at the logs and was able to trace the device discoveries. Not too many users have > 300 devices. From ISY Portal's perspective, 497 devices are being returned to Amazon. It dropped to 496 yesterday in the evening, probably due to having removed the program from the list of spokens. Now, this may be a limitation at Amazon, or perhaps there is a bug somewhere in the format of the data sent. Would you be able to find a case where it is not reported. Is it a program? If so, do you have other programs working? Thanks, Benoit
  24. Open is a word used to invoke a custom skill, like in "Alexa, open izzy" It's probably the reason why we can't use it to "open" a device. Sent from my iPhone using Tapatalk
  25. This is not specific to programs. In the Smart Home skill V2, programs, state vars, scenes and regular devices are all exposed to Alexa as devices. Alexa has no way to know this is a program. Sent from my iPhone using Tapatalk

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.