andyf0

Yup! Picked up an Amazon Tap for $79. There have been a few times when I've wanted a mobile bluetooth speaker to play some music from my iPhone.

Well I liked the local notifications. Does anyone have the updated version and still have the sounds when entering and exiting their fences? They did leave the ON/OFF settings in there for notifications and mine are all ON, but nothing, no sounds and no notifications.

Locative had a new update in the Apple Store today. Now I no longer get any notifications that it did anything. I assume the cloud removal also removed the sound and visual notifications that I listened for to ensure it worked correctly. Anyone else?

Program1 will call it OK. By disabling it you prevent it from triggering when the light level changes by itself.

First, you can't use "Control" on a Z-Wave device unless you're running the latest alpha software. You need 2 programs. Program1: if status z sensor is switched on then Run (if) Program2 else set kitchen lights off Program2: if status z sensor < 50 lux then set kitchen lights on You should set Program2 to disabled. Either the Then or Else will be interrupted if anything in the "If" changes, if you have a Wait or Repeat statement in the body of the program.

The last portal update added support for Chunked Data. Previously, it didn't work at all.

Thanks, seems silly to me! How would you indicate an outside sensor/temperature?

The portal web access tool seems to take forever to display all the devices when using "Chunked Data". I can literally sit and twiddle my thumbs while waiting for the display to come up. Switching back to Default seems to make it much faster, maybe 1 second or so.

Benoit, When you ask Alexa for the temperature she prefixes it with "Inside it is ...............". Is that Alexa or part of the Smarthome skill?

Awesome. Thanks!

Ah! Got it! Thanks.

I created a device "iPhone" inside a location "Home". "iPhone" shows True and False as I would expect. This shows that "iPhone" is occupied in "Home" or not. But "Home" is also showing True and False. While this is cosmetic for me with one device, if I had 2 devices and one was True and the other was False, what would "Home" show? Shouldn't "Home" just be blank?

I setup network resources to do this because once in blue moon Locative will decide I've left the area when the phone is just sitting on the table. So I have programs to correct that and fix the mess caused by ISY thinking I've left the area when I'm sitting watching TV.

You can setup network resources to call the same URLs that Locative uses to force a Home and Away situation. That way you can debug your home and away code without leaving the house. This will set your device to TRUE. POST /api/location/ <insert key here> /report/in HTTP/1.1 Host: my.isy.io:443 User-Agent: Mozilla/4.0 Connection: Close Content-Type: application/x-www-form-urlencoded Content-Length: 0 Change the word "in" in the URL to "out" to set your device to FALSE. For you & your wife I would imagine you have one location called Home and two devices, my iPhone & Wife's iPhone. Then you can test both of them to be false for Away or one of them to be true for Home. I don't think you need two users on the portal.

Thanks Benoit. BTW, it works great with Locative.

Re: The Geofencing module update. Do we need to do anything if we are using this? Do we need to re-upload the node server? Please edit the title. Meant to be Portal Maint 4/14/17

1. Yes, you cannot use both at the same time. 2. With previous versions of MobiLinc you couldn't update a variable via the ISY Portal. This seems to be fixed with the latest version of MobiLinc. So Geofencing may work with MobiLinc and the ISY Portal now. I haven't tried it. I much prefer using Locative on IOS now for my Geofencing. I like the ability of Locative to have separate fences for leaving and arriving. 3. That's a good question. Someone else may know the answer.

The temperature setting does work. However, my thermostat is always in Auto mode with set points at 75H 82C. Whatever temperature I tell Alexa to set she always changes the heat setpoint, never the cool setpoint, but then I probably don't understand how it works in Auto. I'm sure what you wanted to know though was if she accepted normal numbers for input and she does appear to do so.

Here you go: FYI, Dashboard also reports current temp & set points with a zero on the end of the temperature. e.g. 75 is shown as 750. <nodeInfo> <node flag="128" nodeDefId="UZW0049"> <address>ZW038_1</address> <name>HU.(TS).HNWL_ZW</name> <family>4</family> <parent type="3">16841</parent> <type>4.8.6.0</type> <enabled>true</enabled> <deviceClass>1</deviceClass> <wattage>1000</wattage> <dcPeriod>60</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW038_1</pnode> <sgid>1</sgid> <devtype> <gen>4.8.6</gen> <mfg>57.17.1</mfg> <cat>140</cat> </devtype> <ELK_ID>E08</ELK_ID> <property id="ST" value="750" formatted="75.0°F" uom="" prec="1"/> <property id="CLIMD" value="3" formatted="Auto" uom=""/> <property id="CLISPC" value="820" formatted="82.0°F" uom="" prec="1"/> <property id="CLISPH" value="750" formatted="75.0°F" uom="" prec="1"/> </node> <properties> <property id="CLIFRS" value="0" formatted="Off" uom=""/> <property id="CLIFS" value="0" formatted="Auto" uom=""/> <property id="CLIFSO" value="0" formatted="No Override" uom=""/> <property id="CLIHCS" value="0" formatted="Idle" uom=""/> <property id="CLIMD" value="3" formatted="Auto" uom=""/> <property id="CLISPC" value="820" formatted="82.0°F" uom="" prec="1"/> <property id="CLISPH" value="750" formatted="75.0°F" uom="" prec="1"/> <property id="ST" value="750" formatted="75.0°F" uom="" prec="1"/> </properties> </nodeInfo>

In 5.0.9, whatever was wrong querying thermostats is now fixed. So I went to ask Alexa the temperature of my thermostat and she reported it was 770 degrees. There's a precision problem here that also messes up MobiLinc. I think it's a MobiLinc problem when using MobiLinc but maybe the Portal could be fixed to have Alexa report the correct temperature? I'm using Honeywell Z-Wave thermostats. Thanks

Just to finish off this thread. The Portal hasn't been updated yet to support "chuncked data". So if you've turned this on, then you need to put it back to "Default" to access parts of the Portal.

A couple of things are no longer working for me on the Portal with 5.0.9. 1. Web Access Tool - Clicking on Device, Scenes or Devices & Scenes does nothing. Programs, Variables etc work fine. Using the UD Ajax interface. 2. Connectivity/Amazon Echo - When trying to add a device or scene, when you click on the drop down menu no devices or scenes are listed in the drop down. Programs work fine. 3. This may not be 5.0.9 related but bringing up my Event Log from the Portal does not load the complete log, it is truncated as if the buffer allocated isn't big enough. Question: Now we have 5.0.9 is there such a thing as an Occupancy node server? Not sure how this is supposed to work but it appears I have to upload a node server. Does UDI have this? I am using Locative. Thanks

Yes, I am. Thanks for info. Sounds like lots of good stuff in 5.0.9. That explains a lot. Why Dashboard doesn't display the current temperature and maybe why MobiLinc thermostat display is messed up.

I am having trouble getting the temperature from my thermostat. The "What is the temperature of upstairs thermostat" return an invalid command for this device. It is a Z-Wave Honeywell thermostat.

Now that the portal has been updated it should be noted that you need to re-discover your devices in order to access the locks/thermostats words in the Smarthome Skill.