Blackbird Posted December 12, 2018 Share Posted December 12, 2018 For some reason the Agave app is showing the status of doors incorrectly. Mobilinc is accurate but not Agave. For example, I load Agave and see that my patio door is showing open even though its closed. I open the door then close it then the status shows closed. Anyone else having this problem? Link to comment
MWareman Posted December 12, 2018 Share Posted December 12, 2018 What are you using as your sensor? Do you have ‘trigger reverse’ set? What about after a query? Link to comment
Blackbird Posted December 13, 2018 Author Share Posted December 13, 2018 Insteon door sensors. No trigger reverse. Not sure about the query. Did a refresh data on agave. Just checked and my Patio door is showing open again and I haven't touched it as well as a few of my other doors which are actually closed. Link to comment
Blackbird Posted December 13, 2018 Author Share Posted December 13, 2018 Going to try a data reset Link to comment
Blackbird Posted December 13, 2018 Author Share Posted December 13, 2018 Reseting the data worked then a couple hours later I see that all my wireless sensors are reversed. All doors show open and the leak sensors only show "dry" with a status of dry. No "wet" sensors Link to comment
Blackbird Posted December 13, 2018 Author Share Posted December 13, 2018 The home screen shows some doors closed. Then when I look in the Sensor/security section is says open the I go back to the home screen and that says open. What is wrong with this app? Link to comment
MWareman Posted December 16, 2018 Share Posted December 16, 2018 When a sensor shows reversed in Agave, what does it show in UDAjax (or the Admin Console)?I believe that Agave is only reporting what the ISY is telling it. Unless ISY is sending it data that’s not being parsed correctly. In this case, get the xml response from a REST query of the device and send it to the author so he can look into it. Link to comment
Blackbird Posted December 16, 2018 Author Share Posted December 16, 2018 Not sure what the UDAjax is but those sensors are showing correct on mobilinc and on the isy (admin console I guess) Link to comment
Blackbird Posted December 16, 2018 Author Share Posted December 16, 2018 I am showing 5 screen shots labeled 1 through 5. This is the sequence I used when loading up Agave a few minutes ago. See how the first home page is correct then by going to sensors/security, it changes the status. Link to comment
Blackbird Posted December 16, 2018 Author Share Posted December 16, 2018 checking Mobilinc and the Admin Console, they both show correct status. This Problem has been going on for more than a year. Maybe the whole time. Link to comment
James Peterson Posted December 16, 2018 Share Posted December 16, 2018 Blackbird - Please send me a node dump of those sensors. http://agaveha.com/docs/node-dump/ . You can respond on this thread or on our email thread. I am also waiting for your debug log when using a current version of Agave. Link to comment
Blackbird Posted December 17, 2018 Author Share Posted December 17, 2018 Emailed to you. Didn't see the update. Will update now. Link to comment
Blackbird Posted December 21, 2018 Author Share Posted December 21, 2018 Since updating Agave I have not had this issue. Things seem to be working fine. Hopefully this problem is gone for good. Thanks for the help Link to comment
Blackbird Posted December 30, 2018 Author Share Posted December 30, 2018 More problems. I sent the debug report. The previous problem of the steps shown in the previous post seem to still be corrected. The problem I have now (maybe all along) is when im on the home screen and I tap on the icon in the top left of the device (only noticed this for doors) it takes me to the option screen as it should and the device reads closed which is correct but when I go back to the home screen, it changes the status to OPEN which is incorrect. I can make it do this every single time for all my doors. Simply refreshing the data doesn't always correct it, sometimes I have to refresh data and clear app cache then reload Agave and the status's are all correct. I have one door that is physically open so when I click on the icon in the upper left corner for that door, I would expect the status to show incorrectly as closed but it doesn't, it remains open. Link to comment
oetbyg Posted January 31, 2019 Share Posted January 31, 2019 I have one 2843-222 door sensor that when closed, shows its status correctly on the ISY, but wrongly on Agave. The 'reverse status' is not checked. If I cycle it, Agave reads correctly for a time, but when refreshed reverts to 'open' when the door is closed. It reads correctly when the door is open, even after refreshed. I also have 3 2845-222s that work correctly. All 4 of them show up as the same <type>16.17.69.0</type> in a node dump. I would appreciate help on this. Thanks, Link to comment
James Peterson Posted January 31, 2019 Share Posted January 31, 2019 2 minutes ago, oetbyg said: I have one 2843-222 door sensor that when closed, shows its status correctly on the ISY, but wrongly on Agave. The 'reverse status' is not checked. If I cycle it, Agave reads correctly for a time, but when refreshed reverts to 'open' when the door is closed. It reads correctly when the door is open, even after refreshed. I also have 3 2845-222s that work correctly. All 4 of them show up as the same <type>16.17.69.0</type> in a node dump. I would appreciate help on this. Thanks, What mode are your devices in? Link to comment
oetbyg Posted January 31, 2019 Share Posted January 31, 2019 Now I have to show my ignorance. I don't know. How do I learn that? I believe I set them all up the same way. Link to comment
James Peterson Posted January 31, 2019 Share Posted January 31, 2019 2 minutes ago, oetbyg said: Now I have to show my ignorance. I don't know. How do I learn that? I believe I set them all up the same way. start on page 4: http://cache.insteon.com/documentation/2843-222-en.pdf Link to comment
Blackbird Posted February 4, 2019 Author Share Posted February 4, 2019 Glad to see im not the only one with this problem Link to comment
James Peterson Posted February 5, 2019 Share Posted February 5, 2019 @Blackbird @oetbyg Can I confirm that this is just with the 2843-222 and no issues with the 2845-222? Link to comment
oetbyg Posted February 5, 2019 Share Posted February 5, 2019 4 minutes ago, James Peterson said: @Blackbird @oetbyg Can I confirm that this is just with the 2843-222 and no issues with the 2845-222? That is the case for me. 3 hidden door sensors (2845-222) work OK, the Open/Close sensor (2843-222) does not. Link to comment
oetbyg Posted February 5, 2019 Share Posted February 5, 2019 25 minutes ago, oetbyg said: That is the case for me. 3 hidden door sensors (2845-222) work OK, the Open/Close sensor (2843-222) does not. The two types show identical behavior in the UD console event viewer if that's any help: 2843-222: Tue 02/05/2019 10:07:13 : [ 3B 3F 83 1] DON 1 Tue 02/05/2019 10:07:13 : [ 3B 3F 83 1] ST 255 (uom=100 prec=0) Tue 02/05/2019 10:07:16 : [ 3B 3F 83 1] DOF 1 Tue 02/05/2019 10:07:16 : [ 3B 3F 83 1] ST 0 (uom=100 prec=0) 2845-222: Tue 02/05/2019 10:02:53 : [ 2D EF 2F 1] DON 1 Tue 02/05/2019 10:02:53 : [ 2D EF 2F 1] ST 255 (uom=100 prec=0) Tue 02/05/2019 10:02:56 : [ 2D EF 2F 1] DOF 1 Tue 02/05/2019 10:02:56 : [ 2D EF 2F 1] ST 0 (uom=100 prec=0) Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.