Comfort  Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register
Comfort Automation/ Security System Forums > Third Party (interfacing to Comfort) > alphaWerk UHAI RPi (Community Edition) > Problems getting started (device network id must be unique) and a few other issues

Problems getting started (device network id must be unique) and a few other issues
 Moderated by: slychiu, mattbrain, benstinton Page:    1  2  Next Page Last Page  
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Tuesday Nov 14th, 2017 01:33 am
   PM  Quote  Reply 
1st Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi Matt,
for info, my seriel number is 000000009e04c47f[size=
]

[code]
Posted in another thread, but prob better off doing a new one as I seem to have a few issues.
I have followed the guide and dont really see any error messages until I get to the discovery bit, so i am asssuming I am doing things right, but prob missing somehting obvious.

1) I notice my alarm file, despite me uploading a revused version of it, does no seem to be uploading. For example, I set the number of counters to be looked at to just counters =50, and responses =301,302  so I expect a fairly limited number of devices to be discovered. I limited the number of zones to 1, the number of outputs to 1, the number of counters to 1 and the number of responses to just 2 responses (301 and 302). 
However, when I upload my alarm file and download it again, it seems to show a full range of inputs, outputs etc, ie, it does not seem to be uploading the file!

2) When I to discovery in the smart app, I get a list of devices, I select just one, as a test, and when I go to save it, I get the error "device id must be unique".
In order to resolve, I have pretty much deleted the "my smart app" and all the "my device handlers" files and redid them, but to no avail, I am still getting the same error.

I feel, so close, hope its something obvious!



 Posted: Tuesday Nov 14th, 2017 02:58 am
   PM  Quote  Reply 
2nd Post
mattbrain
UCM Pi Users


Joined: Tuesday Jun 12th, 2007
Location: United Kingdom
Posts: 185
Status: 
Offline

  back to top

Hi Wexfordmad

Thanks for downloading the software - and your donation :)

I have seen your telemetry data, I'll take a look at it tomorrow and see what is going on. It does look like it has correctly connected to the alarm so it is probably a config issue. As you say its probably something simple - but I know that the current config mechanism isn't particularly intuitive - it is something we are working on improving.

Thanks,

Matt



 Posted: Tuesday Nov 14th, 2017 03:00 am
   PM  Quote  Reply 
3rd Post
mattbrain
UCM Pi Users


Joined: Tuesday Jun 12th, 2007
Location: United Kingdom
Posts: 185
Status: 
Offline

  back to top

Hi Wexfordman.

From the web GUI can you send diagnostics please? That should give me all I need to debug what is going on.

Thanks,

Matt



 Posted: Tuesday Nov 14th, 2017 03:21 am
   PM  Quote  Reply 
4th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

THanks Matt,
Just sent it.
Thanks,.Eamon



 Posted: Tuesday Nov 14th, 2017 12:46 pm
   PM  Quote  Reply 
5th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi Matt,

Progress being made :-)

I have a number of devices now added, but just need to figure out now how to control them, before adding them to my google assistant.

I go into the comfort bridge device, and select the option "add response device" but it is not selectable, any idea what is happening here ?



 Posted: Tuesday Nov 14th, 2017 11:00 pm
   PM  Quote  Reply 
6th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Anyone a quick idea on what might be causing this latest issue, ie what am I missing ?

Cant add a response device type, i get no reaction when i select the option under the comfort bridge device ?



 Posted: Wednesday Nov 15th, 2017 12:46 am
   PM  Quote  Reply 
7th Post
Swiss-Toni
UCM Pi Users


Joined: Thursday Sep 15th, 2011
Location: Greater London, United Kingdom
Posts: 349
Status: 
Offline

  back to top

Have you entered your password in the alarm file on the R pi



 Posted: Wednesday Nov 15th, 2017 12:50 am
   PM  Quote  Reply 
8th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi Toni,

Yep, I can arm and disarm the system, and see counter states, zone states etc.

I cant add a a response device though for some reason. There are lots of existing "response" devices present, but I dont know what they are or what responses they refer to.

I tried to edit one to point it toward a response, and that didnt work, what I did was open the response device, renamed it and assigned on response of 300 and off response of 301 to it (these are the on/off response numbers in comfort). The response eitehr on or off didnt work though

Have I done it correctly ?



 Posted: Wednesday Nov 15th, 2017 03:12 pm
   PM  Quote  Reply 
9th Post
mattbrain
UCM Pi Users


Joined: Tuesday Jun 12th, 2007
Location: United Kingdom
Posts: 185
Status: 
Offline

  back to top

I have been working with WexfordMan to identify the issue and I have seen 2 new issues I am looking into.

1. Responses above 255 will not execute from the UHAI - this is as a result of double byte responses not being recognised. I will resolve this in the next release, but it can worked around by renumbering responses which need to be called from SmartThings or a new response can be added which triggers the target response. In either case make sure the response is numbered below 256.

2. SD Card filling up. I haven't seen this before and want to work closely with WexfordMan on working out what caused it. In normal operation the disk should never get close to being filled, but for some reason this has caused an issue on his install.

I'm going to start a new topic to get a poll of disk free as reported on the interface to see if anyone else is suffering.

Thanks,

Matt



 Posted: Thursday Nov 16th, 2017 03:17 am
   PM  Quote  Reply 
10th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Well, to update on Matts info above, with respect to now controlling devices in comfort, its now working a charm.

I did as Matt sugested and moved my response numbers to below 255 and it now works 100% of the time.

To be clear, I actually now have google assistant control of my comfort system, including my Velbus lighting system all now via matts solution. Google assistant control of velbus was not possible for me until this solution came about, I am absolutely thrilled, well done and thanks Matt.

Without droning on, I do recall building our house back on 2000, and putting in at the time smart lighting (was x10 at the time), comfort, homevision, and also I purchased a load of mics, mixers etc to get voice control via hal2000 at the time. It never worked, so this is nearly 20 years in the making. I have 5 google home devices spread about the house now, and each one of them is controlling my lighting via voice!
Just to explain why I had response numbers above 255, it was because i grouped response numbers together, so all my light responses were in the 300 range, its not that I had 300+ responses.

Fan feckin tastic!

Last edited on Thursday Nov 16th, 2017 03:46 am by wexfordman



 Posted: Thursday Nov 16th, 2017 01:50 pm
   PM  Quote  Reply 
11th Post
mattbrain
UCM Pi Users


Joined: Tuesday Jun 12th, 2007
Location: United Kingdom
Posts: 185
Status: 
Offline

  back to top

Hi Wexfordman


Really pleased you have it working - and you have finally realised your dream :)


I'm currently working with Chiu on the hardware implementation which will take this integration to the next level - and resolve many of the little niggles reported on this forum.


I'm hoping to have something exciting to share before the end of the year.


Thanks,


Matt



 Posted: Thursday Nov 16th, 2017 04:56 pm
   PM  Quote  Reply 
12th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Brilliant thanks Matt,
Just a quick question on status with regards to the status of devices in ST.
I can control devices, but I cannot see the status of them, is there a way of doing this so I can see the status as well ?
The status of a device is related to a comfort counter value, so there would need to be a way of alligning the counter value with the device ?



 Posted: Thursday Nov 16th, 2017 05:41 pm
   PM  Quote  Reply 
13th Post
mattbrain
UCM Pi Users


Joined: Tuesday Jun 12th, 2007
Location: United Kingdom
Posts: 185
Status: 
Offline

  back to top

Hi Wexfordman

Regular Comfort Outputs allow control and report back their status, as do alarm state controls. Comfort Inputs only report their status.

In terms of your request, I believe you have lights which are controlled via Responses and report their status via Counters. I believe to solve this we need create a device which allows control via Responses and reports status from Counters - and there are at least 2 ways we could do this.

1. Create a new device type which talks directly to the Comfort Bridge as do all the other Comfort controls in SmartThings. This would require a little development (probably by me or Ben, but I am happy to support another wiling volunteer) and could be added as an optional component in the same way that Response control is implemented.

2. Create a virtual device and use CoRE, webCore or other SmartThings code to link it to the associated Comfort Response and Counter Devices. This would probably be the quickest way to make this happen, although it isn't the most elegant (as it relies on other devices and creates a chain of dependancies).

Take a look at the behaviour of the Comfort Output devices as it transitions state - It goes from Off -> Turning On -> On. It has states 'Turning On' and 'Turning Off' along with error states 'Unknown' etc. which represent the last know good state of the device. With a device which uses Responses to control it and receiving status via Counters we need to think carefully about how state should be represented and what happens if a light which is already on is turned on (does the counter send a further unsolicited update to reflect the same state).

I don't have access to a lighting system which does this, but I could try and pull something together if you are a willing to be a guinea pig - unless you or someone else fancies having a crack at it...

Thanks,

Matt



 Posted: Thursday Nov 16th, 2017 05:53 pm
   PM  Quote  Reply 
14th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi Matt,
More than happy to be a guinea pig and help out any way I can.
One other possible option, is maybe to look at the way it it is implemented in comfort itself, perhaps slychui can advise a bit here. Here is what I am thinking

Currently, comfort counters are represented in ST, so rather than create a respnse device for a light, maybe the approach is to get ST to update the counter value itself ?
Comfort can then do a response when the counter value changes, and this response could be to turn on or off the light.
I am a bit confused, or unsure of how to manage this triggering a loop though, I tried it on one light, and while it worked, I ended up with a disco in the living room, as everytime the counter value changed, the light toggled. I think a little bit more logic would solve this though.
Slychui, when I did this, I was using older comfort firmware, but is there a change in recent firmware whcih fixes this loop effect, or do you think this is a workable solution ?



 Posted: Thursday Nov 16th, 2017 05:55 pm
   PM  Quote  Reply 
15th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

btw, if you want to try option 1, if you can give me a few pointers, I can see if I can muddle my way through it, although I have little to no coding experience



 Posted: Thursday Nov 16th, 2017 05:57 pm
   PM  Quote  Reply 
16th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

Matt, the is a problem with controlling by Response. When you specify a Response to execute, I believe you are actually using the Response number in a cclx file as it was at that time.

As you know, Response numbers can be changed by Comfigurator when you change or add Responses, as the software dynamically assigns Response numbers to fit into the response number space.  This would cause the wrong Response to be activated.

Fixing the Response numbers prevents this from happening but it is not an ideal solution as you may forget, and sometimes responses may need to be unfixed it they cannot fit

In most of the external UCMs, eg Cbus, KNX, Zwave, Modbus we have moved away from using Responses. Instead the external devices are mapped to Counters,  Flags, outputs, or inputs.

Mapping to Counters triggers the Counter Response. This does not depend on the Response number so the above problem does not apply.
If you use Counters, it can be used for control as well as feedback




 Posted: Thursday Nov 16th, 2017 06:06 pm
   PM  Quote  Reply 
17th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Hi Slychui,
But how do we stop the counter response from looping, for example, I just did the following test using latest firmware
Counter 59 (my velbus light counter) triggers response "corridor light test"
Corridorr light test does the following
if counter 59 =0,then do response "corridoor light on"else do response "corridorr light off"
So obviously when I do this, the minute I change counter 59 value I end up with a flashing light :-)  This happens when I change the state locally even without triggering it from ST or anywhere else.
BTW, with regards to using ST response devices, I did fix all my responses in comfort so that they wont change response numbers.

Last edited on Thursday Nov 16th, 2017 06:09 pm by wexfordman



 Posted: Thursday Nov 16th, 2017 06:12 pm
   PM  Quote  Reply 
18th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

Doh!!

I think I just figured it out, hold on a few mins!



 Posted: Thursday Nov 16th, 2017 06:16 pm
   PM  Quote  Reply 
19th Post
mattbrain
UCM Pi Users


Joined: Tuesday Jun 12th, 2007
Location: United Kingdom
Posts: 185
Status: 
Offline

  back to top

Hi Chui, Wexfordman

Counters are fully supported by the SmartThings interface with the Counters device and should support this use model allowing both control and feedback. I haven't used Counters myself in anger so would be very interested in hearing any and all feedback.

Thanks,

Matt



 Posted: Thursday Nov 16th, 2017 06:16 pm
   PM  Quote  Reply 
20th Post
wexfordman
UCM Pi Users
 

Joined: Monday Jan 1st, 2007
Location: Cork, Ireland
Posts: 546
Status: 
Offline

  back to top

nope, sorry,

I changed the respnse code to

if counter 59 =0, then do response corridoor light off, else do response corridor light on.

Same thing, disco in the corridorr :-)
I am missing something here, so close, probably very obvious too!

Last edited on Thursday Nov 16th, 2017 06:19 pm by wexfordman



 Current time is 02:04 amPage:    1  2  Next Page Last Page  
Comfort Automation/ Security System Forums > Third Party (interfacing to Comfort) > alphaWerk UHAI RPi (Community Edition) > Problems getting started (device network id must be unique) and a few other issues
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems