HPM, as modified by @mavrrick58, uses the 'Beta Switch'* as the signal to display/use the beta tags in the JSON or not.
It's my read of the merged Beta revised HPM code that if the user has selected Beta for your specific Package, then HPM only 'sees' the Beta tags: betaVersion, betaReleaseNotes and betaLocation. I can't see any reason the versions being the same would have an impact, since technically the 'opposite' is never seen. If you don't have Beta selected, then HPM only sees: version, releaseNotes and location. We certainly know that works without confusion about Beta Tags, that have been allowed in the JSON for years.
* 'Beta Switch' is the combination of enabling Beta and selecting the specific package. I want to make sure it's known that allowing Beta is a two action task.
The ability for bundles to be recognized as a manageable individual item was added just in the last couple versions. I believe i may have missed something with the upgrade check that is performed for bundles.
I have seen this same thing with my integration so you are not the only one.
For drivers, apps, and whole packages it seems to force a flag that uses stable release files when the version values are the same.
I will be looking at the upgrade routine to see if i can fix this. Until then the easiest way to work around it would be to simply increment the beta to a higher version then stable.
getting too may events and sing song on the lumination portion of the outlet .. is there any chance of added an option for how often to report or what amount of change before its reported to the hub,..
After acquiring a Moes Matter Bridge and a couple of Kasa Smart Plugs (Matter), I started to play with this technology.
After too many trials and error testing, I’m not going anywhere.
I am guessing that the very first step is to create a Virtual device, naming it Moes Matter Bridge, and then assigning it as a Matter Advanced Bridge type.
After creating this virtual device, I am pressing Run button under the Commands tab on the Discovery Devices option, but after a few seconds all I get is the following message
Did you join the matter bridge to the Tuya or Smart lIfe app first? If not you do so. Then use the app to generate a 11 digit matter code. Sorry don't know the steps for this but you can Google that part. Use the code the app created and go to add device on Hubitat and matter device. Then in the area to enter the code enter the 11 digit code that you got from the Tuya or Smart Life app.
Then the system will generate a device for the matter bridge. Then go into that device and set the driver as the matter advance bridge driver and save it. Then on the commands page select discover all and the matter advance bridge will discover your devices and create chile devices for them inside Hubitat.
Just to make sure I am understanding correctly when you go into the Moes app on your phone you are choosing your gateway device and then going into the settings of that device and generating the matter code?
The warning you are getting seems like the Moes app is not commissioning the gateway to be shared by matter.
I took it upon myself to implement a version that throttles the illum/lux report using ripped off code and the same method you used for the tuya 4-1 driver..
the modified main driver (all that is required is here)
Even if I update the HPM, the update information comes up again. It seems to be a problem with the developer version.
I wonder if this is an error in HPM or something else.
I am trying to enable this for my Dirigera. Currently I only have 4+1 (5) bulbs (2 types) enabled, and this driver/connector will only discover 1 type. I wonder what can be done to get the others discovered?
It will discover the Tradfri Zigbee bulb, but not the Kajplats Matter bulbs.
That is how this works. The Kajplats are allready Matter devices. As such, they should be added directly with Hubitat. Have the Dirigera generate a Matter pairing code and add the device to HE through the add Matter device page.
If/when you get them added to Hubitat via Matter, I'd be curious to hear whether they stay linked for you. Mine will work for a day or two after being paired that way before Hubitat loses connection to them.