Connecting Fibaro Wall Plug crashes SmartHome

[Bergman]

Hello,

My problem is that when I connect my Fibaro Wall Plug to, well anything, the entire SmartHome server becomes inaccessible. My browser does not outright tell me that it cant be accessed, but it takes forever to load and does not really give me any more information.

The only other device connected to my Raspberry Pi running the SmartHome server is a Fibaro Door/Window sensor. Both the devices are set up with Sensor Value Logging, and I have noticed some strange behavior from the Wall Plug in that it does not always log values every second, but sometimes it logs multiple values the same second. I am not sure if this has anything to do with my original problem.

How would I go about solving this?

Best regards,
Anton

[DomotikQuebec]

I think you should not pool devices once a second.... this is way too fast.

Also, you must know, that most device automatically send changes to the network controller... may be not every devices, but most of them.

Your "every second pooling" is a torture for the z-wave network. Just don't !

You must consider the pooling as a way to update values that don't change often.

If you can keep an eye on the log file, you will feel like there is some fight going on the matrix (like in "the matrix" movie)

the fact that you now have two devices to pool instead of one may jam everything.

Hope it helps and let me know what you've done.

By the way, I did the same thing at the beginning

[Bergman]

I think you should not pool devices once a second.... this is way too fast.

Also, you must know, that most device automatically send changes to the network controller... may be not every devices, but most of them.

Your "every second pooling" is a torture for the z-wave network. Just don't !

You must consider the pooling as a way to update values that don't change often.

If you can keep an eye on the log file, you will feel like there is some fight going on the matrix (like in "the matrix" movie)

the fact that you now have two devices to pool instead of one may jam everything.

Hope it helps and let me know what you've done.

By the way, I did the same thing at the beginning

Ok I see! Thanks you very much!

Another question in the same spirit: I am trying to read the .json files generated by Sensor Values Logging approximately once every hour using an automated Python script and send this data to a database. When this is done, I want to delete the content of the file to stop the logging from using too much hard disk space.

Once in a while, the file will just re-create itself with all previous values when I am trying to delete it, which gives me problem with the database.

Is there a way to avoid this behavior?

[pz1]

Another question in the same spirit: I am trying to read the .json files generated by Sensor Values Logging approximately once every hour using an automated Python script and send this data to a database. When this is done, I want to delete the content of the file to stop the logging from using too much hard disk space.

In the App store there is an App from Maros Kollar:

Collect stats via InfluxDb
Store sensor data and Zwave Network data in InfluxDB instances. InfluxDB is a time series database that can be used for storing and analyzing measurements and statistics over time. You need an external InfluxDB instance to operate this module.
Check github.com/maros/Zway-InfluxDbStats for detailed documentation.

[DomotikQuebec]

Just to add more information to this situation.
I just added a Multi Sensor in security mode while looking at the log file...
The interview lasts 13 seconds. So, trying to pool, at least 13 times, during this process....