Ultra1Wire3 (HS3)

[Jon798]

Hello,
I've been using the trial version, but the trial has now expired and I would like to buy the plugin but there doesn't seem to be a way to do it...

Perhaps you could extend the trial for a short while and let HST add your plugins to their purchasing system?

While I'm writing, it would be great if you could look into the possibilities of having different refresh rates for different devices and looking at the light level options for the MS-TL devices (I routinely see light levels of 130% which doesn't seem quite right)...

Thanks,

Jon.

[vasrc]

+1
Would like to purchase as well.

Z

[Guest]

+1
Would like to purchase as well.

Z

+1 Ultra1Wire3 is not in the HS store and HS3 reports 30 trial has expired.

[Ultrajones]

Ultra1Wire3 HSPI for HomeSeer3 was just submitted to the HomeSeer store.

Regards,
Ultrajones

[Jon798]

No sign as yet...

I have some DS2348 devices which are used as light sensors. I can define them as a light level device on the device's ultra1wire3 tab and click save, but they stay as humidity devices.

If I change the graphics or text, then they get reset when I restart HS3.

Could you have a look at this when you get chance? Do you know when that might be?

Thanks,

Jon.

[Jon798]

Hi UltraJones,

Do you have any plans to continue development of the Ultra1Wire3 plugin?

The humidity/light level switch not working for some of my devices is a little irritating (especially now that the plugin rebuilds the value/status text and graphics each time HS is restarted) and I have asked a few times about the issue and I've also asked about what level of support I should expect but haven't received an answer.

I'd prefer to be able to buy your plugin as it's way more polished than anything I could do, but the lack of response to my queries/issues puts me off.

I understand you've probably been really busy on other things, but it would be good to know if your plans include time for changes to existing plugins in the near future, or whether I'd be better off trying to bring my old 1Wire scripts across to HS3.

Thanks,

Jon.

PS For some reason your plugins still aren't available to purchase...

[Ultrajones]

Yes, both ultra1wire2 and ultra1wire3 are fully supported. The message boards are not the best mechanism for reporting issues as posts can be easily missed. I need to look into some type of trouble ticket mechanism so issues can be assigned tracking number and they can be tracked to completion.

Thank you for bringing this issue to my attention. I thought I had this issue resolved, but apparently not. I was able to duplicate the issue. I have prior commitments tonight and tomorrow but should be able to get a fix posted by Friday. Thank you for your patience.

Regards,
Ultrajones

[Jon798]

That's great news - thanks.

I should probably point out that the levels reported by these DS2348-based light sensors routinely go up to 120% for some reason, and sometimes as high as 140%, so the 0% to 100% range you might expect isn't necessarily appropriate. There's maybe some sort of two's complement thing going on as well, because sometimes when it's really dark and cool, the light level gets reported as 320% which is clearly rubbish!

It's not just one of them, though, this happens with 3 different MS-TL sensors.

Thanks again,

Jon.

[Ultrajones]

Jon, when the DS2348-based light sensors report these crazy readings, are they being seen by the plug-in as a light sensor or a humidly sensor?

[Jon798]

The plugin shows them as humidity sensors - I've never managed to make the 'light level' setting 'stick'.

But the same raw readings are reported via the OW-Server's inbuilt web-page and I used to get the same silly readings when I used a Ha7E interface. When I used scripts to read the Ha7E I had to put a load of daft logic in along the lines of "if reading >150 then set to 0".

My quest to find an accurate and reliable light sensor to measure outdoor light levels continues (so far these MS-TLs are the best I've found despite these mad readings every now and then)...

Cheers,

Jon.

[Ultrajones]

Hello Jon. I was able to resolve this issue. Please download the update and let me know if it works for the 3 sensors you have.

Regards,
Ultrajones

[Jon798]

Hello,

Yes it is now possible to save the device as type 'light level' rather than 'humidity' in the Ultra1wire3 tab of the device status.

But :
In the 'home' device management page they still show as type 'humidity'.

The status text is set to Lux when it ought to be %.

The status graphic is just the 100% bright one (i.e. Doesn't vary according to brightness)

The value range runs between 0 and 100 when the device routinely goes up to as much as 150%.

If I change the status text/graphics to accommodate the above points, it gets reset back to 0-100/single graphic when homeseer is restarted, so the changes are lost.

Thanks,

Jon.

[Ultrajones]

Hello,

In the 'home' device management page they still show as type 'humidity'.

This is correct. The 1-wire device is a humidity sensor. The subtype is "Light Level". You can rename the device to show it as a light level sensor.

The status text is set to Lux when it ought to be %.

It was changed from % to Lux at the request of another user, but % makes more sense, so I'll get it changed for the next release.

The status graphic is just the 100% bright one (i.e. Doesn't vary according to brightness)

This will be implemented in the next release.

The value range runs between 0 and 100 when the device routinely goes up to as much as 150%.

The value range for "Light Level" is 0 to 100. You were only seeing 150% because the previous plug-in thought it was a humidity sensor and not a Light Level sensor.

If I change the status text/graphics to accommodate the above points, it gets reset back to 0-100/single graphic when homeseer is restarted, so the changes are lost.

This is by design. However, the next release will have your suggested changes.

Regards,
Ultrajones

[Jon798]

Thanks very much.

I just wanted to note, though, that I currently have one sensor configured as a light level sensor and showing a value of 122 (bright sunny morning). This is after restarts of HS3 and the plugin:-

Technology AddressE900000145652126:H:AStatus122.129997253418 = UnknownValue122.129997253418 StringSupports StatusFalseDimmableFalseInterfaceUltra1Wire3

Also, in the middle of the night the typical reading is approximately 25 except for the odd occasion when it reads 309...

It's almost as though there's a +25 offset and that when the value dips below 24, it 'wraps' to 300+. This is nothing to do with your plugin I should add - these are the numbers direct from the OWServer and the same I used to see when connected via HA7E.

This is the logic I used to apply to these sensors, which would typically give me a range somewhere between 0 and 90%:-

If LevelNew > 165 Then
LevelNew = LevelOld
If LevelOld = 0 Then LevelNew = -25
End If
LevelNew = (LevelNew + 25) * 0.5
If LevelNew < 0 Then
LevelNew = 0
End If

In case it helps... I expect I am somewhat in the minority, though, with these things - I can't imagine Embedded Data Systems have sold that many to HomeSeer users?

Cheers,

Jon.

[mminehan]

I too am having he same problem with the status/graphics values being reset on a restart. Lux and pressure values seem to reset to 0-100. By the scale is millibars and 100 if far too low. Likewise for lux.

It would be great if these did not get reset.

Thanks, Marty