It does not.
(20 chars)
It does not.
(20 chars)
@bs87 haha, this is so crazy. I edited my device type with the range limits and tested and it worked in android and I was excited and went to come post here but you guys already figured that out⦠LOL! Iām late to the party again!
So, I donāt see the need for rounding⦠Why bother? If people want to do a tenth of a degree why not just let them?
I am not able to add this sensor.
I get the following error:
An unexpected error occured.
@Robert_Vandervoort so were you able to put the decimal in the range or just an integer? I tried the decimal 10.0 and it was still crashing the app.
i think the rounding idea was for taking 9.9*10=99.0 to 99 but i doubt the sensor is that picky that it wont just accept a 99.0. or maybe smartthings will just send a 99 for a 99.0 decimal anyway? would have to test more to be sure.
IOS doesnāt let me add decimals. Iāll check it out tomorrow.
In the meantime I just put out 2.0 code moving over to the ānew schoolā multi-attribute tile interface. I picked temp and humidity as that is what I personally care to see while browsing my rooms. I only use motion to trigger events, but the other tiles are still kept of course in the details view.
My impresions:
Colors for light tile are bit awkward. At high lux value its pretty much unreadable.
UV is always showing 0. Is that known isue?
Canāt see humidity in app. Itās showing fine on smarttiles
Other than that. Really nice job.
Iām in UK (nexus6)
Liking the large icon addition! If you want to allow decimals then you need to change line 168 to ādecimalā. Also, I see that you have put the line 171 to range: ā-11ā¦11ā. Is that intentional as on my iPhone this lets me enter 11 and that will get scaled up to 110 to send to the sensor. The spec says only -100ā¦100 as valid entries.
The point of the rounding is to work correctly if a user enters too many decimal points, e.g 4.59 rather than 4.6. Without the round(), you will be sending 45.9 to the sensor which gets truncated to 45 but with the round the sensor gets 46.
Interesting that the android bug is with the implementation of the range parameter. Seems that we need to stick with range: ā-10ā¦10ā to maintain compatibility across both platforms. Luckily this is benign bug and still allows entering decimal offsets.
Just curious but does any range statement with decimals consistently crash on Android, e.g. range: ā5.5ā¦9.9ā ? If so this should be a straight forward ticket for tech support to drill into. A bit poor if you cant set decimal ranges on Android.
anyone having any issues with unexpected outages? One of my sensors stopped sending data to the network last night. I had my wife check for me since Iām at work right now and she said the blue LED flashed when she approached so the device has power. It is, however, listed as INACTIVE in the IDE. Is this jsut a remove and rejoin fix? Pull the batteries? Any recommendations I can try when I get home?
So this is interestingā¦on Android, humidity is missing. Itās there on iOS. Thinking this is maybe app, not device type, but curious.
@Lind_Lau_el_Loren and @wipeout944
For the UV, it takes some powerful UV to trigger it, mine is under an awning so it never changes but if you point it towards the sun you can get a reading. Not sure if this is by design or a flaw but I really have no way to verify.
The light, we need to get around to changing the font color as we change the background color. Itās on my list to improve but lower priority than some of the other issues weāve been working through.
The humidity and funky temperature font size seems to be an android issue. It seems that SmartThings doesnāt do the same QA (if any TBH) on the android app.
v1.9 of my device type seems to work a little better on android right now but @Robert_Vandervoort seems to work better on iPhone. Try them both and see which one works better for you.
Hello Again bs87,
I still have an issue to connect my Multisensor⦠I did exactly all what you said. Do you have any idea.
You are all talking about the ZW100-A model but mine is ZW100-C ⦠Could the problem come from that?
Thank you again are sorry for my dumb attitudeā¦
AFAIK the C model is just the European one and the A is the US one. I donāt think they are really different but canāt say for certain. I think a couple people have gotten bad sensors and exchanged them but it could be that you need to exclude the device due to a failed pairing. I havenāt gone through that process but itās somewhere in the IDE. Maybe someone with more experience on that can weigh in? or do a search through the forum for how to exclude a device, I am sure someone has posted some instructions.
I talked with support a while back. At this point the foreground color automatically changes based on the background color. The reason I chose to change the background color is because a lux value is irrelevant to me. I like to be able to glance at it and know is it dark, dim, light, bright. Also j combined humidity into the multi attribute tile so itās now in the bottom left corner in the 2.0 code. Relative humidity is normally not all that important to me since my ac controls it but j do want to see it without having to dig, more so than lux or uv. Yes UV is incredibly insensitive. I had to put the sensor face up at the sun outdoors here in Texas to register a 7. The max is 11. This is because they sort of hide the sensor. Plastic also filers UV so until they use a glass lens this will be a problem. On the note about tamper, there is not to my knowledge real implementation of it. I had initially implemented it as a touch sensor. Some do it as an acceleration sensor. The truth is it can be implemented however you want. In the native code for the zwave device it is part of the alarm function that would be in the same class as a motion detector for a burglar alarm. Ultraviolet didnāt even HAVE a capability for it a few months ago. Crazy how fast stuff changes here which is a good thing really.
Hmm hadnāt actually looked, but there isnāt a font change attribute. It is always white, somebody didnāt really think that through.
I really think they need a [better] UX team that reviews everything for usability and bugs. Maybe they could reach out to some of their most active\prominent external developers and show them mock ups and get feedback before implementing.
Yea hopefully it keeps getting better and better.
Im using the Aeon Multisensor 6 - RV 1.5 device type under iOS 9.01 on iphone 6+. Also tried on iOS 9.1 on iphone6. I had 2 sensors and both exhibit the same behavior. All of the fields seem to be populating correctly however the config button does not do anything. Is this normal? I can change the settings via the developer web interface, just not the config.
Comfig doesnāt ādoā anything visually. From a previous @Robert_Vandervoort when I asked about the same thingā¦
āWhen you hit config it wonāt appear to do anything but it is blindly sending the config commands to th device in the hopes it is listening. You can go to the login for the ide and see it work in the live logging view. Youāll see a successful response there too in the form of the sensor returning a report of various metrics and the battery level after a fe secondsā
@wipeout944 @jimrobertsemail Correct. In the newest code though 1.5 and actually 2.0 is out, as part of my configuration action I pull the configuration values set on the sensor after setting them so you can verify they took. Iāve set the delay between commands out a bit for cases where the signal might not be amazing so the config should take better. Really, the best results will be had if you plug the sensor in via USB and just hit config. That way you donāt have to tap the action button to wake up the sensor. When you hit the config tile what happens is any preferences you set prior like temp offset or clear after motion timeouts, pir sensitivity and the lot, along with some basic settings that need to be present for it to work the way I intended, get sent.
Iām going to write a proper instruction manual quite soon. Itās taken a bit to iron out exactly the best way to do everything but I think itās almost there. One thing Iāve seen common is that folks just change the device type and donāt do the config which means reports dont get sent but every hour and UV and tamper donāt work / clear. If I were to put it in bullet points it would go like this.
Hope this helps.
Iāve also put up a new device type today for Aeonās Smart Switch 6 which, I feel, is a pretty sweet little device. Compact, handles 15 amps, has over current protection, reports watts, volts, amps, kwh, kVAh, has adjustable night light colors and a side USB charge portā¦
Cheers
Robert
Nice, want to pick up one of those switches soon anyway!
@Robert_Vandervoort Really great work! Was wondering if you could help me in getting the motion to be the main tile. In the list view it would be ideal to see the motion status over the temp. Tried to give it a go myself but Iām no good at the styling. Thanks!
look for something like (line 159):
main([
"main"
])
change āmainā to āmotionā, the second main, not the first main
save, publish, done