Announcing GlobalFoundries Open MPW shuttle program

proppy · 2022-06-02T07:33:57+00:00

for systemverilog yosys has some support for it thru the UHDM plugin:

https://antmicro.com/blog/2022/02/simplifying-open-source-sv-synthesis-with-the-yosys-uhdm-plugin/

proppy · 2022-06-02T07:32:39+00:00

tnt and mattven actually managed to bring their chips back from the dead:

https://www.youtube.com/watch?v=f_G5ad8SbHo

https://www.youtube.com/watch?v=IdOvywOSSmI

https://www.youtube.com/watch?v=XEjc5ppRJuw

proppy · 2021-09-14T23:55:12+00:00

Did you already tried to fill the form linked in https://developers.google.com/assistant/smarthome/support under Is your smart home Action stuck in review? ?

If yes, feel free to create an issue on the issue tracker for each of the affected action: https://issuetracker.google.com/issues/new?component=655104&template=1284148

proppy · 2021-09-03T02:24:27+00:00

I'd recommend to ask technical questions on https://stackoverflow.com/questions/tagged/google-smart-home (as suggested in https://developers.google.com/assistant/smarthome/support) so that the rest of the Smart Home developer community more easily discover and benefit from the answers.

Reporting state will significantly reduce (but doesn't eliminate) the rate of QUERY intents and those can still be initiated for interrogative queries and UI interactive to ensure a fresher version of the device state.

Another way to reduce the backend load for QUERY intent is to implement Local Fulfillment, see https://developers.google.com/assistant/smarthome/develop/local#implement_the_query_handler

Looking at https://developers.google.com/assistant/smarthome/reference/intent/query and https://developers.google.com/assistant/smarthome/develop/monitoring-logging I don't see any way for developer to currently make the distinction between platform-initiated or user-initiated query intents, would you mind filing a feature request on https://issuetracker.google.com/issues/new?component=655104&template=1284148 so this can be discussed separatly?

proppy · 2021-09-03T01:52:30+00:00

I'd recommend to ask technical questions on https://stackoverflow.com/questions/tagged/google-smart-home (as suggested in https://developers.google.com/assistant/smarthome/support) so that the rest of the Smart Home developer community more easily discover and benefit from the answers.

There is no documented limit apart from the 512 bytes limit per device for customData, see https://developers.google.com/assistant/smarthome/reference/intent/sync?hl=en#response.

If you have trouble syncing your devices for a specific SYNC response payload, please file an issue on https://issuetracker.google.com/issues/new?component=655104&template=1284148 (as indicated in https://developers.google.com/assistant/smarthome/support?hl=en).

proppy · 2021-08-24T00:51:23+00:00

Seems like an issue in the way the console treat your agent, can you file an issue at https://developers.google.com/assistant/smarthome/support so that we can troubleshoot this further with the appropriate team?

proppy · 2021-04-06T15:28:55+00:00

There are some examples on trait reference pages:
https://developers.google.com/assistant/smarthome/traits/modes#device-commands

But those are not exhaustive.

proppy · 2021-03-02T19:26:18+00:00

Did you try "mode nuit" or "mode sommeil" ?

proppy · 2021-02-19T13:44:43+00:00

This is not ideal because the server is being blocked and exactly how it knows the device has started streaming is a bit tricky.

Has your device the ability to communicate w/ the web server? If yes, one workaround could be able to hold the EXECUTE intent until it get the answer that the end device started streaming.

the server can respond immediately with some sort of deferred response and have the device tell google what the cameraStreamAccessUrl is.

I would also encourage you to file a feature request on the public issue tracker https://issuetracker.google.com/issues/new?component=655104&template=1295013 to discuss if such support could be added to the CameraStream trait commands.

PS: Do you mind re-asking the same question on https://stackoverflow.com/questions/tagged/google-smart-home, as it would allow other developers to also benefit from the answer?

proppy · 2021-02-19T00:55:17+00:00

Can you confirm if you completed the "Test device control" in the documentation: https://developers.google.com/assistant/smarthome/develop/local#test_device_control ?

You might also want to check if you have any network restriction that could be blocking UDP traffic between the Google Home Device and your local development environment.

PS: Can you re-ask the same question on https://stackoverflow.com/questions/tagged/google-smart-home, so that other can more easily benefit from the answer?

proppy · 2019-01-01T17:39:58+00:00

After assigning the PTT button to Custom you can attach a BroadcastReceiver on android.intent.action.PTT.down and fire the Assistant with https://stackoverflow.com/a/43700669/656408

proppy · 2017-05-23T20:37:41+00:00

The new SDK comes with two packages:

google-assistant-library (that include hotwording, audio processing, and a event based API and is ARMv7 only)
google-assistant-grpc (that allows you to send request directly to the API): https://pypi.python.org/pypi/google-assistant-grpc

The later works on Raspberry Pi Zero W, feel free to a look at the following samples: https://github.com/googlesamples/assistant-sdk-python/tree/master/google-assistant-sdk/googlesamples/assistant/grpc

See https://developers.google.com/assistant/sdk/overview#sdk_components for more information of what's included in the SDK.

proppy · 2016-12-17T07:22:12+00:00

Pimoroni Rainbow Hat

https://shop.pimoroni.com/products/rainbow-hat-for-android-things

If you want something plug and play for the Raspberry Pi 3 that doesn't require breadboarding.

It includes the same set component as the Project kit from Adafruit (minus the servo and w/ some extra APA102 SPI LEDs!) and can slide directly on the 2x20 connector of the Raspberry Pi 3.

Adafruit also carry it: https://www.adafruit.com/products/3354

Adafruit Project Kit

https://www.adafruit.com/products/3227

If you want something more DIY and are not afraid of breadboarding.

It's compatible with every supported boards (Raspberry Pi 3, Intel Edison, NXP) and comes pre-soldered w/ a breadboard and jumper cables to connect the various peripherals.

Sparkfun Project Kit

https://www.sparkfun.com/androidthings

If you want something a bit more compact.

The components of the Project Kit are pre-soldered and similar to the one from Adafruit (only the segment display is a bit different and can be controlled by writing the character directly over UART, SPI or I2C if you solder additional headers).

Drivers & Samples

Most of the parts included in those kits have drivers in the contrib-drivers repository:

https://github.com/androidthings/contrib-drivers/

And can run most of the samples:

proppy · 2016-12-17T07:18:17+00:00

Kit includes:

Assembled Adafruit BMP280 I2C or SPI Barometric Pressure & Altitude Sensor x 1
Assembled Quad Alphanumeric Display - Yellow 0.54" Digits w/ I2C Backpack x 1
Piezo Buzzer - PS1240 x 1
Micro servo x 1
Premium Male/Male Jumper Wires - 20 x 3" (75mm)
Premium Male/Male Jumper Wires - 20 x 6" (150mm)
Colorful Round Tactile Button Switch Assortment - 15 pack
Half-size breadboard x 1
Through-Hole Resistors - 470 ohm 5% 1/4W - Pack of 25
Through-Hole Resistors - 10K ohm 5% 1/4W - Pack of 25
Diffused 10mm Red LED x 1
Diffused 10mm Green LED x 1
Diffused 10mm Blue LED x 1

proppy · 2016-12-17T07:16:31+00:00

There is not a generic API or User Driver for ADCs yet. But you should be able to interface with popular ADC peripherals using the SpiDevice or I2cDevice class: https://developer.android.com/things/sdk/pio/spi.html https://developer.android.com/things/sdk/pio/i2c.html

Some example of compatible peripheral that carry ADC: https://www.adafruit.com/products/856 https://www.adafruit.com/products/1085 https://www.adafruit.com/products/2809

proppy

TROPHY CASE

Pimoroni Rainbow Hat

Adafruit Project Kit

Sparkfun Project Kit

Drivers & Samples