Domoticz

SweetPants wrote:After resetting the Nefit Easy Adapter (I have an old boiler), everything works again.

If you reset the adapter you take the power from the thermostat and then in essence reset the thermostat. This is probably what caused it to work again. Next time you can take the Easy from the wall again by clicking the button at the bottom, wait for a couple of seconds and the push it back on the mount again. This will do the same.

Hm, strange. Since it works for me since the last stable of domoticz on a pi, I suppose Nefit and Domoticz are not really the problem, but something in the os or surrounding network (settings).

We added one new option, that is also to read the gas value every 5 minutes... maybe that is causing the problem ? Or are you running a version from lets say 3 weeks ago? (This does not have the gas option)

And ... after doing nothing for 2 days, it's working again...
still a new version is being build that will request the new Gas value at another poll interval to 'relax' things

Marcel wrote:Next time you can take the Easy from the wall again by clicking the button at the bottom, wait for a couple of seconds and the push it back on the mount again. This will do the same.

I know, but taking the power of the Nefit adapter i can do from domoticz, so practically anytime/anywhere I want, or maybe detect it is going wrong and reset it automatically.

There is now a new version with a different poll interval.
So this could be an issue outside Domoticz/http-server?
Normally when you do not use Domoticz or have the Android/iOS application open, the thermostat is not polled that much....

gizmocuz wrote:There is now a new version with a different poll interval.

Thnx, just build it. Let see what happens

Maybe a domb question but I used the node-red option for a while. Unfortunately one of my pi's crashed the other day and lost a lot. I decided to rebuild my network from skretch. I see more developments with the http nefit server but lost track over 22 pages with posts how to install it.. Can some of you help me with it?

Tale a look at: https://github.com/robertklep/nefit-easy-http-server

gizmocuz wrote:There is now a new version with a different poll interval.
So this could be an issue outside Domoticz/http-server?
Normally when you do not use Domoticz or have the Android/iOS application open, the thermostat is not polled that much....

gizmo, what are the update intervals now? me personaly dont need the interval on 30 secs for temp, statusupdate, pressure, this can all be 1 or 2 minutes.
flow temperature is interesting for me to be 30 secs.

i will be trying the beta out now,,will give an update when i have more experience with the beta.

knights wrote:gizmo, what are the update intervals now?

Got this from sourcecode (seconds) in last beta 3.5116

#define NEFIT_FAST_POLL_INTERVAL 30
#define NEFIT_SLOW_INTERVAL 300
#define NEFIT_GAS_INTERVAL 400

Since the new polling interval I havent got any problems with strange timeouts. I have been stable for a few days now, I will give some more feedback when I have more data.

Great to see that the for me less important data such as. pressure and status are beeing polled on a slow interval.

I have been using the php version in combination with the easy httpd server for a while and that resulted in problems every few weeks. After I stopped using the php version it runs smoothly with only 2 disconnects in a few months.

I would love to have a built in option to give me a notice (Prowl?) that the easy httpd server hasn't been able to get data for about half an hour or so. That way we now we have to disconnect the wall-device for a few seconds to reset it. At least I think that's the only solution?

Is this something that could be built in Gizmocuz ?

Thanks for the feedback

@mvveelen, monit ? Or another monitoring application?

Monit already checks the easy httpd server for me on my Synology. But it can't check if the server passes its data to Domoticz. Right?

I think monit is able to check the response of the http output, when the connection is lost, you get a timeout message returned

OK, well, then I have to dig into that to find out HOW this could be done.

Although this would be a nice extra for Domoticz: if a weather station stops spitting out data, or when a temperature sensor stopped because of the batteries which are drained, or when doorsensors stop working because of drained batteries (this already can be noticed by looking at the hardware config in the zwave section), etc.

For hardware, we have already Hardware timeout....
So the thing to add would be a notification in case this happens ?

Could be handy?

But for me the most important at the moment is the status, or better yet, the output of the easy-httpd-server.
When I check Monit, it tells me:

Data collected Sat, 14 May 2016 16:27:36

And this every minute or so. Haven't figured out yet how to check the period between the "data collected instances", so if this could be built into Domoticz, that would even be better

I see there are a few problems mentioned here with the loss of connection, so if people could set a notification for it, you don't have to check it yourself, see ?

That is the hardware timeout... when no data (no sensor) is received from hardware named xxyy, then a notification (and a restart), not that a restart will help in this case