Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Search the Community

Showing results for tags 'Freeze'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Facebook


Google+


Skype


Website URL


WhatsApp


Country


Gateway/s


Interests

Found 8 results

  1. Hi all, I see that some users have downloaded Z-wave monitor script and I think it could be a good idea to share our data and know-how to optimize our Z-wave performance. In my case I have manage to reduce Z-wave traffic from average of event per 1.7 sec. to 4.8 sec (24 hours monitoring, 78 physical devices, 382 IDs), but I don't know if this is a good number. It will be interesting if anyone could share an average of his system. That way we can compare and might be to achieve the right number and stable performance which may be could prevent Z-wave freeze in the future. I think average of Z-wave traffic somehow depends on number of the devices in the system and again I believe we need team work to find correct formula for that. Few users have shared with me that they have found devices, which "bombarding" the traffic with unnecessary reports and they fixed the issue. It could be very helpful to all of us to share our solutions and fixes... we all can learn from others If you think it could violate your privacy, please ignore this message... Thank you
  2. I have installed my Intercom with access from a couple of iPads. After testing the opening of a gate with a code (which worked), the intercom started blinking red (5 digits alternating) and stopped being accessible by my iOS devices. Either local or cloud access has become impossible. It seems also that the Intercom has totally disconnected from the network (I had given a static IP which is no longer seen by my router), restarting the router did not help. What happened and what can I do? It cannot be that the Intercom would stop working all of a sudden and that the only way forward would be to reset everything!
  3. Intercom freezes once in a while - runs fine for several days and then stops spontaneously communicating, however is still reachable over app. No more rings/calls broadcasted. After a reboot over app intercom works fine again - however leads to missed calls at the door which is annoying - Unreliable performance is difficult especially when away. Intercom is hardwired with PoE. Anyone same experience or solution? Thank you Pfirry
  4. Winter has gone and 30 degrees are back in town so time ago I stopped all scenes that control the heating system in the house. We are talking about 16 scenes changed from automatic to manual, but I did not stop the automatic daily restart scene. Immediately after that, the used RAM dropped from 99% to 80%. Now, looking at the RAM usage I can read numbers between 96 and 99% without implementing anything new. Yes it eats RAM, a lot, not known why, not possible to do anything about that. I read that people with FW 4.130 are less happy then 4.120 or 4.110 or xxxxx. Guys nothing changed, it's always the same story. Don't think that a new FW is totally rewritten from zero every time and in the correct way, it is just a bunch of extra coding squeezed inside the other rows of code. Hardware remains the same. Issues remain the same. Sad but true (cit.)
  5. Like many others here, I'm frequently plagued by periodic crashes and 503 errors. In my case, I noticed that the memory usage would increase dramatically, to the point where scenes would no longer run, and the web interface wouldn't respond. Only a restart would fix it. I traced it to what I can only think is a memory leak, and I have a suspicion that it's related to the Heating/Cooling Panels. It might be fine for a while, and then for a week or so, I'll get the memory leak problem occur again. I can't be 100% sure, but I'm coming to conclusion that this happens after I've updated the Heating Panel. So I wrote this scene to monitor the memory usage and to automatically reboot the HC2 if the usage exceeds a specified value. I also have it writing the memory usage values off to AllThingsTalk, so that I can see the history, like this: For more details of AllThingsTalk, then see this post: Topic 21656 (Recording Data to AllThingsTalk.IO) Disclaimer: Only use this scene if your system is generally stable but occasionally has a memory problem, otherwise you might send your system into a continuous reboot loop. Please use this scene at your own risk. Only use it if you know what you are doing. Memory Monitor.lua --[[ %% properties %% events %% globals fiveMinuteTimer --]] -- Scene : Memory Monitor -- Version : 1.6 -- Date Created : 16 May 2016 -- Last Changed : 16 May 2017 -- HC Version : Home Center 2 v4.080 -- Created By : Dave Harrison -- Purpose : To keep an eye on the memory usage. -- : When it increases beyond a certain limit, then send a message and reboot the machine. -- : Record data to allthingstalk.io -- Trigger : Triggered by the fiveMinuteTimer global variable --================================================= -------- Declaration: Local Variables --================================================= local debug = true local sourceTrigger = fibaro:getSourceTrigger() local currentDateISO = os.date("!%Y-%m-%dT%XZ") local memoryUsedLimit = 70 local notificationDevice = 266 -- Change this to the mobile device number to send the notification to local allThingsTalkClientID = "xxxxxxxx" -- Change this to your AllThingsTalk ClientID local allThingsTalkClientKey = "yyyyyyyyy" -- Change this to your AllThingsTalk ClientKey local allThingsTalkAssetId = "789b2783e3dfe27040c84833" -- Change this to the Id of the AllThingsTalk Asset that is being used to record the usage --================================================= -------- Functions --================================================= local function log(str) if debug then fibaro:debug(str); end; end local function errorlog(str) fibaro:debug("<font color='red'>"..str.."</font>"); end local function processResponse(response) local memory = response.memory if (memory ~= nil) then local memoryFree = memory.free local memoryCache = memory.cache local memoryBuffers = memory.buffers local memoryUsed = memory.used local memoryTotalUsed = 100 - memoryFree -- Send the memory utilisation to AllThingsTalk local requestData = {value = memoryTotalUsed, at = currentDateISO} local requestBody = json.encode(requestData) sendData(allThingsTalkAssetId, requestBody) if (memoryTotalUsed > memoryUsedLimit) then fibaro:call(notificationDevice, "sendPush", "HC2 memory utilisation is " .. memoryTotalUsed .. "%") errorlog("Memory utilisation is too high: " .. memoryTotalUsed .. "%") -- Reboot the HC2 HomeCenter.SystemService.reboot() else log("Free memory is: " .. memoryFree .. "% Cache: " .. memoryCache .. "% Buffers: " .. memoryBuffers .. "% Used: " .. memoryUsed .. "% Total Used: " .. memoryTotalUsed .. "%") end else errorlog("Memory usage not found in diagnostics API") end end local function processError() errorlog("Error calling diagnostics API") end function sendData (assetId, requestBody) local url = "https://api.allthingstalk.io/asset/" .. assetId .. "/state" local httpClient = net.HTTPClient({timeout=5000}) local httpHeaders = { ["Auth-ClientId"] = allThingsTalkClientID, ["Auth-ClientKey"] = allThingsTalkClientKey, ["Content-Type"] = "application/json", } httpClient:request(url, { options={ headers = httpHeaders, data = requestBody, method = 'PUT', timeout = 5000 }, success = function(response) if (response.status >= 200 and response.status < 300) then log(assetId .. ": " .. response.status .. " - successful") else errorlog(assetId .. ": " .. response.status .. " - ERROR") end end, error = function(error) errorlog(assetId .. ": " .. "ERROR") log(error) end }) end --================================================= -------- Main --================================================= -- Get the memory and CPU usage information response, returnCode = api.get("/diagnostics") if (response ~= nil and returnCode == 200) then processResponse(response) else processError() end If you don't want to mess around with setting up AllThingsTalk, then here is a second version without this functionality: --[[ %% properties %% events %% globals fiveMinuteTimer --]] -- Scene : Memory Monitor -- Version : 1.6 -- Date Created : 16 May 2016 -- Last Changed : 16 May 2017 -- HC Version : Home Center 2 v4.080 -- Created By : Dave Harrison -- Purpose : To keep an eye on the memory usage. -- : When it increases beyond a certain limit, then send a message and reboot the machine. -- Trigger : Triggered by the fiveMinuteTimer global variable --================================================= -------- Declaration: Local Variables --================================================= local debug = true local sourceTrigger = fibaro:getSourceTrigger() local currentDateISO = os.date("!%Y-%m-%dT%XZ") local memoryUsedLimit = 70 local notificationDevice = 266 -- Change this to the mobile device number to send the notification to --================================================= -------- Functions --================================================= local function log(str) if debug then fibaro:debug(str); end; end local function errorlog(str) fibaro:debug("<font color='red'>"..str.."</font>"); end local function processResponse(response) local memory = response.memory if (memory ~= nil) then local memoryFree = memory.free local memoryCache = memory.cache local memoryBuffers = memory.buffers local memoryUsed = memory.used local memoryTotalUsed = 100 - memoryFree -- Send the memory utilisation to AllThingsTalk local requestData = {value = memoryTotalUsed, at = currentDateISO} local requestBody = json.encode(requestData) if (memoryTotalUsed > memoryUsedLimit) then fibaro:call(notificationDevice, "sendPush", "HC2 memory utilisation is " .. memoryTotalUsed .. "%") errorlog("Memory utilisation is too high: " .. memoryTotalUsed .. "%") -- Reboot the HC2 HomeCenter.SystemService.reboot() else log("Free memory is: " .. memoryFree .. "% Cache: " .. memoryCache .. "% Buffers: " .. memoryBuffers .. "% Used: " .. memoryUsed .. "% Total Used: " .. memoryTotalUsed .. "%") end else errorlog("Memory usage not found in diagnostics API") end end local function processError() errorlog("Error calling diagnostics API") end --================================================= -------- Main --================================================= -- Get the memory and CPU usage information response, returnCode = api.get("/diagnostics") if (response ~= nil and returnCode == 200) then processResponse(response) else processError() end The scene is triggered every 5 minutes by a global variable. See Topic 24789 (Simple Timer/Scheduling Scene) or Topic 23510 (Main Scene for Time Based Events Control) for examples of how use a timer global variable. The scene is currently set to reboot when the memory usage exceeds 70%. There is still the possibility that if the memory usage is increasing at a very high rate, then the HC2 will crash before the scene next runs. So setting it to 70% seems to be low enough to catch most instances. Do not set this to a low value otherwise your HC2 might go into a continuous reboot loop. Take a look at your normal RAM usage in the Diagnostics Panel and use a value higher than this. You will need to change the line of code that specifies the Mobile Device Id which should receive the notification message when the memory limit is exceeded. You can find the device id from the API. Enter the following URL into a browser: http://<HC2 IP Address>/api/iosDevices This will return a list of the mobile devices and you can select the appropriate one. You'll also need to assign the correct values to the AllThingsTalk ClientID, ClientKey and AssetId if you're using the first version of the scene. You can get all these values from the Maker pages of AllThingsTalk.com.
  6. An option to to filter spikes of degree changes would be ideal. Sometimes the sensor are not very accurate for a short of period, like this screen-shot. Ideally the system need to verify the degree or wait for X second before it sends notifications.
  7. Hi Excuse my google english, and for the long post. Since upgrading from 3.6x to 4.0xx HCL has max running for four days without rebooting. I have been using automatic restart (about every 3 days) for more than a year. After ver. 4.082 was worse, being 78% "used space" of 3 days. Throughout the summer, with only 12 active scenes of 47 https://forum.fibaro.com/index.php?/topic/22084-experiences-from-hcl-4090/&do=findComment&comment=95287 Fibaro developers have had access to HCL from d. August 24 to d. Sept. 9 When Fibaro have access see graph like this. 27th August necessity restart about 78% "used space". 30th august HCL freeze, then restart. Fibaro support, d. 9 September. I have got reply from software team that they need to prepare proper fixes and include them to next software versions, but at present they weren’t able to fix your system. Anyway we are very thankful for this shared connection, because we have found more information about possible causes of this issue. Fibaro have probably not noticed that HCL has stopped eating ram d. August 30. On all scenes d. 6-7-8 September. Now 47 active scenes. Which 10 with the "Running instances: 1" and 37 scenes (Running instances 0). HCL running yet, since restart d. August 30. HCL is now 100% stable. When Fibaro's software team writes "but at present they weren’t able to fix your system" so they have probably not changed anything about my HCL. The system is not yet fully proven, but that HCL can now run with 47 scenes completely stable, from before with 12 scenes and only in 3 days. It speaks for itself. Why is HCL then become stable? In my frustration (just to do something), I removed all the checkmarks in the "Associations - group - Single channel associations" except the last group, in all my devices. Maybe someone out there on the forum who know what significance it has. See answers from Fibaro support. http://forum.fibaro.com/index.php?/topic/22433-associations/?p=97577 Summary: Fibaro have now had remote access for 6 days and HCL have gone down 2 times during the period. The last restart I have done in a different way (again in my frustration) to try something I have not tried before. Like some laptobs will not start. Pull the power plug out of the HCL box. Wait at least 20 seconds. Hold the power button for about 7 seconds, release the power button. Hold the + button for about 7 seconds, release the + button. Hold both buttons for about 7 seconds, release both buttons. I forgot it, so there was enough four hours before I put the power cord back. Have you seen what HCL doing when we sleep. (Every night at. 00:00)
  8. Hi We recived a batch of brand new HCL yesterday and we wanted to add an Aeotec micro motor controller to our system, sadly this wasn't possible. The HCL is running under 4.044 we added a door sensor a double switch realy and made a scene, working all right so far, but when we tried to add the motor controller clickcing the ID button the system recognize the device but then stall on the device configuration process. We have been using this devices with HC2 working fine the up, down, pause commands (the slider to set the blinds control no so well), so we are going nuts to find what may be causing this. We have reseted the HCL Several times trying diferent approaches, but with no luck we always end in the repair website for the HCL Any comments are welcomed. Gracias
×
×
  • Create New...