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. Hi Michael, The mapping of spoken to devices is now managed on portal. There is an "Amazon Echo" tool that has been added on the ISY page. The skill can only use devices defined there. You can delete those that you don't need. Benoit.
  2. Hello Ronbo, The refresh button only refreshes the table with content hosted on portal. This does not do the same as "refresh device" did. It is now a somewhat a manual process where you decide which devices you want to expose to the skill (and eventually connected home), and of course the corresponding spoken. Currently, programs work the same as before. They work with the name that you have on your ISY. However, you can expect this to change. You will soon see a button added there to allow to define a spoken for programs. Benoit.
  3. Actually, testing shows that custom slots work well when the skill is not too large. It behaves just like a literal, with the added benefit that it helps recognition if what is spoken is close to one of the samples. The problem we are facing are these: 1 - As we add more utterances, alexa starts having difficulty passing values to the custom slot. With only the turnOn turnOff utterances, it works very well. Just about any word spoken and correctly understood as seen on the echo app are passed in the custom slot to the skill. However, if we gradually add more unrelated utterances to the skill, alexa start dropping the last word like; light, lights, lamp, etc.. As we add even more, it stops passing simple words to the skill like "bard", "master, etc... Except for the words in the samples. I made sure that this is not due to words like "light" in the added utterances. I thoroughly tested with different blocks of utterances. 2 - As we add more utterances, we can save the skill (at least it appears as such), but we reach a point where underneath, something looks corrupted. Let's say I add many utterances, I save, everything looks good. It is there. But then, if we delete some of those utterances and save... they still work. I took such a skill, trimmed it to the point where I had only 1 utterance with 1 intent, and the skill still worked as if was never modified. So something is not updated underneath, but that only happens if the skill reach a certain size. Both problems, which may very well be related, have been reported to Amazon. The only possible short-term fix would be to add samples to the device list. That I know works. Benoit.
  4. Hello Xathros, If you are referring to the the Amazon account link in "My profile" - it's is not required to use the Alexa skill. Alexa skill account linking is done when you enable the skill. It prompts you for a portal account, then links the accouts. The reason for the Amazon account link in "My Profile" is for the Connected Home only. The will be useful only when the connected home ISY adapter will become available. I know it can be confusing. Connected home (lighting API) and Alexa skill uses 2 totally different ways to link accounts. Benoit.
  5. You need to go to the admin console, in configuration/portals. There, you need to click a button to give approval. The reason for this is that anyone who knows your uuid could enter it in it's portal account. But authorization has to be given at the admin console before it can actually be used. Benoit.
  6. HAD is now bundled with Portal. When you select "ISY web access", you will get to UDAjax. From there, go to settings change the default UI to HAD. When in HAD, you can also switch back to UDAjax, just like on the firmware version. Benoit.
  7. bmercier replied to bmercier's topic in Amazon Echo
    Absolutely. Good idea for the leds. Benoit.
  8. bmercier replied to bmercier's topic in Amazon Echo
    I was thinking of up to sunday inclusively. However, I'm currently testing, and I'm running into another problem which might change these plans. Testing shows that if I fill in 2 slots, predevice+device or device+postdevice, it works well. But if I only fill one like "kitchen", it is not recognized I need to get back to Amazon with this... Benoit.
  9. We are progressing well. I'm currently working on enhancing the device list before we resubmit to Amazon. Please see this thread to review the device list and provide feedback: http://forum.universal-devices.com/topic/17632-device-list/?p=158852 I figured it would be best to have a separate thread focused on enhancing this list. Benoit.
  10. bmercier posted a topic in Amazon Echo
    We are progressing well. The next iteration of the skill should bring a significant improvement in speech recognition. Given that changes to the skill configuration such as the device list requires a recertification, I'm trying to refine this list before resubmitting to Amazon. This time, the device list will consist of 3 components. They are what I call the predevice, device and postdevice. Any combination of those 3 components will be a valid device name. Each components are not mandatory. Any of those components, filled or not, is a valid device name, as long as it's in the right sequence (left bathroom is valid, bathroom left is not). Some valid examples: upper hallway lights left bedroom lamp kitchen sink light front door master So I'm looking for your feedback to enhance these lists. We can't increase them too much, so I'm looking for only real practical items that would be useful to you and subject to be common. predevice upper lower front side rear right left main master first second third postdevice light lights lamp lamps track light track lights neon neons spot spots flood floods fan fanlight accent device door garage door small garage door porch entry yard garage front exterior exterior decor tree landscape garage master kitchen kitchen window kitchen sink kitchen island kitchen desk kitchen area kitchen table kitchenette bar pantry living living room parlour dining dining room computer computer room media media room game room rec room nook guest room office library music room attic box room locker room cinema cinema hall hallway hallway landing basement basement bedroom cellar utility utility room toilet bathroom washroom floor bathroom basement bathroom basement washroom basement toilet deck awning swimming swimming pool pool lanai upstairs desk desk room island island sink downstairs great room family room entrance yard barn patio driveway walkway stairs steps holiday christmas chrismas tree xmas xmas tree breezeway entry foyer laundry laundry room t. v. theater receiver stereo wall sconce wall sconce fireplace den study study room entertainment entertainment room breakfast table breakfast area sprinkler heater chime door chime chime mode air conditioner thermostat floor zone one zone two zone three zone four zone five zone six zone seven zone eight bedroom guest's room guest's bedroom boy's bedroom girls's bedroom kid's bedroom children's bedroom sally's bedroom andrea's bedroom jess's room mary's room erin's room greg's bedroom katie's bedroom mary's bedroom patricia's bedroom linda's bedroom barbara's bedroom elizabeth's bedroom jennifer's bedroom maria's bedroom james's bedroom john's bedroom robert's bedroom michael's bedroom william's bedroom david's bedroom richard's bedroom charles's bedroom joseph's bedroom For now, I left all those named bedrooms as is, hoping that it helps Alexa recognizing this pattern. That was an Amazon recommendation during the first try for certification. I had tried to put 3000 names in there, but this was simply just too big. Please post your suggestions in this thread. Benoit. Edit: Hold on, I'm running into problems with 3 slots. Theoritically that should work, but testing shows that in this scenario, it is necessary to speak at least 2 words. Example: "kitchen lights" would work (2 words in 2 slots) "first kitchen" would work (2 words in 2 slots) "kitchen" only is not recognized. Interestingly, "living room" and other 2-word slots work well. Long story short, I may have to revert to only 2 slots, a device and postdevice. That worked well. I'm in contact with Amazon on this and I will keep you posted.
  11. Yes. I have incorporated all the suggestions from the forum. In the case of the game room, it's only "game room" though, not "gameroom". Benoit.
  12. From all of those variations, those would work well in the next version: Computer Light Computer Room Light Computer Fan Computer Room Fan Computer Room In other words, not motor, not ceiling. Would you consider it sufficient? Benoit.
  13. Hello PurdueGuy, HAD will be added to portal, it's in the roadmap. It is actually planned to be completed before Christmas. It will work just like on the firmware version, with a setting in UDAjax to swith to HAD, and a setting in HAD to switch back to UDAjax. Thanks, Benoit.
  14. Connected home will provide better speech recognition accuracy, and shorter sentences. However, it will not allow to control lock, thermostats, or programs. This is the reason why we decided to do both a connected home adapter, and a skill. Benoit.
  15. Scenes are supported. However, if you have a device and a scene using the same name... only one of the two will work. When doing a refresh devices, it will tell you if it found duplicate names. Benoit.
  16. Thermostat setting will be solved in the next version. Note, if you want to use bathroom 1 and bathroom 2, you have to write it "bathroom one" and "bathroom two". You can't use numeric characters. All the feedback so far is invaluable. Thanks, Benoit.
  17. In addition to Michel's suggestion, if you have not changed anything on your ISY, you may want to try a reboot. Alternatively, you could try the following. Telnet to your ISY Command SPU will allow you to change your portal URL. Change it to something else, then bring it back to https://my.isy.io/dispatcher Benoit.
  18. Actually, a scene can be dimmed. /rest/nodes/<device>/cmd/BRT and DIM will work on a scene. However, we can't set a scene to an absolute level. /rest/nodes/<device>/cmd/DON/<level> will turn on devices in the scene to their on level, not the level specified in the url. Interestingly, a zwave device in a scene will respond correctly to an absolute level! Thanks for your kind comments, Benoit.
  19. Unfortunately that would not work. Alexa will never come up with a comma or a dot in it's speech recognition.
  20. The main benefit of the skill over the connected home is extra functionnalities like locks and thermostats, as you pointed out. But I don't think that also handling device turn on, turn off, brighten and dim hurts lock or thermostat functionnality. The skill can report the status of a device (no matter what the type is), and the status of a program. Scenes unfortunately don't have a status. For a device: Alexa, ask izzy to get the status of {device} For a program: Alexa, ask izzy to get the status of program {program} There are many variations of those. > In text representing speech, the comma signifies a short pause and the period a long one. Did you notice a place where a change would be appropriate? Thanks, Benoit.
  21. Your ISY with uuid ending in :eb is indeed not online on portal. Benoit.
  22. It will, and recognition will be just as good. Benoit.
  23. Note taken for next release.
  24. Can you post exactly what she heard? Copy paste please. Thanks, Benoit.

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.