text:
simulation,validation,speedup

speeding up simulation and a bunch of scripts for validation scans with many reuse factors
https://indico.cern.ch/event/823156/contributions/3442008/attachments/1850883/3038435/fastml_simulation.pdf

We have a working branch here:
https://github.com/hls-fpga-machine-learning/hls4ml/tree/gdg/validation
I discussed with @vloncar  and he suggested few changes that I totally agree with and I will integrate soon on the branch.

We have a consolidated validation flow. The basic idea is to generate two log files with the predictions after both the C simulation (csim_design) and the RTL co-simulation (cosim_design), respectively. These two files are then compared. Any difference is a symptom of a wrongly generated RTL implementation and must by investigated (maybe a too aggressive HLS configuration, etc.).
There are two implementations of this validation approach:

The C/C++ testbench performs the log comparison (with an OS-dependent diff call). I report this for the sake of completeness.
The TCL testbench performs the log comparison. This is neater and is the solution that @vloncar and I agreed on.

Few more notes:

The first implementation, which embeds the validation in C/C++, is what Xilinx proposes in various guides (for example at page 33 - Self-Checking Test Bench). The latest versions of the Vivado Suite made commands like diff available on Windows too.
For the second implementation, we were counting on the compilation flag __RTL_SIMULATION__ to distinguish between C and RTL simulation. This flag should be automatically added by Vivado HLS, but unfortunately, it seems only available for SystemC/RTL co-simulation. @vloncar suggested this workaround, but we hope in a future fix from Xilinx. See also this forum post.

The code on this branch also integrates the feature to load weights from files on simulation to avoid long compilation runs and to reduce the overall C-simulation and RTL-co-simulation times. In the master-branch implementation, the compilation of the headers which declare and define the weight and bias arrays could take a few hours in the case of large layers. In this branch implementation, we only declare those big arrays in the headers, we store the weights in TXT files, and we load the weights at the beginning of the simulation. To preserve the HLS flow (we need still need those weights/biases in the headers when ``, we use conditional macros to keep the weights in the headers when we run HLS (csynth_design).
At this point, we may be ready for a PR.

source: gharchive/issue

authors: GiuseppeDiGuglielmo nhanvtran

license_type: permissive

license_source: github-api


text:
Cards links

There should be an option to add a link to whole cards (not only to the text within the cards).
A lot of pages have cards, some with images and some without, that link to other pages. In those cases, the entiere card should be the link.
Example pages:
https://www.mammotome.com/patient-resources/
https://www.mammotome.com/news-media/
https://www.mammotome.com/product-support/
This could be achieved by adding another column to the cards block containing the link

That is already supported
https://main--mammotome--hlxsites.hlx.page/en/products/cards-test-wide-no-callout

authors: dzehnder smiroslav

repo: hlxsites/mammotome


text:
Feature/civ 659

Before creating a pull request make sure that:

[X] commit messages are meaningful and follow good commit message guidelines
[X] README and other documentation has been updated / added (if needed)
[X] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-659
Change description

civil-ccd-definition : Add required fields under ccd-definition/ComplexTypes/GeneralApplicationGAspec.json to be able to capture all individual details per screen. (done)
civil-ccd-definition : Add businessProcess (done)
civil-ccd-definition : Add a CallBackURLAboutToSubmitEvent for CaseEvent INITIATE_GENERAL_APPLICATION in UserEventsGAspec.json  (done)
civil-ccd-definition : Add a fields under ccd-definition/ComplexTypes/GeneralApplicationGAspec.json to indicate whether the parent claim is multiparty or not (done)

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

Closing this PR as the pull from old integration branch caused issue... Creating another branch and will create another PR

source: gharchive/pull-request

repo: hmcts/civil-ccd-definition

license: MIT


text:
DTSPO-13563 - Add script and add pipeline

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DTSPO-13563
Change description
Add script and add pipeline

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

Proof that multiple broken environments work:

repo: hmcts/dtspo-daily-monitoring


text:
FACT-1552 fixing fact frontend dependancies

JIRA link
https://tools.hmcts.net/jira/browse/FACT-1552
Change description
fixing up frontend
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Will be fixed under different PR.

authors: joshblackmoor justiceia

repo: hmcts/fact-frontend


text:
sdo changes

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the enable_keep_helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

no longer needed

repo: hmcts/prl-ccd-definitions


text:
updated config

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

closing as no longer required

authors: praneethhm priteshkr

repo: hmcts/prl-cos-api


text:
Feat(Product): Edit Product with TimeStamp

Description

Closes #88
Changes proposed
What were you told to do?

Develop an API endpoint to edit user product_name, price, description, and category and create a timestamp for updates.
What did you do?

The endpoint should be accessible at api/v1/products/{id}

The endpoint should accept HTTP PUT requests.

The endpoint should be secured to ensure that only authenticated users can edit products.

Proper authentication mechanisms (e.g., JWT, OAuth2) should be implemented.

Requests to the endpoint must include a valid authentication token in the Authorization header. Authorization: Bearer

Request Body:

{
  "name": "Updated Product Name",
  "price": 600.0,
  "description": "Updated Product Description",
  "category": "Updated Category"
}

Response:

On a successful update, the API should return a 200 OK status code.
The response body should contain the updated product details.

{
  "id": 1,
  "name": "Updated Product Name",
  "price": 600.0,
  "description": "Updated Product Description",
  "category": "New Category",
  "created_date": "2024-07-17T12:34:56Z",
  "updated_date": "2024-07-18T14:20:00Z"
}

Validation:
If any required field is missing or invalid, the API should return a 400 Bad Request status code with an appropriate validation error message.

{
 "status_code": 400,
  "message": ["product_name is required", "price must be a positive number"],
  "error": "Bad Request"
}

Check List (Check all the applicable boxes)
🚨Please review the contribution guideline for this repository.

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.
[x] I am making a pull request against the dev branch (left side).
[x] My commit messages styles matches our requested structure.
[x] My code additions will fail neither code linting checks nor unit test.
[x] I am only making changes to files I was requested to.

Screenshots/Videos

move validation logic to command handler then good to go


text:
Feat/ generate backup code

@

Doing


text:
Problems deploying Portworx

I tried to deploy portworx, but forgot to change the variables PX_STORAGE_SERVICE which was set to /dev/vdb instead of /dev/vda.
So I manually deleted the daemon_set and the storage class, and redeployed using kubectl apply -f storage.
However it seems that smth is broken as I end up with 3 pods in CrashLoopBackOff state.
Here is the log from one of the pod:
container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/var/lib/kubelet/pods/aad88e78-09c2-11e8-8395-de2b44396007/containers/portworx-storage-1/ccd4ada6\\\" to rootfs \\\"/var/lib/docker/overlay2/04e4c34c1d0f67a09e9f3b4feef3cadd6e4b1e8e016fae48762b250798769803/merged\\\" at \\\"/var/lib/docker/overlay2/04e4c34c1d0f67a09e9f3b4feef3cadd6e4b1e8e016fae48762b250798769803/merged/dev/termination-log\\\" caused \\\"no such file or directory\\\"\""

The thing is that it worked at firts try. It could'nt make a volume though since I didnt attached anything on /dev/vdb.
It seems like when running a new container, kubernetes is trying to look at the oldest one, in the termination-log files but can't find it.
Kubernetes says all pods are removed.

terraform destroy => terraform apply fixed everything....
Seems like at the first deployment volumes at /dev/vdb were not attach.
Thanks for the great work!

repo: hobby-kube/guide

license: mit

license_source: bigquery


text:
Can't seem to initialize more than 1 instance

Hello,
I need to send on more than 1 universe from within the same code.  I'm trying to create multiple instances of the artnet library but it does not seem to work.  Is it possible to do this ?
Thanks

Hi,
I published a new version of the module, now you can send to multiple universes:
artnet.send(0, 1, 255); // set channel 1 in universe 0 to 255
artnet.send(2, 1, 255); // set channel 1 in universe 2 to 255

I own a Artnet node that only supports one universe, so i can't test that - would be glad to hear from you if it works as expected.
Pls mind the changes in the interface, see Readme.
Regards,
Sebastian

...forgot to mention: you can now use multiple instances of the module too.

authors: hobbyquaker natcl

repo: hobbyquaker/artnet


text:
windows 7 @ aurora bugs

Errors:

mosek doesn't build, hanging uninterupptably after complaining about header syntax issues
mosek_cli doesn't work with paths that have dots in their names
cvxopt takes like 10 seconds to import? needs profiling
tests take forever; is this in mosek_cli?

edited cli_expopt.py:
def imize_fn(path=None, clearfiles=False):  # 8/25, Ned: clearfiles was True
    """Constructor for the MOSEK CLI solver function.

    Arguments
    ---------
    path : str (optional)
        The directory in which to put the MOSEK CLI input/output files.
        By default uses a system-appropriate temp directory.
    """
    if not path:
        path = "C:\\gpkit" # 8/25, Ned: TERRIBLE HACK, WAS tempfile.mkdtemp()
    filename = path + os.sep + "gpkit_mosek"
    if "mosek_bin_dir" in settings and settings["mosek_bin_dir"] not in os.environ['PATH']:
        os.environ['PATH'] = ":".join([os.environ['PATH'],
                                       settings["mosek_bin_dir"]])

@wthalheimer are you using mosek 7 or 8?

@mayork I'm using 8, just freshly downloaded from the link in the docs

@wthalheimer cool just curious. debugging a separate issue rn.

I'm thinking that MOSEK 8 might be having some weird constant-offset in solve time :-/
@wthalheimer @mayork try MOSEK 7? https://www.mosek.com/downloads/list/7/

@bqpd i'm still on mosek 7...all I did was update license, not reinstall

Weird...

@bqpd have you experienced the slow down?

I didn't notice if so. Let's move discussion to the other thread

authors: bqpd mayork wthalheimer

repo: hoburg/gpkit


text:
[ll] to {ll} in array latex

Doing this made me notice we have triply-repeated code in latex array generation
ready for review.

Looks good! Geometric program will lose it once it inherits from CostedConstraintSet.

authors: bqpd whoburg


text:
Get Crashes Can't access the Fragment View's LifecycleOwner when getView()

Get crashes like this even when i already check if lifecycle at least in STARTED
Fatal Exception: java.lang.IllegalStateException: Can't access the Fragment View's LifecycleOwner when getView() is null i.e., before onCreateView() or after onDestroyView()
at androidx.fragment.app.Fragment.getViewLifecycleOwner(Fragment.java:361)
at android.view.View.performClick(View.java:7297)
at android.view.View.performClickInternal(View.java:7274)
at android.view.View.access$3600(View.java:819)
at android.view.View$PerformClick.run(View.java:28023)
at android.os.Handler.handleCallback(Handler.java:914)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:225)
at android.app.ActivityThread.main(ActivityThread.java:7564)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:539)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)

Hi @JosephSanjaya
You should access ViewBinding property after onCreateView until onDestroyView.

Hi @JosephSanjaya
You should access ViewBinding property after onCreateView until onDestroyView.

The problem is i'm not even trigger the onClick event, I'm assigned it on DataBinding as variable "listener" at onViewCreated which mean it safe right?.

The problem is i'm not even trigger the onClick event, I'm assigned it on DataBinding as variable "listener" at onViewCreated which mean it safe right?.

May you post some lines of code ?

May you post some lines of code ?

Fragment
class SampleFragment :Fragment(R.layout.sample_layout), View.OnClickListener {
    private val mBinding by viewBinding(SampleLayoutBinding::bind)

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        mBinding.listener = this
    }

    override fun onClick(view: View?) {
        if(viewLifecycleOwner.lifecycle.currentState.isAtLeast(Lifecycle.State.STARTED)) {
            when(view) {
                mBinding.sampleButton -> sampleFunction.invoke()
            }
        }
        super.onClick(view)
    }
}

Layout
<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools">

    <data>
        <variable
            name="listener"
            type="android.view.View.OnClickListener" />
    </data>

     <LinearLayout
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:orientation="vertical">
         <Button
                android:id="@+id/sampleButton"
                 android:onClick="@{listener}"
                android:layout_width="match_parent"
                android:layout_height="wrap_content"/>

        </LinearLayout>
</layout>

Here it is, thank you!

Fragment
class SampleFragment :Fragment(R.layout.sample_layout), View.OnClickListener {
    private val mBinding by viewBinding(SampleLayoutBinding::bind)

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        mBinding.listener = this
    }

    override fun onClick(view: View?) {
        if(viewLifecycleOwner.lifecycle.currentState.isAtLeast(Lifecycle.State.STARTED)) {
            when(view) {
                mBinding.sampleButton -> sampleFunction.invoke()
            }
        }
        super.onClick(view)
    }
}

Layout
<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools">

    <data>
        <variable
            name="listener"
            type="android.view.View.OnClickListener" />
    </data>

     <LinearLayout
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:orientation="vertical">
         <Button
                android:id="@+id/sampleButton"
                 android:onClick="@{listener}"
                android:layout_width="match_parent"
                android:layout_height="wrap_content"/>

        </LinearLayout>
</layout>

Here it is, thank you!

@JosephSanjaya  I copied  and run your code, no crash happened

@JosephSanjaya  I copied  and run your code, no crash happened

I didn't get crashed either when in staging build, but it listed in my Application Crashlytics Dashboard on production build, and it happened occasionally.

I didn't get crashed either when in staging build, but it listed in my Application Crashlytics Dashboard on production build, and it happened occasionally.

Hey, mind giving 1.0.0-alpha03 a go?

https://github.com/hoc081098/ViewBindingDelegate#throws-illegalstateexception-attempt-to-get-view-binding-when-fragment-view-is-destroyed-when-accessing-delegate-property-in-ondestroyview

Sure, sir
Thank you for your reply...


text:
Fix rendering in table with empty cells

This is for the 3.0 branch.
find_emph_char returns 0 if the char specified is not found in the current line, but this is also what happens when there's an empty cell. This patch adds logic to work around this problem.
Tests added for general table syntax validation. The last example in Table.text addresses the problem mentioned.
See uranusjr/macdown#321.

Thanks!

authors: jmendeth uranusjr

repo: hoedown/hoedown

license: isc


text:
Player doesn't start on old android web browsers in webview when activated google ima.

Hi,
Old Android browsers are using by a few people, but webview engines in android applications use old  android browser in version <= 4.4.2 . In these devices when a user click on the player, player doesn't do anything. If the player starts without google ima, the player plays as expected.
I use  function at below to detect this browsers.
    var isAndroidBrowser = function() {
       var navU = navigator.userAgent;

       // Android Mobile
       var isAndroidMobile = navU.indexOf('Android') > -1 && navU.indexOf('Mozilla/5.0') > -1 && navU.indexOf('AppleWebKit') > -1;

       // Apple webkit
       var regExAppleWebKit = new RegExp(/AppleWebKit\/([\d.]+)/);
       var resultAppleWebKitRegEx = regExAppleWebKit.exec(navU);
       var appleWebKitVersion = (resultAppleWebKitRegEx === null ? null : parseFloat(regExAppleWebKit.exec(navU)[1]));

       // Chrome
       var regExChrome = new RegExp(/Chrome\/([\d.]+)/);
       var resultChromeRegEx = regExChrome.exec(navU);
       var chromeVersion = (resultChromeRegEx === null ? null : parseFloat(regExChrome.exec(navU)[1]));

       // Native Android Browser
       return isAndroidMobile && (appleWebKitVersion !== null && appleWebKitVersion < 537) || (chromeVersion !== null && chromeVersion < 37);
   };

   var playerConfigs = {}; // some configs

   if (!isAndroidBrowser()) {
       playerConfigs.ads = {
           adsUrl: "url",
       };
   }

   hola_player(playerConfigs); //

I guess google ima sdk or videojs-ima has a bug. Many people uses devices with <= 4.4.2 android os, in applications  use webview videojs-ima doesn't working well.  Do you have any suggestion for this situation?

Hi,
I'm trying to reproduce this with android emulator. It would be very helpful if you could give some more info:

page URL. Is it reproducible on the following page? http://jsbin.com/bilahoq/1/edit?html,output
exact user agent string for such device
browser console output
error messages, screenshot, etc.

Hi,
This is user agent of the test device:
User agent is Mozilla/5.0 (Linux; Android 4.4.2; LG-D802TR Build/KOT49I.D802TR20c) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/30.0.0.0 Mobile Safari/537.36
This is my test page: http://www.mynet.com/tv/hola_player_test.html
You can see the problem run the test page in a WebView container.

Hi,
I've tried to reproduce this issue on different real devices and emulator, but with no luck. The closest I've found is Android 4.4.2 emulator with a user agent:
Mozilla/5.0 (Linux; Android 4.4.2; Android SDK built for x86 Build/KK) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/30.0.0.0 Mobile Safari/537.36
The emulator has a bug with displaying video (black screen instead of the video, but audio plays fine) which is not related to Hola player and effects plain mp4 video as well.
Your test page works on this emulator. There is an ad and the main video after it (actually only sound, because of the emulator bug).
Could the described issue be related only to your test device?
Do you see an ad but the video after it doesn't work, or the player doesn't respond to a click and doesn't start an ad?

Hi,
The player doesn't respond to a click. When i click to player device fire touch event, but doesn't anything happen.
I will try to send a video.

Screencast -> https://drive.google.com/file/d/0B1C2r2ovnkvQUmJRSGNhOFQzWXM/view?usp=sharing

Could you please share this app sources?

Hi,
Yes, it is here -> https://github.com/erayasan/android-webview-browser

Thanks for the app. Now I can reproduce the issue.

Hi,
For some reason video element ignores click event that come from google ima iframe.
I made a workaround to fix the issue. To activate it you should init the player with ads.hideAdContainer=true option. Player will hide an ad container and show it only after user clicks on the video.

authors: akashta mahmutbayri


text:
attribute_updated initial value issue from re-started end device?

I'm setting up subscription to attribute_updated events on the MeasuredValue attribute from a sensor device. This is working fine as long as the end device is not re-started.
When an end-device is re-started, I notice that the attribute_updated event may contain a "random" (initial) value, since the end sensor device may not yet have been able to perform a sensor reading and write that value to the MeasuredValue attribute.
This may cause an issue with an "invalid" sensor value being reported.
This is an example of an attribute_updated message regarding an end device with a temperature sensor that was just re-started:
{
"event": "attribute_updated",
"data": [
1,
"1/1026/0",
0
]
}
Ideally the reported value should have been NULL and not zero.
From the end device side it looks like the default value should be NULL, but I have not confirmed this yet.

I don't know the underlying Matter platform well enough to understand if it's possible for a client to distinguish between a MeasuredValue read from an end device that is just some initial value, or if the value is from an actual sensor reading.
Ideally, the MeasuredValue would not be reported until it contains a proper sensor value.
Would this be possible, or is this a limitation of the underlying Matter platform, since the client is polling for values  rather than waiting for reports (like Z-Wave works in most cases)?
Or, is it up to the end device to make sure that the MeasuredValue attribute is set to NULL before writing an actual value to the attribute and the clients will handle NULL properly?

It looks like the initial value from the device in question was reported as zero and not NULL, so it's not an issue with the Python Matter Server for now.


text:
MariaDB Addon - cant restore database from mysql dump

First thanks for the MariaDB Addon. I am currently writing my own addon and want my new addon to integrate with your MariaDB Addon. Unfortunatly I am unable to restore a mysql dump (sql file) into your addon.
I have created the database in the mariadb addon.
The following command works, but unfortunatly displaying tables, and entrys doesnt return anything.
`
host=$(bashio::services "mysql" "host")
password=$(bashio::services "mysql" "password")
port=$(bashio::services "mysql" "port")
username=$(bashio::services "mysql" "username")
bashio::log.info "Creating database $mariadb_filename on MariaDB Addon $host if required"
mysql \
    -u "${username}" -p"${password}" \
    -h "${host}" -P "${port}" \
    -e "CREATE DATABASE IF NOT EXISTS \`$mariadb_filename\` ;"
if [ -f /share/$mariadb_filename.sql ]; then
bashio::log.info "Listing current Tables of $mariadb_filename Database with user ${username}"
mysql \
    -u "${username}" -p"${password}" \
    -h "${host}" -P "${port}" \
    -e "SHOW TABLES FROM $mariadb_filename ;"
bashio::log.info "Importing file  /share/$mariadb_filename.sql on MariaDB Addon $host with user ${username}"
mysql \
    -u "${username}" -p"${password}" \
    -h "${host}" -P "${port}" \
    -e "--database=$mariadb_filename < /share/$mariadb_filename.sql ;"

`

I'm not really sure where the problem is with just this piece of information.
I do have an example on where I have done something similar with a migration from an internal add-on hosted MySQL instance to the MySQL service:
https://github.com/hassio-addons/addon-nginx-proxy-manager/blob/master/proxy-manager/rootfs/etc/cont-init.d/mysql.sh

Okay, I am sorry. Looks like I used the worng commands. Your link helped me.
Thank you!

authors: FaserF frenck

repo: home-assistant/hassio-addons


text:
OpenZwave add-on does not startup

OpenZwave does not startup or update.
Error first visible when updating 0.5.2 to 0.5.3.
Error msg:
Can't install homeassistant/armv7-addon-zwave:0.5.3 -> 404 Client Error: Not Found ("manifest for homeassistant/armv7-addon-zwave:0.5.3 not found: manifest unknown: manifest unknown").
This error is often caused by not having enough disk space available. Available space in /data is: 20.8 GiB

Bypassing the update by deleting and (re) installing OpenZwave add-on, gives the same error.
Result error: Zwave network is not accessible.
Environment

Raspberry Pi 4:

arch
armv7l

chassis
embedded

dev
false

docker
true

docker_version
19.03.11

hassio
true

host_os
HassOS 4.13

installation_type
Home Assistant OS

os_name
Linux

os_version
4.19.127-v7l

python_version
3.8.3

supervisor
243

timezone
Europe/Amsterdam

version
0.114.4

virtualenv
false

Home Assistant Core release with the issue: 0.114.4
Last working Home Assistant Core release (if known):
Operating environment (OS/Container/Supervised/Core):
Integration causing this issue:   OpenZwave 0.5.3
Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Error msg: 20-09-15 09:11:08 INFO (SyncWorker_1) [supervisor.docker.interface] Pull image homeassistant/armv7-addon-zwave tag 0.5.3.
20-09-15 09:11:10 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install homeassistant/armv7-addon-zwave:0.5.3 -> 404 Client Error: Not Found ("manifest for homeassistant/armv7-addon-zwave:0.5.3 not found: manifest unknown: manifest unknown").
20-09-15 09:11:10 INFO (SyncWorker_1) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 20.8 GiB
20-09-15 09:18:24 INFO (SyncWorker_0) [supervisor.docker.interface] Pull image homeassistant/armv7-addon-zwave tag 0.5.3.
20-09-15 09:18:25 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install homeassistant/armv7-addon-zwave:0.5.3 -> 404 Client Error: Not Found ("manifest for homeassistant/armv7-addon-zwave:0.5.3 not found: manifest unknown: manifest unknown").
20-09-15 09:18:25 INFO (SyncWorker_0) [supervisor.docker.interface] This error is often caused by not having enough disk space available. Available space in /data is: 20.8 GiB
Additional information

The docker builds for three architectures, armv7, armhf and i386 failed for version 0.5.3. We currently don't know why.

Watching this thread, can't install for the same reason.

Seems to be failing on just 32-bit architectures and the CI error seems to be looking for a 64-bit time value.
/usr/lib/gcc/armv6-alpine-linux-musleabihf/9.3.0/../../../../armv6-alpine-linux-musleabihf/bin/ld: /usr/lib/gcc/armv6-alpine-linux-musleabihf/9.3.0/../../../libunwind.so: undefined reference to `__fstat_time64'
collect2: error: ld returned 1 exit status

I have same update error but have not uninstalled.  I am running on Rpi4 64bit Hassos with lots of space.  If there's any other logs or actions I can perform to assist diagnose please advise.  Not sure if the above 32/64 bit is a compile/build error or what but wanted to indicate 64bit HA isn't able to upgrade to 0.5.3 either.
Tnx

Is there a workaround until the build gets fixed? Could someone possibly copy the docker image of 0.5.2 to 0.5.3 so we can at least install OpenZWave... https://hub.docker.com/r/homeassistant/armv7-addon-zwave/tags?page=1&ordering=last_updated

Is there a workaround until the build gets fixed? Could someone possibly copy the docker image of 0.5.2 to 0.5.3 so we can at least install OpenZWave... https://hub.docker.com/r/homeassistant/armv7-addon-zwave/tags?page=1&ordering=last_updated

In my case a snapshot of two days ago was helpful.

We think we have solved the build issues now. A new release and build is underway. Stay tuned.

0.5.4 is available on the store and has installed, I'm off to try it out...

Implemented 0.5.4 successfully.
My ZWave device are accessible again.
Thanks to the developers for the quick response.

Agreed, I was too busy setting up my zwave network after it worked, because it works.
Thanks for the efforts

Confirm installed 0.5.4 and working.  Thank you.

Guys!! 0.5.4 worked well (as did 0.5.3). But 0.6.0 does not start!!!
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] auth.sh: executing...
[22:48:06] INFO: Auth database exists
[cont-init.d] auth.sh: exited 0.
[cont-init.d] mqtt.sh: executing...
[22:48:09] INFO: Connected to internal MQTT service
[cont-init.d] mqtt.sh: exited 0.
[cont-init.d] network_key.sh: executing...
[cont-init.d] network_key.sh: exited 0.
[cont-init.d] novnc.sh: executing...
sed: /usr/share/novnc/vnc_lite.html: No such file or directory
[cont-init.d] novnc.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] mqtt.sh: executing...
[22:48:10] INFO: Ensure upstream MQTT server has the correct OZW status
[cont-finish.d] mqtt.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Deleted the openzwave topic via mqtt explorer.... nothing! Help!

same here

restoring from a vmware snapshot 22:00 (1:18) but sooo slow (waiting takes long)

is there an easy way to downgarde?

Don't know and don't think so... unless you use the native containers instead off the add-on I think you must be able to with a new (old) docker pull (but not the expert here).

Created separate ticket for 0.6.0: #1582

@GeertvanHorrik thank you, that seems indeed the issue. I successfully restored my vmware snapshot all fine again... holding my updates for a few days for now...

0.5.3 issue is solved. Therefore this issue is closed.
for 0.6.0 problems; see ticket https://github.com/GeertvanHorrik

authors: AndrewGWalsh GeertvanHorrik MartinHjelmare bakboord4 dsegantx edvanr gcorgnet-vista nemith sanderlv tolookah


text:
Unable to update hassio 0.73.2 to 0.74

Home Assistant release with the issue:
0.73.2
Unable to updated to 0.74
Last working Home Assistant release (if known):
0.73 updated successfully to 0.73.2
Operating environment (Hass.io/Docker/Windows/etc.):
Raspberry Pi 3 B+
hass.io 115
Resin OS 2.3.0+rev1
Connected via WiFi
Component/platform:
Upgrade
Description of problem:
Attempting to upgrade to 0.74 from the UI or via the hassio command line fails.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
https://github.com/shortbloke/home_assistant_config
Traceback (if applicable):
# hassio ha update
ERROR
panic: interface conversion: interface is nil, not string

goroutine 1 [running]:
panic(0x2c7050, 0x1070a920)
        /home/travis/.gimme/versions/go1.7.6.linux.amd64/src/runtime/panic.go:500 +0x33c
github.com/home-assistant/hassio-cli/command/helpers.DisplayOutput(0x107cc200, 0x24, 0x200, 0x0)
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/helpers/common.go:118 +0x3c8
github.com/home-assistant/hassio-cli/command/helpers.ExecCommand(0x2f6f83, 0xd, 0x7ecb2e60, 0x6, 0x0, 0x0, 0x76500, 0x0, 0x0, 0x0, ...)
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/helpers/common.go:155 +0x308
github.com/home-assistant/hassio-cli/command.CmdHomeassistant(0x107864d0)
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/homeassistant.go:48 +0x540
github.com/urfave/cli.HandleAction(0x2af768, 0x324b14, 0x107864d0, 0x0, 0x0)
        /home/travis/gopath/src/github.com/urfave/cli/app.go:503 +0xf0
github.com/urfave/cli.Command.Run(0x2f6f83, 0xd, 0x0, 0x0, 0x40bd10, 0x1, 0x1, 0x301e4d, 0x2f, 0x0, ...)
        /home/travis/gopath/src/github.com/urfave/cli/command.go:165 +0x6b8
github.com/urfave/cli.(*App).Run(0x107b2380, 0x1070a120, 0x3, 0x4, 0x0, 0x0)
        /home/travis/gopath/src/github.com/urfave/cli/app.go:259 +0x8b0
main.main()
        /home/travis/gopath/src/github.com/home-assistant/hassio-cli/main.go:22 +0x108

Checking hassio su logs shows:
18-07-21 20:34:30 INFO (SyncWorker_5) [hassio.docker.interface] Update docker 0.73.2 with homeassistant/raspberrypi3-homeassistant:0.74.0
18-07-21 20:34:30 INFO (SyncWorker_5) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.74.0.
18-07-21 20:34:41 ERROR (SyncWorker_5) [hassio.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:0.74.0 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi3-homeassistant:0.74.0: No such image: homeassistant/raspberrypi3-homeassistant:0.74.0").

Additional information:
Update to 0.74 is advertised in the hass.io Dashboard

exactly same problem here - except trying to upgrade from 0.72.1

A 404 Client Error: Not Found thrown by Docker can be either of the following things:

The container images do not exist.
You don't have enough disk space left to complete the operation.

It isn't the first option, so you probably are experiencing the second.
PS: Seems like a weird message to receive, but this is actually documented by Docker.

Could it be the trailing "." at the end of the version number, or is that just message formatting?
Pull image homeassistant/raspberrypi3-homeassistant tag 0.74.0.

Might be something specific to Resin OS based Hassio. I've just spent this creating a new SD card using HassOS 1.7 (64bit). This started as 0.74, restoring my snapshot took it back to 0.73.2, ran the update from the command line and it's now successfully running 0.74.0. Admittedly I switch from 32bit to 64bit and from  Resin OS to HassOS, so at least two things changed.

Yes, the docker version on ResinOS have some times troubles. I don't know why but we support now only HassOS

As mentioned I made the move from Resin OS to HassOS and it wasn't too difficult, followed:
https://www.home-assistant.io/blog/2018/07/11/hassio-images/
Only thing I noticed was that the dropbox addon I was using, disappeared during the migration. Might have been something I did, or maybe because it was from a non-standard repo?
But sounds like people who are having this issue should consider moving to HassOS.

Yeah, look like there is a timing bug on restore snapshot. I will look into that soon

authors: frenck jens-idoer pvizeli shortbloke

repo: home-assistant/home-assistant


text:
Xiaomi Temperature Sensor Units Change When Unavailable - Issue with min_max sensor

Home Assistant release with the issue:

Home Assistant 0.85.1
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

https://www.home-assistant.io/components/sensor.min_max/
https://www.home-assistant.io/components/xiaomi_aqara/
Description of problem:
When the Xiaomi Temperature sensors are working their units are °F, but when the Xiaomi Temperature sensor is unknown, which happens occasionally, the units change to °C.  This breaks the min_max sensor since the units are no longer the same for all sensors.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
xiaomi_aqara:
  discovery_retry: 5
  # interface: '192.168.86.119'
  # interface: '192.168.86.145'
  gateways:
    - mac: !secret xiaomi_mac
      key: !secret xiaomi_pw
    - mac: !secret xiaomi_mac2
      key: !secret xiaomi_pw2

  - platform: min_max
    name: "Shop Average Temperature"
    type: mean
    round_digits: 1
    entity_ids:
      - sensor.shop_multisensor_temp
      - sensor.shop_cart_temp
      - sensor.shop_entry_temp
      - sensor.finishing_room_temp
      - sensor.finishing_room_temp2

Traceback (if applicable):

Additional information:

I believe this is still an issue.


text:
MySensors dev build: Gateway has changed to MQTT-Client-Mode

We try to setup a MySensors-Array with HomeAssistant. Currently we use both as Clients, connected to a RabbitMQ.
We currently uses the Dev-Build of MySensors which allowes that the MySensors-Gateway is connected to MQTT as Client.
Does anybody uses MySensors in a MQTT-Setup as Client? We are not successful on getting the presentation-messages displayed as buttons in HomeAssistant.
Home Assistant release (hass --version):
0.23.1
Python release (python3 --version):
Python 3.5.2
Component/platform:
HomeAssistant-MySensors
Description of problem:
Troubles on initial presentation-messages as MQTT-Client from an RabbitMQ.
Problem-relevant configuration.yaml entries and steps to reproduce:

mysensors:
  gateways:
    - device: '11.12.15.1'
      persistence_file: './mysensors.pickle'
      tcp_port: 1883
  debug: true
  persistence: true
  version: '1.5'
  optimistic: false

//cc @robertproemper

I forgot to mention that we tested the MQTT-Setup before with a manual configuration via the MQTT-Plugin:
mqtt:
  broker: 11.12.15.1
  port: 1883

binary_sensor 1:
  platform: mqtt
  state_topic: "mygateway1-out/0/7/1/0/16"
  name: "Button-Tester"
  payload_on: 1
  payload_off: 0

There's currently no connection between the mysensors component in home assistant and the mqtt component. This means that if you want to use mqtt for mysensors you have to setup each mqtt device/entity yourself in the home assistant config using the mqtt component and platforms and you shouldn't use the mysensors component. Just configure the correct topics according to the topic pattern of the mysensors mqtt client gateway.
@Mihai258 has plenty of experience on this.
FYI, I'm working on a mqtt feature for the mysensors component, which will configure the topics automatically, but it's still WIP.

Hm sad to hear that, we want to add something around 50 nodes with many different types of sensors and actors ... so a parse of the presentation would be a must-have feature for us.
How may we help you?

There seems to be a bug in the documentation as well, there is an IP-Address.
https://home-assistant.io/components/mysensors/

The mysensors component currently supports the serial and ethernet gateways.

As soon as I can push a PR it would be great if you want to test it.

I'm fine with that, actually I'm a Python programmer so I could do a review too.

Great! I'll ping you and ref this issue when it's up. If I don't get it up tomorrow, it'll probably be after the weekend some time.

I have something semi-functional here now:
https://github.com/MartinHjelmare/home-assistant/tree/mysensors-mqtt
I can see topic updates coming in but I'm thinking some messages are missed cause devices are not added to home assistant. I'll have to do more testing and dig into that. Feel free to have a look and test it if you want, but mind its incompleteness.
I've tested with 2.0 version of mysensors library, mqtt W5100 client gateway and a node, and the home assistant built in mqtt server. Config instructions for home assistant are in the docstring in the mysensors component module.

Thanks, I'll give it a try

Sorry for the long delay, try to find time today, another project blocked my time completely.

No problem. I think I've found the problem that was causing missing messages. I've made a line comment in the PR at pymysensors. Hopefully I can push a fix later today.

Ok, I think it's working as expected now. I haven't tested it extensively though, so I'll appreciate all feedback.

hass[1234]: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=Motion Sensor, qos=0, topic=mygateway1-out/0/255/3/0/11>
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=1.0, qos=0, topic=mygateway1-out/0/255/3/0/12>
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=, qos=0, topic=mygateway1-out/0/7/0/0/1>
hass[1234]: ERROR:mysensors.mysensors:Node 0 is unknown, will not add child sensor.

My config:
mqtt:
  broker: 11.12.15.1
  port: 1883
  client_id: home-assistant-1
  keepalive: 60

mysensors:
  gateways:
    - device: mqtt
      persistence_file: './mysensors.json'
      topic_in_prefix: 'mygateway1-out'
      topic_out_prefix: 'mygateway1-in'
  debug: true
  persistence: false
  version: '2.0'
  optimistic: false
  retain: true

sensor:
  platform: mysensors

switch:
  platform: mysensors

Wondering what is missing? I thought all unknown switches etc. are added automatically? :)

Looks like you have the sensor(s) locally on the gateway? There's a bug in 2.0.0 of mysensors, where a gateway without radio transport defined, does not present itself (node).
https://github.com/mysensors/MySensors/issues/524
Do you have radio defined? Do you have a parallell serial log output from the gateway?
To workaround the bug you can call present yourself in setup,ie
present(255, S_ARDUINO_REPEATER_NODE);

Thanks for the very fast help, we're using the radio and the w5100 module, but you were right - it's a gateway only setup a.t.m. so the wifi-module might not be fully initialized.
There is no serial output, as far as we know.
Just again for the record: we're using a dev-version of mysensors 1.7, just because this has support for MQTT as client. On the x86_64 system which runs HA a RabbitMQ as message broker is passing the MQTT messages to HA.
We're reviewing our source and head back to give you feedback. :)

Thats what we hacked so far ...
https://github.com/OpenSourceHouse/MySensorsSketches/blob/master/GatewayW5100MQTTClient

If you hook up the gateway arduino to a computer eg via USB, you can open the Arduino IDE and the serial monitor. The gateway will log what's going to serial if you have #define MY_DEBUG in the sketch or in MyConfig.h. It's really good to see this log when debugging. I always try to have atleast one side on a serial monitor, either gateway or node.
There's also this bug:
https://github.com/mysensors/MySensors/issues/449
I think your sketch looks ok, but it wont work to have local sensors with these bugs. I suggest connecting a separate node to the gateway.

We've added a presentation message as you described:
https://github.com/OpenSourceHouse/MySensorsSketches/commit/0a710c9644675e4cd9a09fb80b2ac78f84038a18
Now the home-assistant-log read like this:
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=2.0.0-beta, qos=0, topic=mygateway1-out/0/255/0/0/18>
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=Motion Sensor, qos=0, topic=mygateway1-out/0/255/3/0/11>
hass[1234]: INFO:homeassistant.components.mysensors:No sketch_name: node 0
hass[1234]: INFO:homeassistant.components.mysensors:No sketch_name: node 0
hass[1234]: INFO:homeassistant.components.mysensors:No sketch_name: node 0
hass[1234]: INFO:homeassistant.components.mysensors:No sketch_name: node 0
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=1.0, qos=0, topic=mygateway1-out/0/255/3/0/12>
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=, qos=0, topic=mygateway1-out/0/7/0/0/1>
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: service=publish, service_data=payload=, retain=True, qos=0, topic=mygateway1-in/0/7/3/0/19/, service_call_id=140319303721480-1, domain=mqtt>
hass[1234]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=140319303721480-1>

We're getting closer. Can you add the logger component to your HA config and activate debug level logging for mysensors.mysensors module. I'd like to see topic subscription logging.
One thing is missing from your sketch. You need to send an initial value for your sensor in the end of presentation.
The last message in your log is a publish from HA to request a new round of presentation. That did not seem to happen. Wonder if that's something with your mysensors library version?

One thing is missing from your sketch. You need to send an initial value for your sensor in the end of presentation.

We're doing this:
Line 110: int oldValue=-1;
Line 157: if (value != oldValue)
Line 157 is on the first loop always true. :)

Btw, I looked at your HA config again: you should not add mysensors sensor or switch platforms. Those will be setup automatically via discovery. Only have the mysensors component.

Btw, I looked at your HA config again: you should not add mysensors sensor or switch platforms. Those will be setup automatically via discovery. Only have the mysensors component.

Acutally I didn't added them before I've discovered that issue with node 0... but they didn't changed anything, so they are deleted again anyway :)
Now my debug-log, right from the start of the arduino:
Jul 29 22:24:01 kernel: r8169 0000:04:00.0 eth1: link up
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/255/0/0/18: 2.0.0-beta
Jul 29 22:24:07 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=2.0.0-beta, qos=0, topic=mygateway1-out/0/255/0/0/18>
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Receiving 0;255;0;0;18;2.0.0-beta
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/255/3/0/11: Motion Sensor
Jul 29 22:24:07 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=Motion Sensor, qos=0, topic=mygateway1-out/0/255/3/0/11>
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Receiving 0;255;3;0;11;Motion Sensor
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:24:07 hass: INFO:homeassistant.components.mysensors:No sketch_name: node 0
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/255/3/0/12: 1.0
Jul 29 22:24:07 hass: INFO:homeassistant.components.mysensors:No sketch_name: node 0
Jul 29 22:24:07 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=1.0, qos=0, topic=mygateway1-out/0/255/3/0/12>
Jul 29 22:24:07 hass: INFO:homeassistant.components.mysensors:No sketch_name: node 0
Jul 29 22:24:07 hass: INFO:homeassistant.components.mysensors:No sketch_name: node 0
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/7/0/0/1:
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Receiving 0;255;3;0;12;1.0
Jul 29 22:24:07 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=, qos=0, topic=mygateway1-out/0/7/0/0/1>
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Receiving 0;7;0;0;1;
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:24:07 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Subscribing to: mygateway1-out/0/7/1/+/+
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Subscribing to: mygateway1-out/0/7/2/+/+
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Publishing 0;7;3;0;19;
Jul 29 22:24:07 hass: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: service=publish, service_data=retain=True, payload=, qos=0, topic=mygateway1-in/0/7/3/0/19/, service_call_id=140358736011840-1, domain=mqtt>
Jul 29 22:24:07 hass: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=140358736011840-1>
Jul 29 22:24:15 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:24:15 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:24:15 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:24:15 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:24:15 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:24:30 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:24:30 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:24:30 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
Jul 29 22:24:30 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:24:30 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:24:30 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None

Actally some parts of HAs seem to have crashed before I restarted it now. The main website just responded with HTTP-Code 503 ... so there might be a servant bug left in the code. :)

Oh ... Home-Assistant tried to start an MQTT-Server without any reason:
Jul 29 21:08:30 hass: ERROR:asyncio:Task exception was never retrieved
Jul 29 21:08:30 hass: future: <Task finished coro=<broker_coro() done, defined at /usr/lib/python3.5/site-packages/homeassistant/components/mqtt/server.py:19> exception=BrokerException("Broker instance can't be started: [Errno 98] error while attempting to bind on address ('0.0.0.0'
Jul 29 21:08:30 hass: Traceback (most recent call last):
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/base_events.py", line 958, in create_server
Jul 29 21:08:30 hass:     sock.bind(sa)
Jul 29 21:08:30 hass: OSError: [Errno 98] Address already in use
Jul 29 21:08:30 hass: During handling of the above exception, another exception occurred:
Jul 29 21:08:30 hass: Traceback (most recent call last):
Jul 29 21:08:30 hass:   File "/var/lib/hass/deps/hbmqtt/broker.py", line 257, in start
Jul 29 21:08:30 hass:     loop=self._loop)
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/streams.py", line 113, in start_server
Jul 29 21:08:30 hass:     return (yield from loop.create_server(factory, host, port, **kwds))
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/base_events.py", line 962, in create_server
Jul 29 21:08:30 hass:     % (sa, err.strerror.lower()))
Jul 29 21:08:30 hass: OSError: [Errno 98] error while attempting to bind on address ('0.0.0.0', 1883): address already in use
Jul 29 21:08:30 hass: During handling of the above exception, another exception occurred:
Jul 29 21:08:30 hass: Traceback (most recent call last):
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/site-packages/homeassistant/components/mqtt/server.py", line 53, in start
Jul 29 21:08:30 hass:     loop.run_until_complete(start_server)
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/base_events.py", line 375, in run_until_complete
Jul 29 21:08:30 hass:     self.run_forever()
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/base_events.py", line 345, in run_forever
Jul 29 21:08:30 hass:     self._run_once()
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/base_events.py", line 1312, in _run_once
Jul 29 21:08:30 hass:     handle._run()
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/events.py", line 125, in _run
Jul 29 21:08:30 hass:     self._callback(*self._args)
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/tasks.py", line 307, in _wakeup
Jul 29 21:08:30 hass:     self._step()
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
Jul 29 21:08:30 hass:     result = coro.send(None)
Jul 29 21:08:30 hass:   File "/usr/lib/python3.5/site-packages/homeassistant/components/mqtt/server.py", line 24, in broker_coro
Jul 29 21:08:30 hass:     yield from broker.start()
Jul 29 21:08:30 hass:   File "/var/lib/hass/deps/hbmqtt/broker.py", line 279, in start
Jul 29 21:08:30 hass:     raise BrokerException("Broker instance can't be started: %s" % e)
Jul 29 21:08:30 hass: hbmqtt.broker.BrokerException: Broker instance can't be started: [Errno 98] error while attempting to bind on address ('0.0.0.0', 1883): address already in use

Is there any call for the MQTT-Server part in your component?

You're not using the embedded broker, so I don't think the server should start. Make sure you follow the instructions for MQTT component with external broker.
Thanks for the debug log! Everything looks good, except that you're not getting a reply after you publish:
Jul 29 22:24:07 hass: DEBUG:mysensors.mysensors:Publishing 0;7;3;0;19;

This should trigger a new round of presentation, ie node and sensors. This is so that sending the initial value, which really is best to have specifically in the presentation function, has time to come in after subscribing to the set/req topics. I noticed during testing that the arduino already had sent those values before the topic subscription was done, hence I wanted to request a new presentation.
Can you give me the commit hash of of your mysensors library, so I can check if requesting a presentation is supported. Of course, this could be due the one of the bugs I referenced above.

Is there any call for the MQTT-Server part in your component?

I setup and get the mqtt component, but I think that should use your HA config, so it shouldn't load the embedded broker. I might have to check with @balloob here though, if we can't figure out any other reason.

My config is at the moment like:
mqtt:
  broker: 11.12.15.1
  port: 1883
  client_id: home-assistant-1
  keepalive: 60

mysensors:
  gateways:
    - device: mqtt
      persistence_file: './mysensors.json'
      topic_in_prefix: 'mygateway1-out'
      topic_out_prefix: 'mygateway1-in'
  debug: true
  persistence: false
  version: '2.0'
  optimistic: false
  retain: true

while 11.12.15.1 is the  local ip of eth1 which is directly connected to the arduino. The startup fail because obviously RabbitMQ is running on the same port.

Can you give me the commit hash of of your mysensors library, so I can check if requesting a presentation is supported. Of course, this could be due the one of the bugs I referenced above.

I'm waiting for a friend, it was not compiled on my machine. :)

I've give the arduino another round of rebooting, while HA remains running, because I wanted to verify with an tcpdump that the message is actually send out.
So this is happening:
-Now the sensors appeared.

The debug-log is this:
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
Jul 29 22:55:24 kernel: device eth1 entered promiscuous mode
Jul 29 22:55:44 kernel: r8169 0000:04:00.0 eth1: link down
Jul 29 22:55:45 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:55:45 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:55:45 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:55:45 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:55:45 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:55:47 kernel: r8169 0000:04:00.0 eth1: link up
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/255/0/0/18: 2.0.0-beta
Jul 29 22:55:53 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=2.0.0-beta, qos=0, topic=mygateway1-out/0/255/0/0/18>
Jul 29 22:55:53 hass: DEBUG:mysensors.mysensors:Receiving 0;255;0;0;18;2.0.0-beta
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/255/3/0/11: Motion Sensor
Jul 29 22:55:53 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=Motion Sensor, qos=0, topic=mygateway1-out/0/255/3/0/11>
Jul 29 22:55:53 hass: DEBUG:mysensors.mysensors:Receiving 0;255;3;0;11;Motion Sensor
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/255/3/0/12: 1.0
Jul 29 22:55:53 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=1.0, qos=0, topic=mygateway1-out/0/255/3/0/12>
Jul 29 22:55:53 hass: DEBUG:mysensors.mysensors:Receiving 0;255;3;0;12;1.0
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/7/0/0/1:
Jul 29 22:55:53 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=, qos=0, topic=mygateway1-out/0/7/0/0/1>
Jul 29 22:55:53 hass: DEBUG:mysensors.mysensors:Receiving 0;7;0;0;1;
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mqtt:received message on mygateway1-out/0/7/1/0/16: 1
Jul 29 22:55:53 hass: INFO:homeassistant.core:Bus:Handling <Event mqtt_message_received[L]: payload=1, qos=0, topic=mygateway1-out/0/7/1/0/16>
Jul 29 22:55:53 hass: DEBUG:mysensors.mysensors:Receiving 0;7;1;0;16;1
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:55:53 hass: WARNING:mysensors.mysensors:child_id 7 already exists in children, cannot add child
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mysensors:update sensor_update: node 0
Jul 29 22:55:53 hass: INFO:homeassistant.components.mysensors:Adding new devices: <Entity Motion Sensor 0 7: off>
Jul 29 22:55:53 hass: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.motion_sensor_0_7, old_state=None, new_state=<state binary_sensor.motion_sensor_0_7=unavailable; friendly_name=Motion Sensor 0 7 @ 2016-07-29T22:55:53.340068+02:00>>
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.mysensors:Motion Sensor 0 7: value_type 16, value = 1
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.api:STREAM 140358845297552 FORWARDING <Event state_changed[L]: entity_id=binary_sensor.motion_sensor_0_7, old_state=None, new_state=<state binary_sensor.motion_sensor_0_7=unavailable; friendly_name=Motion Sensor 0 7 @ 2016-07-29T22:55:53.340068+02:00>>
Jul 29 22:55:53 hass: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.motion_sensor_0_7, old_state=<state binary_sensor.motion_sensor_0_7=unavailable; friendly_name=Motion Sensor 0 7 @ 2016-07-29T22:55:53.340068+02:00>, new_state=<state binary_sensor.motion_sensor_0_7=on; child_id=7, battery_level=0, V_TRIPPED=on, sensor_class=motion, device=mqtt, node_id=0, friendly_name=Motion Sensor 0 7 @ 2016-07-29T22:55:53.342750+02:00>>
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.api:STREAM 140358845297552 FORWARDING <Event state_changed[L]: entity_id=binary_sensor.motion_sensor_0_7, old_state=<state binary_sensor.motion_sensor_0_7=unavailable; friendly_name=Motion Sensor 0 7 @ 2016-07-29T22:55:53.340068+02:00>, new_state=<state binary_sensor.motion_sensor_0_7=on; child_id=7, battery_level=0, V_TRIPPED=on, sensor_class=motion, device=mqtt, node_id=0, friendly_name=Motion Sensor 0 7 @ 2016-07-29T22:55:53.342750+02:00>>
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.api:STREAM 140358845297552 WRITING data: {"time_fired": "2016-07-29T20:55:53.340139+00:00", "data": {"entity_id": "binary_sensor.motion_sensor_0_7", "old_state": null, "new_state": {"entity_id": "binary_sensor.motion_sensor_0_7", "state": "unavailable", "last_updated": "2016-07-29T20:55:53.340068+00:00", "attributes": {"friendly_name": "Motion Sensor 0 7"}, "last_changed": "2016-07-29T20:55:53.340068+00:00"}}, "event_type": "state_changed", "origin": "LOCAL"}
Jul 29 22:55:53 hass: DEBUG:homeassistant.components.api:STREAM 140358845297552 WRITING data: {"time_fired": "2016-07-29T20:55:53.342815+00:00", "data": {"entity_id": "binary_sensor.motion_sensor_0_7", "old_state": {"entity_id": "binary_sensor.motion_sensor_0_7", "state": "unavailable", "last_updated": "2016-07-29T20:55:53.340068+00:00", "attributes": {"friendly_name": "Motion Sensor 0 7"}, "last_changed": "2016-07-29T20:55:53.340068+00:00"}, "new_state": {"entity_id": "binary_sensor.motion_sensor_0_7", "state": "on", "last_updated": "2016-07-29T20:55:53.342750+00:00", "attributes": {"child_id": 7, "battery_level": 0, "V_TRIPPED": "on", "sensor_class": "motion", "device": "mqtt", "node_id": 0, "friendly_name": "Motion Sensor 0 7"}, "last_changed": "2016-07-29T20:55:53.342750+00:00"}}, "event_type": "state_changed", "origin": "LOCAL"}
Jul 29 22:56:00 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:56:00 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:00 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:00 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:00 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:01 crond[3909]: pam_unix(crond:session): session opened for user root by (uid=0)
Jul 29 22:56:01 CROND[3910]: (root) CMD (/usr/local/bin/issue_update.sh)
Jul 29 22:56:01 CROND[3909]: pam_unix(crond:session): session closed for user root
Jul 29 22:56:15 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:56:15 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:15 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:15 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:15 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:27 hass: INFO:homeassistant.components.http:Successful login/request from 127.0.0.1
Jul 29 22:56:28 hass: INFO:homeassistant.components.http:Successful login/request from 127.0.0.1
Jul 29 22:56:28 hass: DEBUG:homeassistant.components.api:STREAM 140358845297568 ATTACHED
Jul 29 22:56:28 hass: DEBUG:homeassistant.components.api:STREAM 140358845297568 WRITING data: ping
Jul 29 22:56:30 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:56:30 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:30 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:30 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:30 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:45 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:56:45 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:45 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:45 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:56:45 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:56:55 hass: INFO:homeassistant.components.http:Successful login/request from 127.0.0.1
Jul 29 22:57:00 hass: INFO:homeassistant.components.device_tracker.ubus:Checking ARP
Jul 29 22:57:00 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
Jul 29 22:57:00 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:57:00 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None
Jul 29 22:57:00 hass: INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 11.12.13.14
Jul 29 22:57:00 hass: DEBUG:requests.packages.urllib3.connectionpool:"POST /ubus HTTP/1.1" 200 None

And this is the dump from eth1:
eth1.pcap.zip

I think I've found the bug, causing the embedded broker to load. It's here:
https://github.com/MartinHjelmare/home-assistant/blob/mysensors-mqtt/homeassistant/components/mysensors.py#L87
It should be changed to:
if not setup_component(hass, 'mqtt', config):

I'll push in a minute.

https://github.com/MartinHjelmare/home-assistant/commit/78189df0aa61d7270ba61768616d163e6b175db9

Very nice support! Thanks for the awesome fast fix :)

Hey @MartinHjelmare, are you planning to merge this MySensors update to the master HA branch? I'm using ESP8266 Wifi gateway right now, but thinking to change to a MQTT GW.
Is this stable right now? Maybe using this as a custom_component...

@danichispa my plan is this:
MQTT feature is merged with dev branch at https://github.com/theolind/pymysensors, and I'll like to bump the version of master branch over there very soon. I have two more feature branches (re-presentation and OTA FW updates) I'd like to get merged before that though. When the bump at pymysensors is done, I'll make a PR to HA to use the new version and probably another PR to make the mqtt feature available. OTA FW is also another PR.
Regarding the mqtt feature, I have two fixes/changes I'd like to do, but nothing major. Since version 2.0 of mysenors, you can't send the initial value in setup or presentation, due to node's waiting for registration, that currently happens after setup and presentation. This means we should update HA docs and explain that it's best to do this in the loop and using acknowledgement. For the mqtt feature this becomes important, cause it takes a while for the mqtt topics to finalize subscription, so the HA component might miss the initial values of the topics. Currently I'm requesting a re-presentation specifically for mqtt gateway after presentation, but I'm thinking it's better to document how to make sure the gateway/HA has received the initial values, and I'll remove this re-presentation from mqtt gateway. There will be a general feature for re-presentation request for any unknown sensors, instead.
The other fix is regarding the topic prefix, to make sure this is an empty string if not set.
I can't promise a time plan, but I'd like to have this in by 0.27 of HA, so ~ two weeks.

@danichispa I would recommend also a rabbitmq as broker and connect HA as client as well as the MySensors. We use this because we want to send from a different daemon messages to MySensors for more dynamic lightning than currently available in HA :)

@RubenKelevra Now I'm using mosquitto as broker, for various sensors and device tracking, so I can send that daemon messages for lightning :D

OFFTOPIC
@danichispa what do you plan to use for lightning?

I have now 2 RGB Led strips, one behind my TV and another on our bedroom, and a cool white Led strip in the kitchen. I want to set transition time, as for now is fixed. I want the rgb leds make effects in a near future, but that will require some more study of the effects.

Solved in https://github.com/home-assistant/home-assistant/pull/2960.

@MartinHjelmare
Thanks for your work! :)
I have still some troubles to get my setup to work ... so we downloaded the latest dev-version of mysensors 2.0 and build it. Seems to work fine, our minimal mqtt-thing sends messages to our rabbitmq.
Now mysensors in HA seem to work fine as well:
[...]
INFO:homeassistant.loader:Loaded climate.mysensors from homeassistant.components.climate.mysensors
INFO:mysensors.mysensors:Setting up initial MQTT topic subscription
DEBUG:mysensors.mysensors:Subscribing to: mygateway1-out/+/+/0/+/+
DEBUG:mysensors.mysensors:Subscribing to: mygateway1-out/+/+/3/+/+

My config is:
mqtt:
  broker: 11.12.15.1
  port: 1883
  client_id: home-assistant-1
  keepalive: 60

mysensors:
  gateways:
    - device: mqtt
      persistence_file: './mysensors.json'
      topic_in_prefix: 'mygateway1-out'
      topic_out_prefix: 'mygateway1-in'
  debug: true
  persistence: false
  version: '2.0'
  optimistic: false
  retain: true

The serial console of mysensors shows the following:

I was wondering if you can give me a hint what we're doing wrong :)

You aren't seeing anything on HA side after start of gateway?
FYI there are two bugs currently, publishing from HA goes to the wrong topic structure, persistence does not subscribe to sensor topics.

Nope, we restarted the Arduino several hours later while log containing "mysensors" was recorded since the quoted ones.

Have you tried publishing to either gateway and HA with a MQTT tool?

@MartinHjelmare any progress on those two MQTT/MySensor issues you mentioned above? I have a similar config to @RubenKelevra (using latest builds) and HA is not automatically picking up the published topics from the gateway so I had to hardcode the topic paths (e.g. sensorA-in/0/9/1/0/2') because HA is only listening for 'sensorA-out/+/+/3/+/+'  when using mysensors directly.

Both bugs are fixed. HA should listen for presentation and internal messages by default, ie prefix/+/+/0/+/+ and prefix/+/+/3/+/+.
Your node should present itself and then the sensors should present. Sketchname should be sent. Please capture a debug log from HA and a parallel serial log from a node, if you think there's a bug.
From your topic it seems you have a local sensor on gateway, ie the gateway is the node (0)? Make sure you use mysensors version 2.1 as the gateway failed to present itself in some cases in version 2.0.

Thanks for the quick reply Martin. And you're right. There's nothing wrong with HA - the bug was in my yaml configuration. I had the topic_in and topic_out prefixes switched. doh!
One other question if I may. Is there a way to rename the sensors coming on MySensors via the MQTT gateway? My configuration.yaml looks like:
mysensors:
gateways:
- device: mqtt
topic_in_prefix: 'P'
topic_out_prefix: 'S'
debug: true
optimistic: false
persistence: true
retain: true
version: 2.0

Good! If you want another name than the default, "[sketch_name] [node_id] [child_id]", you can change the friendly_name for the entity under the customize section under homeassistant in the yaml configuration.
See: https://home-assistant.io/getting-started/customizing-devices/

In the logs I see my entity_id from the node being "switch.sensorgw2ce5de_0_9" (which looks like [type].[sketch_name][node_id][child_id] ) but when I add this to the customize section under 'homeassistant' like:
customize:
   switch.sensorgw2ce5de_0_9:
   friendly_name: 'Bedroom'

it says:
"Invalid config for [homeassistant]: Value of switch.sensorgw2ce5de_0_9 is not a dictionary for dictionary value @ data['customize']"
what am I doing wrong?

Try this:
customize:
  switch.sensorgw2ce5de_0_9:
    friendly_name: 'Bedroom'

holy cr*p, that was it. thanks a million. you guys are awesome.

authors: MartinHjelmare Mihai258 RubenKelevra danichispa proddy


text:
Honeywell climate component missing hvac_mode

Home Assistant release with the issue:
0.96.3
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Component/platform:
honeywell
Description of problem:
The hvac_mode attribute is missing from both of my Honeywell thermostats.

In the json payload from TCC, the current mode is uiData.SystemSwitchPosition, with values

1 heat
2 off
3 cool

However I don't see SystemSwitchPosition referenced anywhere in honeywell.py
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

HVAC mode is state.

Yes, SystemSwitchPosition --> system_mode --> hvac_mode --> state
In somecomfort:
    @property
    def system_mode(self):
        """Returns one of SYSTEM_MODES indicating the current setting"""
        try:
            return SYSTEM_MODES[self._data['uiData']['SystemSwitchPosition']]

In HA:
    @property
    def hvac_mode(self) -> str:
        """Return hvac operation ie. heat, cool mode."""
        return HW_MODE_TO_HVAC_MODE[self._device.system_mode]

authors: elupus ericgla zxdavb


text:
Mysensors V_LEVEL units incorrect --  needs to read presentation type

Home Assistant release (hass --version):
0.36.1
Python release (python3 --version):
3.5.2
Component/platform:
mysensors
Description of problem:
I have sensors that "present" as S_SOUND, S_VIBRATION, and S_AIR_QUALITY (among others)
they then send messages in mysensors rf as V_LEVEL
According to the spec here:
https://www.mysensors.org/download/serial_api_20
S_SOUND + V_LEVEL means the units are dB
S_VIBRATION + V_LEVEL means the units are Hz
S_LIGHT_LEVEL + V_LEVEL means the units are lux
etc
but in the code i see homeassistant's mysensors component is only looking at set/req of V_LEVEL.
I looked into modifying the code to read the presentation type too, but it doesn't seem to be saved somewhere that can be read at message received time. Help?
Can we determine show the units as per the spec?

The entity has access to the child type (S_TYPE), so that can be used to set the appropriate unit in the unit of measurement property. PR is welcome.
FYI, it's possible to set a custom unit for any sensor, in particular for sensors of V_LEVEL type.
https://home-assistant.io/components/sensor.mysensors/#custom-unit-of-measurement


text:
Wake On Lan switch fails setting up because of implicit conversion

Home Assistant release (hass --version): 0.4.0
Python release (python3 --version): 3.4.2
Component/platform: wake_on_lan
Description of problem:
Component fails setting up, because it cannot convert NoneType to str implicitly. Same configuration worked fine on 0.39.x and before.
Expected:
Component sets up correctly.
Problem-relevant configuration.yaml entries and steps to reproduce:
switch:
  - platform: wake_on_lan
    name: Desktop PC
    mac_address: xx-xx-xx-xx-xx-xx

Traceback (if applicable):
17-03-12 01:04:10 ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform wake_on_lan
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 153, in _async_setup_platform
    entity_platform.schedule_add_entities, discovery_info
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/switch/wake_on_lan.py", line 43, in setup_platform
    add_devices([WOLSwitch(hass, name, host, mac_address, off_action)])
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/switch/wake_on_lan.py", line 59, in __init__
    self.update()
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/switch/wake_on_lan.py", line 94, in update
    status = sp.call(ping_cmd, stdout=sp.DEVNULL)
  File "/usr/lib/python3.4/subprocess.py", line 537, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.4/subprocess.py", line 859, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.4/subprocess.py", line 1395, in _execute_child
    restore_signals, start_new_session, preexec_fn)
TypeError: Can't convert 'NoneType' object to str implicitly

Additional info:

In .40 wake_on_lan requires a host: key, add a blank one or the IP address of the machine that you are trying to wake and it should work, this will be fixed once https://github.com/home-assistant/home-assistant/pull/6532/files gets merged

In .40 wake_on_lan requires a host: key

Just an FYI, this isn't reflected in the current docs and it is not mentioned in the 0.40 announcement post.

host isn't required per se in 0.40. It was just a bug. We've adjusted the fix in #6532, and host will still not be required.

authors: MartinHjelmare iamtpage mKeRix maddox


text:
Generic thermostat fixes

Description:
The main issue fixed in this pull request is a race condition between the keep-alive mechanism and the tracking of temperature.
As a refresher on the inner workings of the generic thermostat, it tracks temperature and signals the A/C motor/heater to turn on when the temperature goes above/beyond a given threshold. When the opposite happens, it signals the motor/heater to turn off. Meanwhile, a keep-alive option retransmits the turn on/off signal, based on the thermostat's state, by using async_track_time_interval.
For example, when the A/C motor is currently cooling the room, and at the same moment a keep-alive event occurs (meaning that Home Assistant attempts to re-transmit the signal that turns on the motor) and the temperature dips below the target, causing a state change that results in turning off the motor. If the execution of the keep-alive event begins first, but is interrupted by the state change - the stage change will turn off the motor, and the continued keep-alive event will turn it back on. And the motor will stay on for another minimum cycle duration.
I took the liberty of refreshing the code, marking many of the thermostat's methods async.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[X] The code change is tested and works locally.
[ X Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hello @aronsky,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

be72838fa68007e8be5c5d5b07f86340a54897dd - This commit has something that looks like an email address (lev.aronsky@israel.ottawa.watchfire.com). Maybe try linking that to GitHub?.
e28e7afd83bb32ed536df4163aeaee57ce60f617 - This commit has something that looks like an email address (lev.aronsky@israel.ottawa.watchfire.com). Maybe try linking that to GitHub?.
b0bf108418697612f23753aced482abebb9ecf2e - This commit has something that looks like an email address (lev.aronsky@israel.ottawa.watchfire.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name <email@address.com>"

(substituting Author Name and email@address.com for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Oops, I developed this on a new system, where I didn't properly configure commit signing. I'll squash them into one commit and sign it properly soon.

authors: aronsky homeassistant


text:
Add Intent component

Description:

Google Draw version
Intents represent a users intent to do an action. Although it is very similar to a service, it is not the same. Services are meant for home control.
Now that we have API.ai, Alexa and Snips, I noticed a lot of repeating pieces of code. All three work with intents and expect some sort of response. This can be either voice or a card.
The goal is to make it trivial in Home Assistant to handle intents from different services and hook them into your components. Bonus goal is to auto-configure the conversation component with sentences that your component supports so that we get a voice assistant up and running fairly easy.
The intent component abstracts the handling of the intents away from these components and makes it available as a general interface. This makes it easy for other components to offer intent handling.
The first use case for intents will be a new intent_script component. This is basically the functionality that Alexa and Snips offer today, abstracted into a component. Both Alexa and Snips have been updated to use this new structure.
As a second use case I have included an example shopping list component that can be controlled by your voice.
Breaks config for Alexa, Snips, Conversation
To do:

[x] Fix Alexa tests
[x] Verify Alexa still works
[ ] Fire events on event bus intent_received and intent_handled (? - we don't do this for HTTP either)

Future:

[ ] Update api.ai component
[ ] Include a panel for the shopping list
[ ] Persist shopping list between restarts
[x] Update conversation to use intents
[ ] Make input available in intent_script script variables (?)
[ ] Add default intents for turning things on/off to conversation component
[ ] Allow any component to register conversation sentences that turn into intents

Feedback welcome :-)
Related issue (if applicable): fixes #8394
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
intent_script:
  LightKitchen:
    action:
      service: light.turn_on
      data:
        entity_id: light.kitchen

shopping_list:

conversation:
  intents:
    ShoppingListAddItem:
      - Add {item} to my shopping list
    LightKitchen:
      - Brighten up the kitchen

Checklist:
If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

I've updated the introduction with an architecture diagram.
@acockburn yes, API support will come too.

This is pretty similar to how I imagined an abstraction on conversational services, implementation looks good, and this is a good starting point for further functionality.

It is correct that we need import class/exception from http or intent component. But all what will go on runtime and not compile time, we should use our new hass.component.xy construct....

@balloob Really nice feature  ! thanks !
I have two questions:

How do you plan to make the shopping list persistence ?
Could we imagine to create something like Amazon Echo Dot but build by/for Home Assistant ? (Running on a Raspberry PI ?)

just write it as JSON to a file, nothing fancy (id, checked, name).
Snips.ai offers free Amazon Echo like voice service that runs 100% locally.

authors: balloob lwis pvizeli titilambert


text:
Care indicators all with the same name "Filter Mantenance"

Hi,
I notice in Eve all care indicators are shown as "Filter Mantenance" and it's difficult to see which one is main brush, filter, side brush etc, screenshot attached. How can I make it to display the name of care indicator like the screenshot on the readme page?
Many thanks in advance!
This is what I have in Eve:

This is from Readme page:

Anybody who has experienced the same issue?


text:
Plugin is responding to headphones buttons but when i press the volume up and volume down button. It would only increase the device volume but doesn't fire an event

I am trying to develop an app where when i press the input volume up button on headphone it handles the event and do something in the app but the headset buttons are not firing any event.
Any idea why is this happening ?

Check the readme, some buttons only fire events on certain operating systems.  iOS doesn’t fire volume events and will only change device volume.  This is an iOS limitation.
Android should fire volume change events.

Updated. Managed to solve the issue but now when press the volume buttons then it would not fire event rather than that it would increase the device volume.

Hi! I know it's been a while but how did you managed to make it work in Ionic3. I can't get the events from headphones. I only need the main button.

What do you mean by main button ?

Sorry if I explained myself wrong. Headphones usually have 3 buttons: vol+, vol- and the one you use to play/pause. I don't know its name. My app recognize when I plug/unplug the headphones, but none of the buttons.

As far as i remember i was actually not able to get the middle button working but was able to get vol+ and vol- button by listening for cordova events
please refer to this https://cordova.apache.org/docs/en/latest/cordova/events/events.html#volumedownbutton

repo: homerours/cordova-music-controls-plugin


text:
How can I get multi_hand_world_landmarks

As https://google.github.io/mediapipe/solutions/hands.html mentioned, Mediapipe can output multi_hand_world_landmarks, I tried to use it in unity by compling Python script into exe and sending multi_hand_world_landmarks to C# script. It works pretty good with 3D model, but .exe cannot run on Android and IOS.

I found this plugin and tried to convert handLandmarks in HandTrackingSolution.cs into multi_hand_world_landmarks, but it's too hard for me to calculate them correctly. Hope the plugin can providing multi_hand_world_landmarks directly or give me some advice how to achieve it.
Thanks！

This project depends on MediaPipe v0.8.8 (the latest version at the moment), that does not includes this feature as far as I know.
cf. https://github.com/homuler/MediaPipeUnityPlugin/issues/351
Note that source files under Assets are only sample code.
You can write and use your own config file that outputs multi_hand_world_landmarks once MediaPipe releases it and this project supports that version.

repo: homuler/MediaPipeUnityPlugin


text:
How may I get MANO parameters from pose2mesh model?

In the demo, it outputs the mesh and rendered joints on 2D image for MANO. Is there a method to output betas & poses instead of the mesh? I have the labeled hand joints, but need to extract mano parameters (betas, poses).

Pose2Mesh is a model-free method that directly regresses a 3D mesh without model parameters.
You could re-train the Pose2Mesh attached with some layers that regress parameters. Refer to this
Or you can use other projects like this

Thanks for the quick reply, I will try the linked project.

authors: hongsukchoi pzxszbry


text:
Json 转JavaBean

在成功转成JavaBean之后右侧的文本框的大小还是比较合适的，当鼠标点上去的时候，文本框就自动缩小了；
如果 Json 过长，转成JavaBean 的之后就会出现 JavaBean 里的方法和参数不完整。

可以贴一下，json字符串吗？我周末测试下，顺带修复下

抱歉，那个 Json 字符串我没找到，不过又发现了 这个小工具的一个小 bug：
3. 不能进行第二次转换，点击清空之后，将新的 Json 字符串填入，再次转 JavaBean 显示的结果还是之前的。
网站建议：
可以让大家都来投稿，但不是一股脑的塞进来，把大家推送的文章归到单独的一类，然后在首页的时候向读者进行随机推送，让读者阅读完之后进行评价或是打分。同一篇文章达到一定的程度之后（符合大部分读者的需求之后）再加入到现有的文章体系中。这个类似于向杂志社投稿，你可以参考一下，不过这个工作量有些大了。我感觉我给你挖了一个大坑？

有没有使用浏览器相关信息~
通过chrome,safari3个问题均未复现。

根据你的提示，我仔细检查了一下我的Chrome，发现有个检查英文写作纠错工具的插件：Grammarly for Chrome。我把他关闭之后就没有出现过之前的问题了。真的非常抱歉。

ok

authors: CherryLover hongyangAndroid

repo: hongyangAndroid/wanandroid


text:
face boxes 预训练权重

作者您好
4. face boxes 预训练权重这一部分下面的google drive这个链接的文件失效了

同问

这个项目引用的其他项目的链接可能已经失效了，推荐你使用这个项目的代码，里面有我自己的百度云链接https://github.com/hongyaohongyao/smart_classroom_demo

authors: Taeok-Lee hongyaohongyao sugarmeone


text:
Download data

Hi,
I am having trouble downloading data using the command
python -m spacy.en.download all
or
python -m spacy.en.download
It gives a value error,
ValueError: numpy.dtype has the wrong size, try recompiling
I noticed when searching on google, other people had this issue with numpy while installing pandas. My numpy version seems to be the latest. Which version of numpy does spacy use?
Or is there some other way of downloading the data files?
Thanks,

Hey,
The error means that the numpy that spaCy is trying to load at run-time is different from the one used at compile time. This might be because some other library has conflicted requirements, or some PYTHONPATH/virtualenv/python version/etc trickery that means you're executing in a different way from how you installed.
I often just delete the virtualenv and start a new one when this happens, because it's often faster than figuring out what's wrong. Another way is to uninstall numpy and reinstall it.

Thanks for the quick reply. I am wondering if there is a way to manually download the data needed for spacy to work? It installed properly, its missing the data.

You can download the data manually, but if you do import spacy.en.download I think you'll find it's not installed correctly.

Thanks again, i will try to do a new install.

authors: honnibal rjsbhatia

repo: honnibal/spaCy


text:
Type instantiation is excessively deep and possibly infinite with RPC

What version of Hono are you using?
3.2.5
What runtime/platform is your app running on?
Cloudflare Workers
What steps can reproduce the bug?
When the routes are separated into different files and the endpoints are defined using the builder pattern, for a route that has 17 methods and 378 lines of code
const organizationRoute = organizationController

.get("/layout", async (c, next) => {
    const response = await getOrganizationLayout(c);
    return controllerResponse(response, c);
})

.get("/link", checkAccess(), async (c) => {

})

export { organizationRoute };

Typescript gives this compile time error.
What is the expected behavior?
The generated types should be simplified to avoid the error.
What do you see instead?

Nested types generated cause the problem.
Additional information
No response

Hi @subhendupsingh !
This may be fixed with new version "v3.5.2". Try it and share the whether it is resolved.

@yusukebe This worked great on the backend. On the frontend it throws this error now. Is there a version of Typescript you'd recommend being on?

authors: Tanner-Scadden subhendupsingh yusukebe

repo: honojs/hono


text:
GitPage缺少部分样式

如图，最近更新了主题之后，在本地使用 hexo s 预览效果没有问题，部署到 GitPage 之后  部分样式缺失了，可否看下为什么？
GitPage  可见 https://limerencist.github.io

请尝试使用 hexo clean 清除缓存后重新执行 hexo s，并清楚浏览器缓存后测试。如果没有问题再使用 hexo d 部署试试，如果还有问题请继续反馈。

authors: hooozen limerencist

repo: hooozen/hexo-theme-tranquility


text:
🛑 BA is down

In aea2df9, BA ($BA_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BA is back up in be4aa2b.

repo: hoopybe/uptime


text:
Add enron failures

This branch adds a few documents that fail when indexing the Enron dataset.

Tika returns 415 for a few files. Probably a problem with our mime type detection? Anyway not a big deal.

The file Enclosed.txt gives the following error:

 Traceback (most recent call last):
   File "/opt/hoover/snoop/snoop/data/tasks.py", line 146, in run_task
     result = func(*args, **depends_on)
   File "/opt/hoover/snoop/snoop/data/digests.py", line 104, in index
     content = _get_document_content(digest)
   File "/opt/hoover/snoop/snoop/data/digests.py", line 277, in _get_document_content
     content.update(email_meta(digest_data))
   File "/opt/hoover/snoop/snoop/data/digests.py", line 193, in email_meta
     message_date = zulu(email.parse_date(message_raw_date))
   File "/opt/hoover/snoop/snoop/data/analyzers/email.py", line 153, in parse_date
     return email.utils.parsedate_to_datetime(raw_date)
   File "/usr/local/lib/python3.6/email/utils.py", line 210, in parsedate_to_datetime
     *dtuple, tz = _parsedate_tz(data)
 TypeError: 'NoneType' object is not iterable

If this is merged, the integration test in the snoop2 test suite will fail on these documents.

If this is merged, the integration test in the snoop2 test suite will fail on these documents.

Ok, this will happen again, next time let's try github's new "draft pull request" feature, I think it perfectly describes this status.

authors: jarib mgax

repo: hoover/testdata


text:
延迟评估

您在论文中提到的延迟数据具体是运行那个文件得到的：

@VainF @eltociear @horseee

Why you closed it? I also want to know

Why you closed it? I also want to know

Maybe is the test_speedup.py file. I just use time.time() to record the latency.

thank you

Why you closed it? I also want to know

Maybe is the test_speedup.py file. I just use time.time() to record the latency.

authors: BrownTan qxpBlog

repo: horseee/LLM-Pruner


text:
[Vaccin] Ajouter Johnson & Johnson (Janssen)

Le vaccin Johnson & Johnson vient d'arriver dans la campagne de vaccination. Pour l'instant, nous n'en disposons pas dans l'interface de choix du vaccin. Il faut donc le rajouter.

Janssen n'est-il pas le nom du vaccin de la firme Johnson et Johnson ? Auquel cas on l'a déjà dans vaccine.rb

Ah ouais donc en gros j'ai fait ça pour rien 🙈

Si seulement il suffisait d'ajouter une ligne dans un fichier pour avoir un nouveau vaccin :smile: :syringe:

Marf oui je viens de voir la PR, j'allais dire qu'il existait déjà. On peut le renommer "Janssen Johnson et Johnson", comme ça c'est plus clair.

Si seulement il suffisait d'ajouter une ligne dans un fichier pour avoir un nouveau vaccin 😄 💉
Oui clairement ce serait mieux, j'ai pas eu le courage de refacto le Data Model 🙈

Par contre attention, dans les Campaign, voire ailleurs, le nom du vaccin est inscrit en dur dans la base de données, un renommage pourrait casser pas mal de choses.

authors: GuillaumeWrobel MatthieuGariel colinemarie ssaunier

repo: hostolab/covidliste


text:
Add carrier name next to tracking code and implement tracking URL for supported carriers

What is the motivation for adding/enhancing this feature?
Enhance the order tracking information by displaying the carrier name next to the tracking code and providing a tracking URL for supported carriers in the order look up page.
Requirements:

Append the carrier name to the tracking code in the following format
Tracking Code: 532281899 - CityExpress
The tracking URL, at least for the carriers that provide this feature (like C807).

Additional information
Clickup ticket for reference: https://app.clickup.com/t/86cvzt9cc

Verified in release v2.10.0 and found that the tracking URL for C807 is not clickable. Hence, reopening this issue.

Verified and working fine in release v2.11.4. Hence, closing this issue.
https://jam.dev/c/9deb4624-5545-4d8e-b4ab-55f8df208a1b

repo: hotwax/fulfillment