Error: CustomerCounter hardware (12) nothing received for more than 5 Minutes!
-
@sundberg84 thanks. I love Domoticz for being so easy to get started with, but I hate it for all the stupid design mistakes, like "last seen" not really being "last seen" and now this problem where PING has no real purpose. I checked the Domoticz source code yesterday and from what I can see it seems like Domoticz never even checks if it got a reply from the PING.
It might be time to bite the bullet and learn how to use a real controller like OpenHAB.
@mfalkvidd I have had the same thoughts but about HASS.
I think the Domoticz dev-team might be a litte to small and they rely on users making github push about things like this. Im no coder but got the question if I could code and try out the heartbeat function to update last seen and push it... I guess as well this is something you have to be aware of in DIY.
If you get any more insight in PING and last seen I would be happy to know the result.
-
@gohan As in 'Merde' ?
-
@gohan So was the Maginot Line..... ;)
-
No way it's French, I think it's Dutch :p
For a real French controller have a look at Jeedom. -
:D Easy guys or you'll end up upsetting someone :wink:
I like the idea of "last seen" as in "last time he showed up and he gave us news"... makes sense
-
:D Easy guys or you'll end up upsetting someone :wink:
I like the idea of "last seen" as in "last time he showed up and he gave us news"... makes sense
@ben999 that would be better described as "last update" so you have an idea of how old is the data you are seeing. Personally I don't like the fact that a data point in the graph is saved regardless if there has been an update or not because you don't know when the sensor actually sent the data
-
Irrespectively of the "interesting" design decisions on Domoticz (which I fully agree with), and the fact that almost every time a bug or improvement report is submitted the answers seems to be most frequently "please code it yourself", or even "that feature is already included in next beta" which then turns out to be just not true... even though it generally works quite well, some things are very annoying so I'm actually also starting to think on a move to openhab.
...back to the gateway part, I've been using a Wemos D1 R2 for some time and I was routinely finding myself in a similar situation where Domoticz decided that the gw was not connected anymore (though it was), and then all sensors started to (apparently) fall one by one because they failed to connect with Domoticz.
After some testing I started to have a feeling that somethig was not quite right in the gw itself but I wasn't able to identify what. I then started to replace parts of the hardware and am now using a NodeMCU v1.0. The setup seems significantly more robust and it hasn't lost connection to Domoticz for close to 3 weeks now (with the Wemos it happened every couple of weeks more or less).
What may be different between Wemos and NodeMCU that can cause this? Some firmware difference? No idea, but this is my result for the moment.
-
Irrespectively of the "interesting" design decisions on Domoticz (which I fully agree with), and the fact that almost every time a bug or improvement report is submitted the answers seems to be most frequently "please code it yourself", or even "that feature is already included in next beta" which then turns out to be just not true... even though it generally works quite well, some things are very annoying so I'm actually also starting to think on a move to openhab.
...back to the gateway part, I've been using a Wemos D1 R2 for some time and I was routinely finding myself in a similar situation where Domoticz decided that the gw was not connected anymore (though it was), and then all sensors started to (apparently) fall one by one because they failed to connect with Domoticz.
After some testing I started to have a feeling that somethig was not quite right in the gw itself but I wasn't able to identify what. I then started to replace parts of the hardware and am now using a NodeMCU v1.0. The setup seems significantly more robust and it hasn't lost connection to Domoticz for close to 3 weeks now (with the Wemos it happened every couple of weeks more or less).
What may be different between Wemos and NodeMCU that can cause this? Some firmware difference? No idea, but this is my result for the moment.
@manutremo did you buy a genuine wemos ? I've not had any problem with mine, I switched to wifi gateway a few months ago and it's been very stable. I had problems before with "NodeMCU" probably because of bad components used on the board I bought.
For Domoticz like many others here I'm going to leave it, for many annoying things like the 5mns minimum delay, this "last seen" things etc, and I also developed a severe allergy to virtual switches :D
-
@manutremo did you buy a genuine wemos ? I've not had any problem with mine, I switched to wifi gateway a few months ago and it's been very stable. I had problems before with "NodeMCU" probably because of bad components used on the board I bought.
For Domoticz like many others here I'm going to leave it, for many annoying things like the 5mns minimum delay, this "last seen" things etc, and I also developed a severe allergy to virtual switches :D
@Nca78 They are supposedly genuine, purchased in a reputable store. That doesn't discard however that some component is defective and goes unstable after a certain number of hours. Maybe both types of boards can work well, it's just a matter of (bad) luck with specific units.
-
Personally I'm using the last versions of both the arduino ide and the boards definitions. Also I would expect all of us would be seeing the same problem if that was the case, wouldn't we?
Not a big deal for me anyways, the only reason to select the wemos d1 r2 in my case is because I'm using an enclosure designed for the arduino uno which it fits perfectly... But no problem on switching to the nodemcu.
