14f1c44378
- If a Z-Wave event includes an explicit value update then explicitly set that value on the node, in order to prevent issues with Z-Wave value updates not yet propagated to the node structure
...
- Added Z-Wave switch component
2021-03-16 20:52:30 +01:00
fdd46edb6a
Do not force type cohercion on bool values - !!parseInt(true) = false in JavaScript, for some reason
2021-03-16 20:11:49 +01:00
b9738d88df
Added some temporary debug lines to Z-Wave's Value.vue to investigate setValue issues
2021-03-16 20:00:25 +01:00
f92d19a24e
media.vlc.stop should be synchronized on the _stop_lock and should call _reset_state instead of simply setting self._player = None
2021-03-16 19:42:59 +01:00
ce0ca2e9ee
Explicitly pass the new value on the Z-Wave setValue handler in case of binary toggles, since the target element can't be reliably determined
2021-03-16 19:37:42 +01:00
7f157d0234
Dockerfile should be part of the examples/ folder
2021-03-16 00:29:52 +01:00
8a3df30001
Removed Travis-CI and ReadTheDocs integrations (replaced by Platypush CI hooks)
2021-03-16 00:28:25 +01:00
82274d3d12
Added updated reference to CONTRIBUTING.md in README
2021-03-16 00:20:21 +01:00
ab6c85c2a6
Updated CHANGELOG
2021-03-16 00:17:20 +01:00
f8564c19cd
Added log.http backend to monitor HTTP logs [ closes #167 ]
2021-03-16 00:03:32 +01:00
bf519babb0
Updated tests and docs build badges
2021-03-14 17:35:25 +01:00
632a7ab792
Added README for auto-generated docs and changed theme to sphinx-material
2021-03-14 15:07:10 +01:00
1d3d741212
Fixed Sphinx build warnings
2021-03-14 01:09:01 +01:00
b171cb1012
A click on a Z-Wave binary event should result in the value being toggled, not rewritten [see #176 ]
2021-03-14 01:05:02 +01:00
352d421e61
Added file.monitor backend [ closes #172 ]
...
The file.monitor backend leverages watchdog instead of the Linux-only
inotify API and it replaces the inotify backend.
2021-03-14 00:08:20 +01:00
6f224cbda9
Removed legacy "local" backend and pusher script
2021-03-13 01:52:15 +01:00
adb472da7f
Messages should always be posted to the Redis bus in valid JSON format - no need for ast.literal_eval fallback
2021-03-13 01:52:15 +01:00
Fabio Manganiello
347a4d2555
disable_logging=True for ZwaveNodeGroupEvent
2021-03-12 20:29:26 +01:00
cef310ffd7
Added missing methods docs
2021-03-12 01:53:16 +01:00
96588df83b
Bump version: 0.20.4 → 0.20.5
2021-03-12 01:40:03 +01:00
02f6845e72
- Added weather.openweathermap plugin and backend, as a replacement for Darksky [ closes #177 ]
...
- Added note to the Darksky plugin about the decomissioning of the API by the end of the year
2021-03-12 01:31:26 +01:00
40834f7ce5
The zigbee2mqtt backend should use a suffix for the default client_id to prevent clashes with the default client_id from the MQTT backend [see #175 ]
2021-03-11 19:24:13 +01:00
3d6af00ee6
Disable logging of ZwaveValueEvent objects, as they tend to be very verbose
2021-03-11 17:53:39 +01:00
b06867dc5d
Added CONTRIBUTING file
2021-03-11 01:50:24 +01:00
22dad79dd5
Merge pull request #166 from BlackLight/dependabot/npm_and_yarn/platypush/backend/http/webapp/elliptic-6.5.4
...
Bump elliptic from 6.5.3 to 6.5.4 in /platypush/backend/http/webapp
2021-03-10 11:38:07 +01:00
211025cedb
The redis_queue parameter is not necessarily defined on the app config
2021-03-10 11:15:06 +01:00
dependabot[bot]
da27ed7546
Bump elliptic from 6.5.3 to 6.5.4 in /platypush/backend/http/webapp
...
Bumps [elliptic](https://github.com/indutny/elliptic ) from 6.5.3 to 6.5.4.
- [Release notes](https://github.com/indutny/elliptic/releases )
- [Commits](https://github.com/indutny/elliptic/compare/v6.5.3...v6.5.4 )
Signed-off-by: dependabot[bot] <support@github.com>
2021-03-10 10:00:42 +00:00
775478fff0
Improvement management of Z-Wave value types from the web panel
2021-03-10 10:58:51 +01:00
093bac3a60
- Addressed comments in #174
...
- Replaced active_scan flag with a list of track_devices
2021-03-09 19:03:04 +01:00
b3606a8ac3
Changelog edit
2021-03-09 12:54:43 +01:00
4902475caf
Added active_scan mode to bluetooth.scanner backend to actively perform a lookup name on each device discovered at least once [see #174 ]
2021-03-09 11:50:59 +01:00
7687e52058
Added cron examples to README.md
2021-03-09 01:43:28 +01:00
eae4b4f62a
The tmp_file fixture destructor should clean up any temporary files (in case multiple tests import it)
2021-03-09 00:22:18 +01:00
296458ece3
Cron expressions should follow the machine local time, not UTC [ closes #173 ]
2021-03-09 00:18:33 +01:00
71af6e87e0
Bump version: 0.20.3 → 0.20.4
2021-03-08 01:51:39 +01:00
c659ec507f
Added tests/__main__.py entry point to run all the tests
2021-03-06 20:13:38 +01:00
fb1953ce34
Using tests status badge from ci.platypush.tech on README instead of the Travis-CI status badge
2021-03-06 20:04:58 +01:00
34a108bbcb
Clear log objects on teardown to prevent pytest logging errors
2021-03-06 20:02:25 +01:00
5be6ca50f0
Travis-CI pipeline migrated to pytest
2021-03-06 19:50:22 +01:00
090e7d6de8
Support for specifying the application Redis queue from the command line or service constructor
2021-03-06 19:22:13 +01:00
6f85318868
Use another Redis queue for the test app to prevent clashes with another Platypush service running on the same machine
2021-03-06 17:17:55 +01:00
8f256e4077
Check for file creation and content multiple times with timeout
2021-03-06 17:09:40 +01:00
4ed80a0945
More tests improvements
2021-03-06 17:03:50 +01:00
ca90060ba1
Tests improvements
2021-03-06 16:25:37 +01:00
49ad3261f1
Refactored tests to use pytest with fixtures instead of unittest.TestCase
2021-03-06 16:21:28 +01:00
73e16fa6b1
Updated web app files
2021-03-05 21:43:16 +01:00
d860d8aef1
Added SmartThings switch web plugin
2021-03-05 21:29:32 +01:00
Fabio Manganiello
36aee6f787
The same applies to procedures - don't dump context as a JSON in case of exceptions
2021-03-05 19:00:26 +01:00
Fabio Manganiello
04ff008800
Context shouldn't be dumped as json in case of exceptions - if some objects are not JSON serializable then we end up with an uncaught exception
2021-03-05 18:52:57 +01:00
Fabio Manganiello
47ba13d985
calendar.ical.get_upcoming_events should fail hard if there was any exception/unsuccessful response
...
The error should not be swallowed and it should be instead propagated up
to calendar.get_upcoming_events, if it's called from that context. And
calendar.get_upcoming_events should be in charge of handling the
exceptions and make sure that failing to retrieve the events for one
calendar doesn't make the whole method fail.
2021-03-05 11:16:14 +01:00
