Valve Status Change Messages not working? 2007-03-31T22:58:18+00:00

HOME Forums Irrigation EZFlora Valve Status Change Messages not working?

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • Anonymous
    Post count: 6
    #39709 |

    I’m working on a HomeSeer script to control my EZRain device. So far it’s working well exept for keeping track of valve status, specifically when a sprinkler program is running.

    To keep abreast of the changes in valve status, I enable Valve Status Change Messages. This works fine up until another Insteon message from _any_ device (even the EZRain itself) comes along. In other words, I can prevent the 0x27 Status Changed messages from being sent simply turning on my Insteon hallway light switch. At this point, all 0x27 messages stop until I send the EZRain device another Enable Valve Status Change message.

    The only way I’ve gotten around this is to send a 0x44 0x09 Enable Valve Status Change command every time any Insteon traffic is detected. Obviously, this brute-force method introduces too much extraneous Insteon “chatter” to be a long-term solution.

    FYI, the sticker on the back of my EZRain device claims PLM FIRM 2.3.

    Any ideas?

    Thanks,
    -Randy

    Anonymous
    Post count: 6

    Thanks for the insightful reply, Dolf.

    Simplehomenet folks: Is there a better forum for developer/tech support I should post to?

    Thanks,
    -Randy

    Anonymous
    Post count: 192

    OH yes. Seems to be a trend these days.
    Hit the Smarthome site last weekend with I believe 100 messages.
    Wish there was a notify administrator tab here.

    Anonymous
    Post count: 408

    Dolf has been banned – we try to stay on top of this, but unfortunately we cannot get them real time. It is a hard balance – security / usability. If it becomes much more abused, we will tighten things down further.

    Back to on topic, we have been investigating. At first, I can tell you I could not reproduce the problem you are seeing, but we are checking out some things. Sorry for the time it is taking to get you an answer.

    Anonymous
    Post count: 6

    Note that I set all valve timers to 1 minute just to make it quicker to test things. Perhaps such short timers are contributing to the problem.

    It could be also be an issue with Homerseer blocking these messages, I suppose, which would explain why you cannot reproduce this. Either way, I appreciate you looking into it.

    -Randy

    Anonymous
    Post count: 1

    Randy,

    Hi. Any updates on this issue? Have you been able to resolve it and, if so, how? I’d appreciate all help.

    With kind regards,
    Michel

    @randyth wrote:

    Note that I set all valve timers to 1 minute just to make it quicker to test things. Perhaps such short timers are contributing to the problem.

    It could be also be an issue with Homerseer blocking these messages, I suppose, which would explain why you cannot reproduce this. Either way, I appreciate you looking into it.

    -Randy

    Anonymous
    Post count: 256

    WE have tested this feature extensively and can’t reproduce what is reported seen with HomeSeer or a PLM (as used with the ISY.) Our definite test for monitoring traffic is using the SmartLabs Salad IDE with a USB PLC on which we have manually established a link of the EZRain under test. One minute timers are fine, as there is no criticality on valve change triggering the broadcast message. Please verify the functionality of the PLM by using the scheme suggested.

    Anonymous
    Post count: 20

    Have you tried to instrument the code? I did this extensively when I was trying to figure out what was going on between HomeSeer and my EZIO.

    I am still trying to iron out any wrinckles in the setup, but just by placing a bunch of hs.writelog commands in the code and looking at the HomeSeer log, I was at least able to trace the Insteon traffic back and forth.

    I would start with whatever method is registered to your EZRain device.

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.