bmercier

What is the device in question? Does it come from a Nodeserver? ISY Portal identifies a device using the hint of the device (the device category). If it is incorrectly set by the Nodeserver, it may incorrectly be identified as a thermostat. Those hints are considered thermostats: 1.12.x.x (Ecobee and other Nodeserver thermostats) 4.8.x.x (ZWave thermostats) 5.x.x.x (Insteon thermostat) Benoit

For the purpose of clarification, HAD is still available, both on ISY Portal, in the firmware, and as customization interface, and there is no plan to retire it. However, no efforts are planned to enhance it either. Benoit

Whenever possible, put these on the ISY side. If you do this on the Alexa side, one drawback is that to turn off let's say 30 lights, there well be 30 requests sent and queued for execution, so your lights won't turn on simultaneously. The second drawback is that if for some reason you have to unlink and restart clean, you will lose your Alexa configuration. The only time I would do that on the Alexa side is if you have devices coming from different skills that you want to control together as a group.

A contact sensor is not the same thing as a door lock. All a contact sensor allows you to do is trigger a routine. You can query the contact sensor state in the Alexa app, but you can’t query it vocally. Sent from my iPhone using Tapatalk

Thanks for the suggestion, instructions updated. Benoit

Looks like there is a low level problem. Insteon or ZWave communication problem or perhaps a problem with links. Sent from my iPhone using Tapatalk

There is something else at play. First make sure that you can control devices using web access successfully. Benoit

Communication pathway: 1. ISY opens a permanent connection with ISY Portal at boot time, and retries to connect when communication is interrupted. 2. ISY Portal sends commands to ISY through that connection, when required. A few security checks are done, such as the communication must have been previously approved in the admin console. Alexa command confirmation: The command is sent to the ISY in the same way as when using ISY Portal web access or the local UI. In other words, yes, there is a round trip to the ISY, and even to the actual device. Benoit

Recommended troubleshooting sequence: 1. Use the admin console or web interface from ISY to turn on/off devices. 2. Use the ISY Portal web interface to turn on/off these same devices. 3. Then try these same devices through Alexa. If it's a PLM problem, it should fail at step one. Step 2 helps you determine if ISY is communicating with Portal correctly. If it fails at step 3 only, then you know it's an Alexa related problem. If so, this can help you: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3

I made a change to ISY Portal. Nodes with a hint of 0.0.x.x should now appear as a dimmable light. Can you please test it? Thanks, Benoit

Good catch, this is now fixed.

Try to delete the routine and create a new routine using the same ‘virtual’ motion sensor. Benoit Sent from my iPhone using Tapatalk

Most likely, the node now has a new type that is no longer recognized. Please post the output of /rest/nodes Benoit Sent from my iPhone using Tapatalk

In your ISY Portal account, just remove the ISY by pressing X. Please note that if you also sell the new owner an Echo or Google home, that will break the connection with the ISY. It will have to be reconfigured in the new owner's ISY Portal account. Benoit

I believe the problem is the DNS that was not working. The ISY tries to connect to ISY Portal, but if DNS is not working or misconfigured, it won’t connect. Benoit Sent from my iPhone using Tapatalk

This is because the device is not recognized as a thermostat. By the address, I notice that it’s a Nodeserver node. I need to know the device type. You can get it by looking at http://your isy/rest/nodes/n003_ven1 Sent from my iPhone using Tapatalk

The list of devices is loaded from ISY when you open the Amazon Echo dialog (Select Tools | Connectivity | Amazon echo) Therefore, if the dialog is opened, then you add devices to your ISY, your devices won't be shown in the list. When this happens, just close the Amazon echo dialog and reopen it. The list of available devices will be refreshed. There is no need to log off. Doing a search does not help either. I suspect you tried a search, then closed and reopened the dialog, which refreshed the list of devices from ISY. Benoit

What list of devices? Are you referring to the list of devices that shows when trying to add a spoken? (Select Tools | Connectivity | Amaxon Echo | Add device) Are you referring to the list of devices in ISY Web Access? (Select Tools | ISY Web Access) Or something else? Benoit

I'm assuming you are talking about a search in the Amazon echo spokens. Adding devices to an ISY is not enough. You need to add the device in the echo spokens.

This is in response to your private mail, I'm posting here for everyone interested in the fix. The best practice is to always pass the uom (unit of measure) whenever setting the heat or cool setpoint. Celsius is '4', Fahrenheit is '17'. This is true for ZWave thermostats, not insteon. So, let's say we want to set the heat setpoint to 23 Celsius instead of doing this: /rest/nodes/<address>/cmd/CLISPH/23 We need to do this: /rest/nodes/<address>/cmd/CLISPH/23/4 Benoit

3. You need just one key Sent from my iPhone using Tapatalk

1. Just exit the Alexa dialog and come back. 2. Leave it empty Sent from my iPhone using Tapatalk

Do you have an account on my.isy.io? This is where you can configure IFTTT, not the admin console.

This is not normal. Please open a ticket referencing this thread and your uuid, I will check the logs. A work around would be to sync the devices vocally. Ok google, sync my devices. Sent from my iPhone using Tapatalk

Yes it's the only option. The only thing you may lose is the room assignment. If you made those in ISY Portal, it will be retained, but if you assigned rooms using the mobile app, it will have to be reassigned. Benoit