AD2Pi Hubitat Hub Intigration

General Discussion

AD2Pi Hubitat Hub Intigration

Postby raidflex » Thu Jan 10, 2019 12:35 pm

I switched over from Smartthings to Hubitat about 6 months ago and have moved over all my devices. I currently have a AD2Pi setup and with help from the Hubitat community have ported most of the ST app/driver code to work with Hubitat. But there is still one part left, which is the Hubitat Safety Monitor integration. This is equivalent to SHM on ST. In its current state the ported app allows me to arm/disarm the system from the Hubitat Safety monitor. But if I arm/dism from the keypad, the Hubitat Safety monitor's status does not update. Not being a developer I am looking for some assistance in both finishing the integration of Hubitat Safety Monitor and also cleaning up any old ST code that is not needed anymore.

I appreciate any assistance with this Thanks.

Below is the ported Hubitat app/driver.

https://github.com/HubitatCommunity/Hub ... armDecoder

This is some info app/driver porting and HSM.

https://community.hubitat.com/t/hubitat ... -api/934/3
https://community.hubitat.com/t/app-and ... ubitat/812
raidflex
newt
newt
 
Posts: 10
Joined: Wed May 31, 2017 10:50 am

Re: AD2Pi Hubitat Hub Intigration

Postby raidflex » Mon Feb 11, 2019 6:35 am

Bump, any help is appreciated.
raidflex
newt
newt
 
Posts: 10
Joined: Wed May 31, 2017 10:50 am

Re: AD2Pi Hubitat Hub Intigration

Postby mathewss » Mon Feb 11, 2019 4:50 pm

Thanks for the bump. This I had missed. Just looking over Hubitat and I already have many many questions. I currently use ST hub at my house but I have my issues and am more than willing to play with something else to see if it works better for me. Do they have a developer program so I can get my hands on a hub for my lab to play with?

I looked over this code but as far as I can see it looks to be the exact same thing as the ST groovy code. What exactly is this magic? Does this system support the exact same environment? It looks like from the diff I did that it has some differences in addressing things. It does not have the port # just the ip.

Best
Sean M
mathewss
Moderator
Moderator
 
Posts: 80
Joined: Fri Dec 06, 2013 11:14 am

Re: AD2Pi Hubitat Hub Intigration

Postby mathewss » Mon Feb 11, 2019 5:38 pm

I just ordered a Hubitat Elevation. This should be interesting. It looks to be focused on a few key issues that ST suffers from. One key one is the local only processing something HUGE for an alarm!

Please do let me know the "diff" or changes you have made to the driver so it works so I can get up to speed on what is needed to fix the SHM or what ever they call it in Hubitat.

Best
Sean M
mathewss
Moderator
Moderator
 
Posts: 80
Joined: Fri Dec 06, 2013 11:14 am

Re: AD2Pi Hubitat Hub Intigration

Postby raidflex » Thu Feb 21, 2019 7:14 am

mathewss wrote:I just ordered a Hubitat Elevation. This should be interesting. It looks to be focused on a few key issues that ST suffers from. One key one is the local only processing something HUGE for an alarm!

Please do let me know the "diff" or changes you have made to the driver so it works so I can get up to speed on what is needed to fix the SHM or what ever they call it in Hubitat.

Best
Sean M


There was not many changes to the Network driver, most changes were to the AlarmDecoder smartapp. It was a couple months ago so I am not sure the exact changes but if you compare these you should be able to see the changes. The original developer has updated the smartapp/driver recently so I modified my HE code to reflect these changes, so the only differences at this point should be for HE compatibility.

This is my version for HE.
https://github.com/HubitatCommunity/Hubitat-AlarmDecoder

This is the original version for ST.

https://github.com/nutechsoftware/alarmdecoder-smartthings

I also do see this error in the logs when I arm/disarm from the Hubitat Safety Monitor (SHM equivalent). But it does arm properly, its going the other way that is the issue. If I arm from the panel then HSM does not get updated with the status.

Code: Select all
dev:10342019-02-19 03:13:09.276 pm errorgroovy.lang.MissingMethodException: No signature of method: dev155025803993043685673.disarm() is applicable for argument types: () values: []
Possible solutions: isCase(java.lang.Object), is(java.lang.Object), wait(), push(), every(), find() (disarm)
raidflex
newt
newt
 
Posts: 10
Joined: Wed May 31, 2017 10:50 am

Re: AD2Pi Hubitat Hub Intigration

Postby mathewss » Mon Mar 11, 2019 11:57 am

I finally manged to slice out some time at home to get this moving. It was an easy setup and IMHO in some ways more simple that the "Graph1" pages. As noted it is all local so that is cool. I get some errors from the device when I delete the AD2* service I suspect this is a reasonable bug and not a reflection on the stability of the web services provided by the very tiny and fast Hubitat hub.

Load code was not too bad. I chose to view your changes RAW on github and load them using the URL option in the web interface.
Very easy but will need to be documented.
https://raw.githubusercontent.com/Hubit ... ice.groovy

I did find a typo I noted in github and stuff was nto working correctly so I was busy writing code last night.

The sendEvent(app,addZone,bar) recent work did not work :( I changed it to just add the zone it that worked fine.
The Hubitat Safety Monitor or for SmartThings the SHM are similar but the event names were different. I tried to change these to match the documentation for the HSM and it was not working. I will continue this evening to see why but it "should" have worked with the fixes I did.

I "think" I can support both ST and HT with one base of code. I will see about bringing these changes in and just have it be a setting for ST vs HT
Maybe better in the long run since the code is the same only different in some of the names and how addressing works. Both easy to resolve in code.

Best
Sean M
mathewss
Moderator
Moderator
 
Posts: 80
Joined: Fri Dec 06, 2013 11:14 am

Re: AD2Pi Hubitat Hub Intigration

Postby raidflex » Tue Mar 12, 2019 5:36 am

Thanks for looking at the code! If you need any testing I am more then willing to help out.
raidflex
newt
newt
 
Posts: 10
Joined: Wed May 31, 2017 10:50 am

Re: AD2Pi Hubitat Hub Intigration

Postby raidflex » Thu Apr 11, 2019 10:48 am

Thanks for the updates to the code, it seems to be working well so far. I do however see this error in the logs when arming/disarming the system from HSM. If I arm/disarm the system from the Alarmdecoder device in HE, I do not see the error, its only when using HSM.

Code: Select all
groovy.lang.MissingMethodException: No signature of method: user_app_alarmdecoder_AlarmDecoder_service_193.statusHandler() is applicable for argument types:
raidflex
newt
newt
 
Posts: 10
Joined: Wed May 31, 2017 10:50 am

Re: AD2Pi Hubitat Hub Intigration

Postby andersondg » Wed Jan 29, 2020 9:25 am

I have just recently migrated from ST to Hubitat and have my AD2Pi integrated with my Hubitat hub using the latest app and drivers. All of the devices and apps were created successfully and I am able to arm/disarm my panel using modes and rules from Hubitat. However, I am unable to get current panel status or arm/disarm thru HSM like I was with ST's SHM. Is there some additional configuration that I'm missing?

Thank you in advance!!
andersondg
newt
newt
 
Posts: 7
Joined: Thu Aug 03, 2017 7:48 am

"rfxSet: Could not find 'RFX-XXXXXXX-0-1-0-0-0-0|XXX' device

Postby andersondg » Thu Feb 13, 2020 5:36 pm

I have migrated from ST to Hubitat. In Hubitat I am seeing many "rfxSet: Could not find 'RFX-XXXXXXX-0-1-0-0-0-0|XXX' device error entries in the AlarmDecoder Service log. I have tried "Rebuild Virtual Devices" with no effect. The following is from the event logs:

app:972020-02-08 11:09:49.275 am errorrfxSet: Could not find 'RFX-1046060-0-0-0-0-0-0|XXX' device.
app:972020-02-08 11:09:49.256 am inforfxSet 1046060:0:0:0:0:0:0
app:972020-02-08 11:09:46.317 am errorrfxSet: Could not find 'RFX-0404608-1-0-0-1-1-1|XXX' device.
app:972020-02-08 11:09:46.298 am inforfxSet 0404608:1:0:0:1:1:1
app:972020-02-08 11:09:07.719 am errorrfxSet: Could not find 'RFX-0614170-0-0-0-0-0-0|XXX' device.
app:972020-02-08 11:09:07.686 am inforfxSet 0614170:0:0:0:0:0:0
app:972020-02-08 11:09:05.100 am errorrfxSet: Could not find 'RFX-0614170-0-0-1-0-0-0|XXX' device.
app:972020-02-08 11:09:05.078 am inforfxSet 0614170:0:0:1:0:0:0
app:972020-02-08 11:07:26.420 am errorrfxSet: Could not find 'RFX-0061446-0-1-0-1-0-0|XXX' device.
app:972020-02-08 11:07:26.399 am inforfxSet 0061446:0:1:0:1:0:0
app:972020-02-08 11:05:55.661 am errorrfxSet: Could not find 'RFX-0404480-1-1-1-1-1-1|XXX' device.
app:972020-02-08 11:05:55.641 am inforfxSet 0404480:1:1:1:1:1:1
app:972020-02-08 11:05:52.666 am errorrfxSet: Could not find 'RFX-1046060-0-0-1-0-0-0|XXX' device.
app:972020-02-08 11:05:52.638 am inforfxSet 1046060:0:0:1:0:0:0
app:972020-02-08 11:05:44.800 am errorrfxSet: Could not find 'RFX-0614170-0-0-0-0-0-0|XXX' device.
app:972020-02-08 11:05:44.777 am inforfxSet 0614170:0:0:0:0:0:0
app:972020-02-08 11:05:41.811 am errorrfxSet: Could not find 'RFX-0614170-0-0-1-0-0-0|XXX' device.
app:972020-02-08 11:05:41.791 am inforfxSet 0614170:0:0:1:0:0:0
app:972020-02-08 10:59:17.028 am errorrfxSet: Could not find 'RFX-0330660-0-1-0-0-0-0|XXX' device.
app:972020-02-08 10:59:17.006 am inforfxSet 0330660:0:1:0:0:0:0
app:972020-02-08 10:56:27.448 am errorrfxSet: Could not find 'RFX-0967680-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:56:27.417 am inforfxSet 0967680:0:1:1:0:0:0
app:972020-02-08 10:53:40.819 am errorrfxSet: Could not find 'RFX-0276895-0-1-0-0-0-0|XXX' device.
app:972020-02-08 10:53:40.791 am inforfxSet 0276895:0:1:0:0:0:0
app:972020-02-08 10:52:46.689 am errorrfxSet: Could not find 'RFX-0015816-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:52:46.664 am inforfxSet 0015816:0:1:1:0:0:0
app:972020-02-08 10:52:16.812 am infoError creating device: disarm
app:972020-02-08 10:52:16.798 am infoError creating device: alarmAUX
app:972020-02-08 10:52:16.785 am infoError creating device: alarmPanic
app:972020-02-08 10:52:16.771 am infoError creating device: alarmFireStatus
app:972020-02-08 10:52:16.754 am infoError creating device: alarmFire
app:972020-02-08 10:52:16.741 am infoError creating device: alarmBellStatus
app:972020-02-08 10:52:16.725 am infoError creating device: readyStatus
app:972020-02-08 10:52:16.712 am infoError creating device: bypassStatus
app:972020-02-08 10:52:16.698 am infoError creating device: chimeModeStatus
app:972020-02-08 10:52:16.685 am infoError creating device: chimeMode
app:972020-02-08 10:52:16.671 am infoError creating device: exitStatus
app:972020-02-08 10:52:16.657 am infoError creating device: exit
app:972020-02-08 10:52:16.644 am infoError creating device: armAwayStatus
app:972020-02-08 10:52:16.631 am infoError creating device: armAway
app:972020-02-08 10:52:16.617 am infoError creating device: armStayStatus
app:972020-02-08 10:52:16.598 am infoError creating device: armStay
app:972020-02-08 10:52:16.579 am infoError creating device: smokeAlarm
app:972020-02-08 10:52:16.556 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 20
app:972020-02-08 10:52:16.542 am infoApp Event: addZone 20
app:972020-02-08 10:52:16.539 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 19
app:972020-02-08 10:52:16.526 am infoApp Event: addZone 19
app:972020-02-08 10:52:16.524 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 18
app:972020-02-08 10:52:16.510 am infoApp Event: addZone 18
app:972020-02-08 10:52:16.508 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 17
app:972020-02-08 10:52:16.493 am infoApp Event: addZone 17
app:972020-02-08 10:52:16.491 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 16
app:972020-02-08 10:52:16.475 am infoApp Event: addZone 16
app:972020-02-08 10:52:16.472 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 15
app:972020-02-08 10:52:16.447 am infoApp Event: addZone 15
app:972020-02-08 10:52:16.445 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 14
app:972020-02-08 10:52:16.431 am infoApp Event: addZone 14
app:972020-02-08 10:52:16.429 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 13
app:972020-02-08 10:52:16.415 am infoApp Event: addZone 13
app:972020-02-08 10:52:16.412 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 12
app:972020-02-08 10:52:16.398 am infoApp Event: addZone 12
app:972020-02-08 10:52:16.396 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 11
app:972020-02-08 10:52:16.382 am infoApp Event: addZone 11
app:972020-02-08 10:52:16.379 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 10
app:972020-02-08 10:52:16.365 am infoApp Event: addZone 10
app:972020-02-08 10:52:16.362 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 9
app:972020-02-08 10:52:16.347 am infoApp Event: addZone 9
app:972020-02-08 10:52:16.344 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 8
app:972020-02-08 10:52:16.330 am infoApp Event: addZone 8
app:972020-02-08 10:52:16.327 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 7
app:972020-02-08 10:52:16.310 am infoApp Event: addZone 7
app:972020-02-08 10:52:16.307 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 6
app:972020-02-08 10:52:16.294 am infoApp Event: addZone 6
app:972020-02-08 10:52:16.291 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 5
app:972020-02-08 10:52:16.277 am infoApp Event: addZone 5
app:972020-02-08 10:52:16.274 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 4
app:972020-02-08 10:52:16.258 am infoApp Event: addZone 4
app:972020-02-08 10:52:16.256 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 3
app:972020-02-08 10:52:16.240 am infoApp Event: addZone 3
app:972020-02-08 10:52:16.237 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 2
app:972020-02-08 10:52:16.222 am infoApp Event: addZone 2
app:972020-02-08 10:52:16.219 am errorThere was an error (java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI) when trying to addZone 1
app:972020-02-08 10:52:16.201 am infoApp Event: addZone 1
app:972020-02-08 10:52:16.197 am infoError creating device root device AlarmDecoder UI
app:972020-02-08 10:51:57.155 am errorrfxSet: Could not find 'RFX-0011907-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:51:57.135 am inforfxSet 0011907:0:1:1:0:0:0
app:972020-02-08 10:51:30.828 am errorrfxSet: Could not find 'RFX-0287309-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:51:30.789 am inforfxSet 0287309:0:1:1:0:0:0
app:972020-02-08 10:50:44.907 am errorrfxSet: Could not find 'RFX-0015762-0-1-0-1-0-0|XXX' device.
app:972020-02-08 10:50:44.874 am inforfxSet 0015762:0:1:0:1:0:0
app:972020-02-08 10:48:27.968 am errorrfxSet: Could not find 'RFX-0221316-0-0-0-0-0-0|XXX' device.
app:972020-02-08 10:48:27.947 am inforfxSet 0221316:0:0:0:0:0:0
app:972020-02-08 10:43:59.401 am errorrfxSet: Could not find 'RFX-1028560-0-1-0-1-0-0|XXX' device.
app:972020-02-08 10:43:59.369 am inforfxSet 1028560:0:1:0:1:0:0
app:972020-02-08 10:42:59.318 am errorrfxSet: Could not find 'RFX-0426168-0-1-0-0-0-0|XXX' device.
app:972020-02-08 10:42:59.282 am inforfxSet 0426168:0:1:0:0:0:0
app:972020-02-08 10:41:40.496 am errorrfxSet: Could not find 'RFX-0486916-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:41:40.439 am inforfxSet 0486916:0:1:1:0:0:0
app:972020-02-08 10:35:26.937 am errorrfxSet: Could not find 'RFX-0331500-0-1-0-0-0-0|XXX' device.
app:972020-02-08 10:35:26.889 am inforfxSet 0331500:0:1:0:0:0:0
app:972020-02-08 10:32:04.615 am errorrfxSet: Could not find 'RFX-0723106-0-1-0-1-0-0|XXX' device.
app:972020-02-08 10:32:04.581 am inforfxSet 0723106:0:1:0:1:0:0
app:972020-02-08 10:30:06.500 am errorrfxSet: Could not find 'RFX-0348980-0-1-0-1-0-0|XXX' device.
app:972020-02-08 10:30:06.468 am inforfxSet 0348980:0:1:0:1:0:0
app:972020-02-08 10:30:03.859 am errorrfxSet: Could not find 'RFX-1013842-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:30:03.816 am inforfxSet 1013842:0:1:1:0:0:0
app:972020-02-08 10:28:44.679 am errorrfxSet: Could not find 'RFX-0578564-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:28:44.645 am inforfxSet 0578564:0:1:1:0:0:0
app:972020-02-08 10:27:36.037 am errorrfxSet: Could not find 'RFX-0029214-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:27:36.004 am inforfxSet 0029214:0:1:1:0:0:0
app:972020-02-08 10:20:05.250 am errorrfxSet: Could not find 'RFX-0331188-0-1-0-0-0-0|XXX' device.
app:972020-02-08 10:20:05.220 am inforfxSet 0331188:0:1:0:0:0:0
app:972020-02-08 10:15:12.895 am errorrfxSet: Could not find 'RFX-0080861-0-1-1-0-0-0|XXX' device.
app:972020-02-08 10:15:12.863 am inforfxSet 0080861:0:1:1:0:0:0
app:972020-02-08 10:08:04.551 am errorrfxSet: Could not find 'RFX-0688416-0-1-0-1-1-1|XXX' device.
app:972020-02-08 10:08:04.522 am inforfxSet 0688416:0:1:0:1:1:1
app:972020-02-08 10:07:52.034 am errorrfxSet: Could not find 'RFX-0985729-0-0-1-1-0-0|XXX' device.
app:972020-02-08 10:07:52.001 am inforfxSet 0985729:0:0:1:1:0:0
app:972020-02-08 10:01:29.553 am errorrfxSet: Could not find 'RFX-0985729-0-0-0-1-0-0|XXX' device.
app:972020-02-08 10:01:29.521 am inforfxSet 0985729:0:0:0:1:0:0
app:972020-02-08 10:01:24.961 am errorrfxSet: Could not find 'RFX-0985729-0-0-1-1-0-0|XXX' device.
app:972020-02-08 10:01:24.934 am inforfxSet 0985729:0:0:1:1:0:0
app:972020-02-08 09:59:08.998 am errorrfxSet: Could not find 'RFX-0317185-0-1-1-0-0-0|XXX' device.
app:972020-02-08 09:59:08.972 am inforfxSet 0317185:0:1:1:0:0:0
app:972020-02-08 09:57:06.922 am errorrfxSet: Could not find 'RFX-1046060-0-0-0-0-0-0|XXX' device.
app:972020-02-08 09:57:06.887 am inforfxSet 1046060:0:0:0:0:0:0
app:972020-02-08 09:57:03.904 am errorrfxSet: Could not find 'RFX-1046060-0-0-1-0-0-0|XXX' device.
app:972020-02-08 09:57:03.880 am inforfxSet 1046060:0:0:1:0:0:0
app:972020-02-08 09:57:01.001 am errorrfxSet: Could not find 'RFX-0614170-0-0-0-0-0-0|XXX' device.
app:972020-02-08 09:57:00.970 am inforfxSet 0614170:0:0:0:0:0:0
app:972020-02-08 09:56:58.010 am errorrfxSet: Could not find 'RFX-0989824-0-1-0-1-0-0|XXX' device.
app:972020-02-08 09:56:57.972 am inforfxSet 0989824:0:1:0:1:0:0
app:972020-02-08 09:53:54.177 am errorrfxSet: Could not find 'RFX-1046060-0-0-0-0-0-0|XXX' device.
app:972020-02-08 09:53:54.154 am inforfxSet 1046060:0:0:0:0:0:0
app:972020-02-08 09:53:51.147 am errorrfxSet: Could not find 'RFX-0614170-0-0-0-0-0-0|XXX' device.
app:972020-02-08 09:53:51.125 am inforfxSet 0614170:0:0:0:0:0:0
app:972020-02-08 09:53:50.870 am errorrfxSet: Could not find 'RFX-1046060-0-0-1-0-0-0|XXX' device.
app:972020-02-08 09:53:50.846 am inforfxSet 1046060:0:0:1:0:0:0
app:972020-02-08 09:53:48.327 am errorrfxSet: Could not find 'RFX-0614170-0-0-1-0-0-0|XXX' device.
app:972020-02-08 09:53:48.301 am inforfxSet 0614170:0:0:1:0:0:0
app:972020-02-08 09:53:21.183 am errorrfxSet: Could not find 'RFX-0330660-0-1-0-0-0-0|XXX' device.
app:972020-02-08 09:53:21.159 am inforfxSet 0330660:0:1:0:0:0:0
app:972020-02-08 09:48:18.003 am errorrfxSet: Could not find 'RFX-0614170-0-0-0-0-0-0|XXX' device.
app:972020-02-08 09:48:17.964 am inforfxSet 0614170:0:0:0:0:0:0
app:972020-02-08 09:48:14.668 am errorrfxSet: Could not find 'RFX-0614170-0-0-1-0-0-0|XXX' device.
app:972020-02-08 09:48:14.634 am inforfxSet 0614170:0:0:1:0:0:0
app:972020-02-08 09:47:03.346 am errorrfxSet: Could not find 'RFX-0967680-0-1-1-0-0-0|XXX' device.
app:972020-02-08 09:47:03.315 am inforfxSet 0967680:0:1:1:0:0:0
app:972020-02-08 09:46:04.934 am errorrfxSet: Could not find 'RFX-0404480-1-0-1-1-1-1|XXX' device.
app:972020-02-08 09:46:04.904 am inforfxSet 0404480:1:0:1:1:1:1
app:972020-02-08 09:46:02.122 am errorrfxSet: Could not find 'RFX-1046060-0-0-1-0-0-0|XXX' device.
app:972020-02-08 09:46:02.026 am inforfxSet 1046060:0:0:1:0:0:0
--- Live Log Started, waiting for events ---

All seems to be working well, I'm just afraid that this is having a negative impact on performance.

Thanks in advance for your help!
andersondg
newt
newt
 
Posts: 7
Joined: Thu Aug 03, 2017 7:48 am


Return to General

Who is online

Users browsing this forum: No registered users and 1 guest