[1]: https://www.netatmo.com/en-gb/helpcenter/air-care/4/installa...
558 karma · joined February 9, 2014
[1]: https://www.netatmo.com/en-gb/helpcenter/air-care/4/installa...
Given the cost of the device I would be amazed if it wasn't a VOC based sensor. The cheapest CO2 sensors I've seen are well over $250, even in bulk. CO2 is quite innert, so it requires very precise and accurate components
What really kicked this all off was the javascript testing functionality in other projects which we found to be nearly unusable in more complex tests where say, you want to verify the contents of a JWT. We liked the ability to write simple tests quickly, but needed more power to be able to extend when needed - that's why we wrote the ability to hook in to python functions with Tavern as required.
We're just getting started with tavern and the next things on our agenda are: 1) Reference schemas from Json schema or OpenAPI documents 2) Command line deamon to ping your API regularly for functional uptime monitoring
We'd really love to know what you think - either in the comments or github issues!
I guess in these cases it's quite difficult, since it's likely not feasible to update the locations of individual bikes for these guys. I've checked their map and Bristol, UK doesn't appear to show YoBike at the moment, however it's only been in action for a few weeks.
Personally I used it to combine generating mail merged print and laser cut patterns for the place cards. So you get a pdf to print out and a laser cutting SVG which can be 'lasered on' after the printing.
Where are they still used at 'scale'?
W.r.t. having a set of trusted nodes, that's fine, however does the blockchain add anything in this situation?
A low carbon successor to concrete could change this if its low carbon and not so dense that it's difficult to transport (like concrete)
I've been using Papier as a daily todo list and found it's helped me not get distracted by having social media on the new tab page.
I'd suggest as others have that a fresh install is better!
Perhaps they do only use visual feedback for determining the state, which would be a better demo, but I doubt anyone would be able know from that article!
How do you plan to handle the selenium replaying? Does it currently just record the x/y position of the cursor events, because if so I guess it needs playback on a browser window of the same dimensions.
I guess it may be possible to have some adaptors for cursor events which can process the clicked element for a framework, i.e. for reactJS it could pick out the classname and use that as the click target for playback in a screen size independent way.
My gut instinct was that this would mean lots of re-recording tests every time you make a change - but really that's much the case with screenshot testing or any e2e testing already! Great work!
In the case of a true eSIM, there is no sim card at all, it's stored on the device it's self with a lower level bootstraping profile (i.e. not an alternative pre-programmed carrier)
The GSMA and members (i.e. telcos) have been working on secure remote provisioning. I think it'll take a while for the technology to make it in to consumer devices, though it's likely to be used in IoT relatively soon.
It takes a long time to spec these things up collaboratively and then even longer for telco's to act on it!
See: http://www.gsma.com/rsp/2016/04/27/esim-opportunity-operator... and http://www.gsma.com/rsp/ (Warning: Lots of marketing BS)
It does need a touch more work to allow re-usable fragments in get arguments and a couple of other areas, but it's certainly good enough for documenting and basic testing. There's still active development from apiary as far as I can tell and the MSOn syntax is really simple to become productive with.
My team and I spent a few weeks working with Azure IoT before instigating a switch to an alternative.
The problem with Azure IoT as a platform is that they provide SDK documentation (which is relatively good for languages they like), but not API documentation for the AMQP interface which is their preferred method of connecting devices. Their support for python clients and servers (in particular servers) left me and my team spending circa 10 days digging through AMQP logs and wireshark in ever more desperate attempts to integrate our existing python server with Azure IoT. Eventually it became clear that our only option was to wrap the C library for a really brittle integration and that we could switch to a different platform with far less effort! Both Amazon IoT and Watson IoT have been far smoother to integrate with since they provide both SDK and API docs!
The tough thing about it is that on the surface it looks as though it's really well documented and it's not until you hit your first big problem that you start looking around for API docs to try and debug what exactly it is that's wrong!
Currently really fond of Watson IoT for the decent python SDK's (we've only got 2-3 patches in a fork!) and the really handy device management features which can make rebooting etc much easier from the server side. The MQTT implementation they've worked on is great too.
Idea: proper graphics for data/image/video display.
I think it's an interesting idea that a terminal editor can have text only input, but the ability to draw real high-res graphical output. e.g. a canvas to draw your matplotlib diagram in the terminal output or a more graphical version of htop (with time data graphs etc).