• sweetpi

    @atus Good new: I was able to solve the Problem: We used a deprecated npm registry endpoint to get the package list (http://blog.npmjs.org/post/157615772423/deprecating-the-all-registry-endpoint). I migrated the plugin update script to a the new endpoint. Your plugin is now listed. Thanks for your patience.

    posted in Plugins read more
  • sweetpi

    Hi Fabian,

    I will investigate further. You said, that the error repeates? Does this happen after a user interaction with pimatic, (i.e. checking for updates) or without user interaction?

    The error typically mean, there is something wrong with our update server and not with your pimatic installation.

    posted in Troubleshooting read more
  • sweetpi

    I think I was able to fix the issue. The update server could not always receive the full package list from npm. This did result in an empty plugins list or an crash.

    The update server should now operate normally again.

    posted in Forum / Website read more
  • sweetpi

    I can’t find a problem related to the update server itself. It seems to be running fine.

    @wuschel, @johnny11, @incmve Could you check if you can browse to http://api.pimatic.org/plugins with your browser. This is the URL pimatic uses to get the plugin list.

    posted in Forum / Website read more
  • sweetpi

    It looks like requesting the values of the attributes of the devices used in the rule does hang until the webfrontend does request them.

    @macitemre could you post the full rule that is not working and all devices or device classes used in this rule?

    posted in Troubleshooting read more
  • sweetpi

    Hi @koffienl,

    I’m fine, thanks. I’m reading the forum regularly, however I have currently not much time to reply. Some other project are keeping me busy and so I have to prioritize. I’m so happy that pimatic has grown so much and very talented and active people are helping here and contribute to the source code.

    pimatic was build as an open community project from the beginning. I was the main contributor in the beginning, however now I more do some background managing tasks and keep the infrastructure running.

    posted in General Discussion read more
  • sweetpi

    Thanks for the notice. It is now up again. The watchdog script didn’t work and the server provider did reboot the server without notice…

    posted in Forum / Website read more
  • sweetpi

    The contact attribute was accidentally added to the config by the autodiscover function. This should be fixed in the new pimatic-homeduino version 0.9.9.

    posted in pimatic v0.9 read more
  • sweetpi

    There can be multiple reasons for missing signals:

    1. Maybe tow device send at the same time and so the signals conflict with each other. This is a general problem with RF on the them frequency and not solvable without resend and acknowledgment.
    2. To detect and decode an rf package, the pulse sequence must be repeated at least 3 times: First to find the header pulse, second to record and third to verify. So if on sequence gets noised, the detection will fail.
    3. If the receive buffer of rfcontrol is full, it can’t receive new signals.

    If you are able to capture a non detected pulse sequence, you can test why it is not detected by RFControl, by doing a simulation: https://github.com/pimatic/RFControl/blob/master/simulate/simulate.cpp

    Maybe there is really a bug in RFControl. If you find a way of handling one of the issue above let me know. I’m happy about contribution.

    posted in Hardware read more

Looks like your connection to pimatic forum was lost, please wait while we try to reconnect.