tazman

Well mine started working again on it's own but I don't want to restart it to see if everything is good. @Guy Lavoie you can try and see if it will retrieve your devices now.

It's not Emporia it is the people who backwards engineer the data retrieval process that released the code Bob used to make it available for us.

The best I can recommend is to be sure Alexa is not showing more than 1 item with your variable. Then as said give it a day or 2 and if it still not working try to get help from UDI to see if everything looks good in the portal, then you will have to move on to Amazon to try and get it working.

Then it definitely seems to be a problem between the portal and Amazon servers. If you have other devices working then maybe post a screen shot of your portal setup of the variable. Are you using a state variable? I never used an integer and don't know if they work.

You need to monitor the "device" in Alexa to see if that is triggering. The most common problem is with Alexa because it will see the trigger but the routine does not run in which case sometimes it starts working on it's own in a couple of days or people have contacted Amazon to get it resolved.

I just performed a restart of Vue in PG3 and I'm getting the same error and it will not connect. Either Emporia is having problems or they changed something and it will require a code change to get things working again. My Eisy is on 6.0.3_3 so I guess we will have to wait for @bpwwer to take a look.

Sorry I'm not a programmer but it looks like something is wrong with your location settings with Emporia maybe try going through the Emporia app and check/chang your location to see if it helps.

@Guy Lavoie have you installed the Dev Package in the admin console? That use to be a reason for failure before and worth a try.

My understanding is that "170001" is an information item not an error.

The values are pulled from some YoLink sensors and WeatherFlow node server where I send 2 push notifications with values I like to see in the morning before I reset the values with a program.

I use the temperature node to track/display a high and low value.

I would say this is expected, scenes are not triggered when you operate a device from the AC. You can test this with any scene you have only the device you operate from the AC responds. I think because ISY does not receive a command from the switch when it is not manually operated. @sjenkinsI like the new timer function thanks! I use the temperature nodes to record low and high temperature reached for the day. Is it possible to not have it use the "0" it sees on a reboot?

Your Homeassistant should still be there! I had to add the information in /etc/rc.con to start the vm again vm_dir="zfs:storage/vms" vm_enable="YES" vm_dir="zfs:storage/vms" vm_list="homeassistant" This might not be all the same information for you depending on how you did the install back then.

When I have a disconnect from the portal it is usually resolved by rebooting my eisy.

Is the OS 14.3 and IoX 6.0.0 released yet? UDI sent out the email but no announcement in the forum in the Current Version area and upgrading packages is not updating my system. My system is on OS 14.1-RELEASE-p6, UDX 3.9.0_9 and ISY 5.9.1_21